What makes something engineering vs not? Personally what I do doesn't feel like engineering because I imagine engineering as being about following a particular process and doing things in a very cautious and structured way, where programming is normally way more chaotic.

[–] madkarlsson 2 points 9 months ago (1 children)

Your notion of an engineer is correct in a wide sense

https://en.m.wikipedia.org/wiki/Engineer

The fact that you feel programming is not that makes me sad. But likely dependent on what software and what you work with. For example, if you build software for NASA or Baxter and dialysis machines and the likes, you'll get fired fast for not being structured. Working for Elon Musk and Twitter... Well...

[–] chicken@lemmy.dbzer0.com 1 points 9 months ago* (last edited 9 months ago) (1 children)

I don't think it has to be a sad thing. Without that sort of structure you can be more imaginative, which has many advantages. Again, I don't want to be an engineer, I feel that would suck all the joy out of it and just isn't my style. That isn't to say an engineering approach to programming doesn't exist or isn't useful/necessary in some cases, but I would say it isn't the norm and probably shouldn't be.

[–] madkarlsson 1 points 9 months ago

I personally think it's a bit of a fallacy to equal structure with less creativity.

Look at Calatrava https://duckduckgo.com/?q=calatrava&t=fpas&iax=images&ia=images

Further, you can't design something like the Burj Khalifa without creativity

Maybe the line goes where you are risking peoples life or not, maybe somewhere else. It still makes me sad that you equal programming with chaos. But that is very context driven. The drive for new software, new interfaces, new tech overall naturally breeds less oversight and less structure naturally ofc. But it doesn't have to be that way, nor should it be if you ask me