Software “Engineering”
![]() |
| /via https://consolia-comic.com/comics/house |
When you’re out there building bridges, dams, skyscrapers, and whatnot, there is a lot of formalism that is baked into the assumptions. You don’t start the whole damn thing from scratch (“We should google ‘load-bearing struts’, no?”), or worse, assume that it can be worked out in process (“You don’t know what a stress-strain curve is? That’s ok, you can figure it out as you go along”).
If anything, the burden of proof on anything new (“I plan on using plastic straws instead of steel in skyscrapers!”) is extremely high, and spread across a whole bunch of areas. From Code, to regulations, to professional certifications, to permitting, if you want to do something that is new and different, well, you need to have your shit together.
This, mind you, in direct opposition to most Software Engineering, where #CowboyDevelopers roam the earth asserting their Dunning-Kruger infused superiority…
Also, I really, really want there to be a BrickOverflow…

Comments