←back to thread

287 points moonka | 3 comments | | HN request time: 0.406s | 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 #
majormajor ◴[] No.43564230[source]
The biggest mistake those employees make on their way to getting overlooked is assuming their boss knows.

Everyone needs to advocate for themselves.

A good boss will be getting feedback from everyone and staying on top of things. A mediocre boss will merely see "obvious" things like "who closed the most tickets." A bad boss may just play favorites and game the system on their own.

If you've got a bad boss who doesn't like you, you're likely screwed regardless. But most bosses are mediocre, not actively bad.

And in that case, the person who consistently helps unblock everyone needs to be advertising that to their manager. The person who's work doesn't need revisiting, who doesn't cause incidents needs to be hammering that home to their manager. You can do that without throwing your teammates under the bus, but you can't assume omnipotence or omniscience. And you can't wait until the performance review cycle to do it, you have to demonstrate it as an ongoing thing.

replies(4): >>43564968 #>>43570649 #>>43571005 #>>43571453 #
1. stouset ◴[] No.43571005[source]
Your boss can know about it, but if their boss wants data on performance you’re back in the same boat.

Funny you mention engineers needing to market themselves though. That leads to its own consequences. I’ve been at a place where everyone needed to market their own work in order to get promoted, to get raises, and to stay off the chopping block.

The end result? The engineers at the company who get promoted are… good at self-promotion, not necessarily good at engineering. Many of the best engineers at the company—who were hired to do engineering—languish in obscurity while people who can game the system thrive. People get promoted who are only good at cranking out poorly-made deliverables that burden their team with excessive long-term maintenance issues. They fuck off to higher levels of the company, leaving their team to deal with the consequences of their previous work.

Run that script for five or ten years and it doesn’t seem to be working out well for the company.

replies(2): >>43572704 #>>43575584 #
2. geodel ◴[] No.43572704[source]
You made excellent points. As someone looking to solve problems, finish tasks and go home. I just don't feel energized marketing myself if it is not during changing jobs.

And measurement has really taken over now. There is little value in getting task done well as compared to finishing more jira stories.

3. nradov ◴[] No.43575584[source]
And that's fine. It's why the lifecycle of most technology companies is fairly short. They grow for a while and eventually stagnate, to be replaced by the next crop of startups when a disruptive innovation comes along. And then the cycle repeats.