News for hackers. Stuff that matters.
Re:Code quality only matters in context (2019) by hinkley on Tuesday May 31, 2022 @12:09PM (#31571262)
A couple years ago someone wanted to switch us off of Saucelabs because it was Expensive. I don't know how many 4-10 person meetings we had about it but it was a farce, and eventually I called them out on how many $5-10k meetings we'd had in order to try to save $25k a year.

The opportunity cost in these situations is usually harder to quantify. But for me it was distracting from cloud infrastructure work that had price charts associated with it, and contracts that also had dollar values associated with deadlines.

I think what annoyed me the most was that I had to point all of this stuff out to finally shut it down. Were were in a transitional period and people were trying to evaluate every sacred cow at the same time. That sounds like progress to some but like a recipe for burnout to me.

Re:Code quality only matters in context (2019) by mbrodersen on Tuesday May 31, 2022 @09:23PM (#31576978)
Yep it is crazy. Most employees have no idea how their work impacts the cash flow and revenues of the company they work for.
Re:Code quality only matters in context (2019) by dhzhzjsbevs on Wednesday June 01, 2022 @10:17PM (#31590535)
Any ideas on how to train people in thos area?
Re:Code quality only matters in context (2019) by mbrodersen on Friday June 03, 2022 @09:39PM (#31615997)
Ask people how they think their work contribute to the cash flow of the company. Ask them to consider what impact them not working would have on the cash flow. If their salary is greater than the income their work generate, then their work is actually not beneficial to the company. If they interrupt people who do have a positive impact on cash flow (unnecessary meetings) then it is even worse.