31–40 of 54 posts
i dont understand why people who write code consider themselves engineers. they arent liable if their code breaks. they have no professional licensing system. they dont even need an education.
This is true. While dealing with building architects on many occasions during my internship, they would say silly things like, 'Can you not just avoid this girder/beam/pillar?' My boss would coldly say 'Do you mind removing brake pedals from your car to make it prettier'?
That's not silly. There correct response is "well, what's your budget?" The reply may be a number that's an order of magnitude too small, but then you have a negotiating point to work with, or at least an understandable (and not condescending) answer.
One of the best general Engineering books I've read is 'Design Paradigms'. It's an excellent book about the importance of understanding failures in Engineering. The author is Professor of Civil Engineering and a professor of history at Duke University, so all the examples are roads/bridges/etc. As a Data/SWE guy, I still enjoyed reading it a lot. https://www.amazon.com/Design-Paradigms-Histories-Judgment-E...
Why Buildings Stand Up: The Strength of Architecture
Why Buildings Fall Down: How Structures Fail
Structural engineers have one of the most stressful jobs as well. Work is incredibly precise with deadly consequences under tight deadlines with a lot of egos in the way. Massive respect to those who thrive in this profession.
Pun intended?
One of the best general Engineering books I've read is 'Design Paradigms'. It's an excellent book about the importance of understanding failures in Engineering. The author is Professor of Civil Engineering and a professor of history at Duke University, so all the examples are roads/bridges/etc. As a Data/SWE guy, I still enjoyed reading it a lot. https://www.amazon.com/Design-Paradigms-Histories-Judgment-E...
Structures: Or Why Things Don't Fall Down by J.E. Gordon https://www.goodreads.com/book/show/245344.Structures
Science and the City https://www.goodreads.com/book/show/28260428-science-and-the...
i dont understand why people who write code consider themselves engineers. they arent liable if their code breaks. they have no professional licensing system. they dont even need an education.
I see no mention of Florida anywhere
This is true. While dealing with building architects on many occasions during my internship, they would say silly things like, 'Can you not just avoid this girder/beam/pillar?' My boss would coldly say 'Do you mind removing brake pedals from your car to make it prettier'?
I hope as you progress through your career you learn to be more respectful of diverse ideas. I'm a software engineer, I have to have discussions with designers and business people who also sometimes ask for things that just aren't reasonably doable given time and budget constraints. It's our job as professionals to explain this using a tone and words that educates others on what the technical constraints are.
This is true. While dealing with building architects on many occasions during my internship, they would say silly things like, 'Can you not just avoid this girder/beam/pillar?' My boss would coldly say 'Do you mind removing brake pedals from your car to make it prettier'?
I hope as you progress through your career you learn to be more respectful of diverse ideas. I'm a software engineer, I have to have discussions with designers and business people who also sometimes ask for things that just aren't reasonably doable given time and budget constraints. It's our job as professionals to explain this using a tone and words that educates others on what the technical constraints are.