3 ms·

? If you're doing that much reduction in your estimation, couldn't the same be said for software? The labor itself might be low skill, but the experience requi

? If you're doing that much reduction in your estimation, couldn't the same be said for software? The labor itself might be low skill, but the experience required to do the job well and to create a lasting structure takes an enormous amount of time. "should I use ceder, spruce, pine or Aztek for the exterior door casings? Should my subsill be 7 degrees or 14? Should I use felt paper or tyvek for my weather barrier, which type of tape should I use for each type?"

throwaway0a5e 6y ago
> If you're doing that much reduction in your estimation, couldn't the same be said for software? And this is why companies hire a hundred fresh grads for every gray hair. 99x/100 they don't need super high quality work output. In all trades there's a hesitation to look at something and say "screw it, it doesn't really matter, just do what's cheap" unless you're being told to and software isn't immune from that (in software "told do" seems to come mostly in the form of time pressure whereas in the trades it's what the number job is paying). Sure it's nice to do "good" high quality work but a lot of the time it really isn't necessary or it's strictly wrong because whatever it is you're building needs to be built to a price point. It's only when you push things to the limit do all the little marginal details (the stuff the experienced pros get right) start mattering. That tends to accidentally happen more (at least in my estimation) in software than the trades because labor is so expensive and code is so easily portable. Also, janky setups and quick-n-dirty fixes abound in all trades. You just only see them in trades you know about.