Gold_Sky3617 t1_j8ivo6m wrote
Reply to comment by Darkstar_k in Meta's chief business officer is leaving after 13 years amid the company ramping up its focus on 'efficiency' by luxisa
That’s not what that post says. It’s not about working hard. You can work hard to do what you’re asked to do even if what you’re asked to do is not efficient.
Developer gets asked to create something stupid. They know it’s stupid but they get paid for it being built so they do it and move on because they don’t really care about the end product.
Versus
Developer gets asked to create something stupid and they turn that request into something more useful.
In both cases the person is working hard and earning their paycheck but one actually cares and one doesn’t. It’s very common for people in tech to work hard at delivering what they are asked to deliver but providing truly good solutions usually requires that workers actually care enough to fight for the best possible end product.
aws2gcp t1_j8jabep wrote
I'll agree but with the added comment that even someone working 50-60 hours a week will never have the time they'd like to make a high quality end product. Even with good tools and a knowledgeable employee, software is extremely complex and time-consuming.
So, you have to chose your battles. It's not always a matter of "caring" - sometimes, it's just a matter of time management.
Gold_Sky3617 t1_j8jcfn6 wrote
Yeah totally agree. My example was not nuanced. Just to demonstrate that hard working does not necessarily mean that a person cares.
Because systems are so complex this really has become a huge problem. Major disconnects exist between what companies ask for, what devs build, and what end users actually care about. I totally get why a dev wouldn’t want to fight every battle but it’s become increasingly common for nobody to fight any battles and the end product just ends up sucking even though everyone on the project worked hard and did what they were supposed to do.
Viewing a single comment thread. View all comments