←back to thread

287 points moonka | 1 comments | | HN request time: 0s | source
Show context
rqtwteye ◴[] No.43562536[source]
I have been in the workforce for almost 30 years now and I believe that everybody is getting more squeezed so they don’t have the time or energy to do a proper job. The expectation is to get it done as quickly as possible and not do more unless told so.

In SW development in the 90s I had much more time for experimentation to figure things out. In the last years you often have some manager where you basically have to justify every thing you do and always a huge pile of work that never gets smaller. So you just hurry through your tasks.

I think google had it right for a while with their 20% time where people could do wanted to do. As far as I know that’s over.

People need some slack if you want to see good work. They aren’t machines that can run constantly on 100% utilization.

replies(25): >>43562590 #>>43562601 #>>43562738 #>>43562748 #>>43562796 #>>43562875 #>>43562911 #>>43562955 #>>43562996 #>>43563116 #>>43563121 #>>43563253 #>>43563309 #>>43563487 #>>43563727 #>>43563795 #>>43563837 #>>43563965 #>>43563995 #>>43564861 #>>43567850 #>>43569250 #>>43569941 #>>43574512 #>>43579456 #
mschuster91 ◴[] No.43562796[source]
> In SW development in the 90s I had much more time for experimentation to figure things out. In the last years you often have some manager where you basically have to justify every thing you do and always a huge pile of work that never gets smaller.

Software development for a long time had the benefit that managers didn't get tech. They had no chance of verifying if what the nerds told them actually made sense.

Nowadays there's not just Agile, "business dashboards" (Power BI and the likes) and other forms of making tech "accountable" to clueless managers, but an awful lot of developers got bought off to C-level and turned into class traitors, forgetting where they came from.

replies(1): >>43563227 #
potato3732842 ◴[] No.43563227[source]
I commend you for having an opinion so bad I can't tell if you're satirizing marxists or not.

Let me ask you this, would you rather be managed by a hierarchy made up of people who don't understand what you do? Because I assure you it is far worse than being managed by "class traitors".

replies(4): >>43563462 #>>43563682 #>>43563912 #>>43566243 #
mschuster91 ◴[] No.43566243[source]
> Let me ask you this, would you rather be managed by a hierarchy made up of people who don't understand what you do? Because I assure you it is far worse than being managed by "class traitors".

One's direct manager should be a developer, yes. The problem is the level above that - most organisations don't have a SWE career track, so if you want a pay rise you need a promotion and that's only available for managerial roles.

The problem there is that a lot of developers make very bad managers and a lot of organisations don't give a fuck about giving their managers the proper skills training. The result is then usually a "tech director" who hasn't touched code in years but just loves to micromanage based on knowledge from half a decade ago or more. That's bad enough in Java, but in NodeJS, Go, Rust or other hipster reinvent-the-wheel stacks it's dangerous.

They come in and blather completely irrelevant, way outdated or completely wrong "advice", plan projects with way less resources than the project would actually need - despite knowing what "crunch time" entails for their staff themselves.

replies(1): >>43567347 #
1. wiether ◴[] No.43567347{3}[source]
And also, the programmers that got "promoted" to management are people that are here for the money/power and asked to be promoted, not because they care about coding. And absolutely not because their peers wanted for them to be promoted because they saw a good manager in them while they were working together.

So they'll definitely make it worse for everyone than a guy that doesn't know anything about tech but wanted a career in management because they care about managing.