3 ms·
I think it's more of an issue where the term "engineering" means something very different in the software world than it does in the rest of the world but I find
by Arch-TK 1y ago
I think it's more of an issue where the term "engineering" means something very different in the software world than it does in the rest of the world but I find it a bit difficult to take any such article seriously when it makes statements like: "LLMs can't replace human engineering." as a response to "If you're a skilled, experienced engineer and you fear that AI will make you unemployable, adopt a more nuanced view."
If you are able to make such deductions then you should also be able to deduce that almost nobody employed in a "software engineering" role is doing any actual engineering.
The article assumes that software companies are hiring software engineers (where "engineer" actually means what it does everywhere else) when in reality most software companies are not hiring any kind of actual engineer.
And if engineers can't be replaced by AI, but you're not actually an engineer, can you be replaced by AI?
Now I don't know the answer for sure, but I'd say for most people in "software engineering" roles the answer is still no, at least for now. But the reasons definitely can't have anything to do with whether AI can do engineering.
As a final note: I'd recommend anyone in a software engineering role, who thinks they do "actual engineering", to actually study some actual engineering discipline. You most likely have the necessary level of intelligence to get started. But you will quickly find that electrical engineering, electronics engineering, mechanical engineering, structural engineering, drainage engineering, etc, are nothing like your actual day to day job in _very fundamental_ ways.
- doug_durham 1y agoI really don't want to have that argument yet again. However I hold an engineering degree and a computer science degree. Software engineering is very much engineering. Engineering is the art of tradeoffs and balance. Using a lighter weight, but more expensive steel in a structure to place less load on the foundation is an example of a tradeoff in Structural engineering. Once you get beyond the most simple code you are practicing tradeoff and balance. You can use a simple, memory intensive algorithm, but you need to understand if you have the space to use it. You might be able to develop software in 1/2 the time if you take a basic approach, but it won't scale. I don't know if you develop software or not. Regardless think more deeply about what is involved in engineering.
- Arch-TK 1y agoYou've managed to describe adulthood, or just responsible decision making, not specifically software or engineering. I notice you said you hold degrees. But which of these two disciplines do you actually work in?
- doug_durham 1y agoYou seem to have a peculiar notion of what makes up engineering. Data informed tradeoffs, math driven analysis, and deep knowledge on your field are keystones of engineering. These are also the keystones of Software Engineering which is what I practice.