this post was submitted on 02 Mar 2024
521 points (93.9% liked)
Programmer Humor
19471 readers
1113 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I still wouldn't say software engineering is actual engineering.
You mean you wouldn't expect a software engineer to understand the coefficient of thermal expansion of tungsten carbide in a gas lubricated piston/cylinder pneumatic deadweight calibration system?
Yeah, me either. But I would expect one to know how to research the documentation to find out what it meant.
Even though my job title has "engineer" in it, I don't agree that it should be considered an area of engineering.
I wouldn't even expect most of them to this kind of research, no. On top of that, I see "engineering" also carrying some type of accountability and responsibility. For example, civil engineering, there are often regulatory bodies, codes, and standards that engineers must adhere to, and they are legally responsible for the safety and integrity of their projects. While in the software side of things, standards and best practices are more loose. Unless you're working in safety critical industries (automotive, aviation, etc...), the "accountability structure" is completely different, if existent at all. Calling themselves Software developer or some derivate would make much more from my point of view.
And software development isn't actually development. They don't build houses!
Did you mean to say software architecture?
What about software painting ?
Can't wait to see the next Mona Lisa of software as an exhibition at the Louvre!
I think the idea is, most people could build a doghouse with no training, but you need planning and education to plan/build a skyscraper. If you want to write your own app at home, maybe no software planning is really required. Keep nailing in workarounds. But if you want to build a huge system, you need to do a bit more than workarounds. You need a good plan from the start to make it all efficient and in a manner others can contribute to the code base.
That said, I feel like just having workarounds is really common even in large industry settings. Maybe I'm wrong though. I'm more of a home doghouse builder type myself.
Anyone can build a bridge. Only an engineer can build a bridge that barely stands.
In the same way, the fact that one built a large online platform, that doesn't necessarily mean it was built with minimal ressources and without taking past or future risk.
Engineering is, as a profession, specifically the application of scientific principles to solve problems the right way, the first time, that is to say efficiently, and with minimal risk.
The fact that one codes, or wields a wrench, or operates a C&C machine does not mean one is applying science to solve problems efficiently and managing risk. These are entirely different skills and professions.
Why? Excited to hear another internet hot take