spudlyo
2 hours ago
So in case you're worried about watching a 35 minute video and wishing you hadn't, here is what I think is an interesting observation that the speaker starts coming around to at around the 7 minute mark.
Why does software suck? Management often has other priorities, and isn't interested in doing the hard work required to increase the reliability and reduce the technical debt in software. Engineers who care about such things, often engage in acts of "benevolent noncompliance". Common workarounds are "asking for forgiveness instead of permission", secrecy, and misdirection. Alternately you can confront management and fight for doing what you think is right. These sorts of things can be risky. You can be fired, you can be reprimanded if caught, you can be retaliated against or lose political advantage. In the past, software engineers had a lot more agency than they do now, because nowadays the supply/demand ratio no longer favors software engineers, and as a result we have weaker negotiation power. Now we're more afraid of being fired and not being able to find a job, and managers aren't afraid of us quitting and not being able to replace us.
I haven't yet finished the whole thing, but there are sections around dark patterns and other forms of user-hostile software. I'll probably finish it.
ianbutler
an hour ago
I don't think this is really entirely true. Everyone who isn't a FAANG or Frontier Lab seem to be absolutely starving for good talent. It's far more often that I hear "we interviewed someone we thought looked good and they couldn't even write a for loop, where are all the good engineers".
I think you have far more leverage than you think in most places still.
bryanrasmussen
an hour ago
I don't think I have ever encountered anyone who could not write a for loop that got a job as a programmer.
I encounter plenty that used a for loop when something else would have been advisable.
brailsafe
an hour ago
> I think you have far more leverage than you think in most places still.
In some sense this is true, but in my view it's not whether a person theoretically has leverage or opportunity, but whether it's feasible to practice or to explore it. If enough people believe that programmers shouldn't have leverage, and in-practice if there's only negative repercussions from trying, then it's not meaningful. Broadly, in any profession, it seems like it comes down to a whole lot of luck whether you have real, practicable leverage. Barring some exceptions for somehow intentionally positioning oneself to be solely responsible for an uncommonly important system in an uncommonly lucrative business, but that seems to me to also be dependent on a lot of luck.
Overall, it seems that if you really have leverage, you effectively can't economically be replaced, and everyone knows it, but otherwise you'll be on the chopping block for not doing exactly what your narcissistic boss wants on a moment to moment basis.
autoexec
2 hours ago
> In the past, software engineers had a lot more agency than they do now, because nowadays the supply/demand ratio no longer favors software engineers, and as a result we have weaker negotiation power. Now we're more afraid of being fired and not being able to find a job, and managers aren't afraid of us quitting and not being able to replace us.
This sounds like a job for unions. It would have been advantageous to have formed and joined them before so much power was lost, but it's easy to be shortsighted when you're happy and comfortable with where you are and ignore that the situation could easily change, if not for you then for the next generation. Companies are happy to leverage every advantage they have against workers. Unions can be a powerful tool for workers, one that could help solve a lot of problems current and future, and it's sitting there just waiting to be used.
enbugger
4 minutes ago
I think such comment are the exact reason why "the speaker" has quit HN. This is literally some AI transcription from the video + "I find this interesting". Why is this even in the top?
conqrr
2 hours ago
This hits so hard. I used to admire Senior developers who would do this. Now, I find myself in a place where there is no one to do this, and I've taken up to playing this role. It is the hardest job, but I cannot do any thing else as my team is committed to just non-stop slop thanks to management directives. I realize all the time I spent admiring, and now I have become.
repeekad
2 hours ago
If the engineers were right the bill will come due on that tech debt eventually. Likely when that happens the company will just spend more than they needed to fixing the issues and no one will be around to say I told you so.
wk_end
2 hours ago
The problem is that the counterfactual isn't obvious. The company spends more time - and money - than they needed to fixing those issues, but how do they know? And how do they know that it would've amounted to less if they'd done those fixes sooner? Figuring that out, and figuring it out accurately, is often extremely difficult. A serious attempt might cost more than the fixes.
...and often the amount more isn't catastrophically more, so they don't even think about it. The company might be bleeding from paper cuts, it might be terribly unhealthy because of it, but still not unhealthy enough to kill it.