←back to thread

287 points moonka | 1 comments | | HN request time: 0.203s | 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 #
p1necone ◴[] No.43562875[source]
> 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.

This has been my exact experience. Absolutely everything is tracked as a work item with estimates. Anything you think should be done needs to be justified and tracked the same way. If anything ever takes longer than the estimate that was invariably just pulled out of someones ass (because it's impossible to accurately estimate development unless you're already ~75% of the way through doing it, and even then it's a crapshoot) you need to justify that in a morning standup too.

The end result of all of this is every project getting bogged down by being stuck on the first version of whatever architecture was thought up right at the beginning and there being piles of tech debt that never gets fixed because nobody who actually understands what needs to be done has the political capital to get past the aforementioned justification filter.

replies(3): >>43562985 #>>43563084 #>>43563216 #
stouset ◴[] No.43563084[source]
Also this push to measure everything means that anything that can’t be measured isn’t valued.

One of your teammates consistently helps unblock everyone on the team when they get stuck? They aren’t closing as many tickets as others so they get overlooked on promotions or canned.

One of your teammates takes a bit longer to complete work, but it’s always rock solid and produces fewer outages? Totally invisible. Plus they don’t get to look like a hero when they save the company from the consequences of their own shoddy work.

replies(5): >>43563146 #>>43563155 #>>43564230 #>>43564503 #>>43565689 #
the_snooze ◴[] No.43563155[source]
It's even got a name: https://en.wikipedia.org/wiki/McNamara_fallacy
replies(2): >>43563336 #>>43568719 #
2OEH8eoCRo0 ◴[] No.43563336[source]
It's got a name and we know that it's happening yet the overpaid overeducated c-suite demands it? What gives?
replies(5): >>43563395 #>>43563558 #>>43563575 #>>43563847 #>>43571592 #
LeifCarrotson ◴[] No.43563558[source]
The problem is that this miserable state of affairs works at scale.

Yes, on problems that exist at the scale of one or intelligent, educated, experienced, and dedicated human (or maybe up to 3-5), an individual or small team will run circles around a business. You can have a top-notch CEO and COO and HR manager and six program managers (each with zero domain experience other than running a Jira board) and four dozen junior consultants who memorized just enough to pass the interviews and an art department and sales and finance and IT. For some problems, that whole $50M enterprise will be utterly demolished by a couple of determined engineers.

Likewise, a monarchy with a wise, benevolent, and just king can flourish, whereas a corrupted and bureaucratically entangled democracy is woefully inefficient.

But if you want your kingdom to last more than two generations before succumbing to a greedy monarch, or want your enterprise to solve bigger problems that don't decompose nicely to small ones, to vertically integrate huge manufacturing systems and scale out to billions of units, the only method that works is the inefficient one. And it does work!

replies(3): >>43563633 #>>43563716 #>>43568124 #
xg15 ◴[] No.43563633[source]
The question is if the Kingdom would then still be worth surviving if life for everyone there ends up being miserable.
replies(1): >>43564268 #
majormajor ◴[] No.43564268[source]
What if it doesn't survive and 70% of the people who were in the Kingdom end up in worse, arbitrarily-ruled, small despotic fiefdoms instead? And only 10% end up being better off by being lucky enough to have landed in the high-trust+high-competence small group?

Or, switching to consumer products vs company revenue/profit or kingdoms, and grounding in a specific example: people love to hate Windows, but how many of them would actually be better off if the options were just Mac (still expensive, still niche) or Linux? And "well they could just learn how to [code or configure text files or whatever]" for these purposes counts as worse off, IMO - more time spent on something that used to kinda-sorta-at-least-work-predictably for them.

replies(2): >>43565348 #>>43568862 #
1. sidewndr46 ◴[] No.43568862[source]
Your comparison isn't very good as Microsoft Windows undergoes perpetual change and churn for the sake of doing it. This breaks existing workflows along the way. As a product it was effectively complete by the time Windows 2000 was released, having successfully integrated what was then considered state of the art technology to develop a practical operating system based on the principals known at the time. All it ever needed from there forward was maintenance updates and kernel updates to enable new hardware level technology to be harnessed by software.