3 ms·
>> It'd be like being a carpenter or mechanic but spending the majority of your time debugging, fixing, and communication with manufacturer's of broken or poorl
by skeeter2020 3y ago
>> It'd be like being a carpenter or mechanic but spending the majority of your time debugging, fixing, and communication with manufacturer's of broken or poorly working tools.
What do you think a mechanic does ALL DAY? Very few carpenters start with a raw blank of nice wood and craft something amazing. It's all interpreting plans (poor spec), framing (boiler plate), figuring out an addition (bolting on features to a shaky platform), correcting things that have failed (maintenance), addressing things that were built wrong (bug fixes) or fixing shoddy renovations (tech debt). Sounds EXACTLY like the majority of software development.
- bmitc 3y ago> What do you think a mechanic does ALL DAY? Are you implying that they are fixing their tools rather than cars? I don't know any mechanic that would put up with that and would replace their tools with tools that actually work.
- fnordpiglet 3y agoExcept mechanics tools are fairly simple devices based on thousands of years of standardization. I think probably a better example would be someone working in a lab on experimental devices. Software tooling is often absurdly complex and relatively new with no clear standard. In 100 years I’ll wager things are not like this.
- bmitc 3y ago> Software tooling is often absurdly complex and relatively new with no clear standard. That was my entire point.
- MrVandemar 3y agoI think the implication was that mechanics generally spend all day "debugging" a car or other machine.
- bmitc 3y agoYes, exactly, because that's actually supporting my point. That is their job, so they spend all day doing their job instead of diversions along the way.