this is a good tweet and is a distinction I didn't properly understand until several years into my working career. I was calling myself a software engineer long before I deserved to.
-
-
-
me too, but i was pressured into it by a boss who hoped that calling me that would encourage me to be one instead of a coder so i don't feel bad
-
of course he also didn't ever want me to budget any time to write tests so i don't know what the hell he thought a software engineer was, at the end of the day
-
gotta love a good cargo cult i refuse to call myself one in interviews until i've made something that could kill people if it breaks
-
most software isn't a life-or-death thing though. the bridge engineering analogy shouldn't be taken too literally.
-
yeah uhhh the fact that i make hyperbolic statements like that is a pretty obvious sign of my immaturity

-
Don't worry, the fact that the system we live in is massively interdependent all but guarantees you will write something that kills people if it breaks eventually.
-
probably the sensible response is write guidance software for smart bombs so that your software kills people even when it's working perfectly
- 7 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.