71–80 of 108 posts
You’re probably optimizing for the wrong metrics. Look at the people that are promoted quickly and copy what they are doing. It probably isn’t number of JIRA tickets.
Earlier quoted context omitted.
Then they proceed to call the samn things “sprints” and except us to do them back to back to no end
A "sprint" when managed well, doesn't need to mean working tirelessly the entire period. One of the features of sprints is a way to avoid scope creep by imposing a deadline. I would argue that generally the more appropriate response to not meeting a sprint deadline is more often to cut scope than to insist than to insist devs put in extra hours.
Earlier quoted context omitted.
I need a job I can care about or else I struggle to do the work.
Right now this is unbearable for you but getting angry with your colleagues is just going to make it unbearable for everyone. Spending your passion on your own projects or OSS will yield you better returns 9 times out of 10.
I spend most of my free time with housework, socializing and hobbies but there just isn't enough meaningful stuff I care to do outside of working hours to overcome the 8 hours a day of meaningless work I do for my employer.
It’s clear other people are able to manage but I have been trying for years and all I ever manage to get out of it is depression.
I just can't do meaningless work for 8 hours a day.
Before you attempt to do anything, first try to assess whether your organization and/or management has a strong “don’t rock the boat” culture. In my experience, an isolated contributor moving super slow might be down to the individual, but a whole team moving slow is usually due to systemic factors. Attempting to create accountability or meaningful changes to velocity in a “don’t rock the boat” org is usually a one-w…
Your mistake is caring. Are you being rewarded for working much harder than your colleagues? Are they being punished for working hardly at all? Why are you working hard for the benefit of the company's bottom line? It's a big company, why do you care about its bottom line? Your colleagues have the right attitude. They are doing the absolute bare minimum to collect a paycheck and go home. I suggest you do the same. Ca…
I made the same "mistake" this person did. Companies didn't reward me. But you know what? I kept improving, they didn't, and I was eventually able to launch my own company while they stay stuck in that job. Obviously companies should reward us for doing better, but, when they don't it still doesn't mean there's no potential benefit from "practicing" doing good work while at work.
I've also worked with many colleagues who were great at their jobs, but that's all it was for them - a job. Their passions (which was sometimes just their family) lied elsewhere. They were just working to support that and were perfectly happy with their lives. I wouldn't try to take that from them.
How can you be so sure all your colleagues are useless? Are they doing any important but non-flashy work (planning, documentation, cleanup, etc) that isn't captured by the "story point" metric, which is a pretty bad tool to gauge productivity anyway?
You're working too hard. And you're stupid. You set your own high watermark super high, now you can't back it off without getting questions directed at you. At no point in your career is holding your peers to account part of the role of a developer. Get that through your skull quickly. Either find a job where you're under the hammer more and the comp is what you want or learn to live with this. Or work on your own pr…
Cynical take: being this much more effective than their colleagues won't get OP promoted, but it might get the rest of the team fired.
* If you're relatively new, are they giving you starter tasks?
* Are the other team member's tasks harder, less-straightforward, involving less-familiar tech, slowed/blocked by dependencies, less amenable to just crunching through mechanically, etc.?
* Are the other team members doing higher-quality work? (A big corp. might have very different ideas of what software engineering is than you did in a one-person-tech-team startups. Are you a one-person tech debt machine?)
* Do the other team members have more responsibilities separate from this code?
* Is the team in a catch-your-breath period, after a big push to ship something, and people also taking summer vacations, etc.?
* Is there a morale problem going on that you haven't picked up on? Were there layoffs recently? Or do people know something you don't know, like that the project is going to be canceled? Is this a team or company that people want to be in? Is everyone interviewing or practicing Leetcode?
* Why is the tech lead or people manager not on top of this, if it's a problem? (Or maybe they are, but they're handling it discreetly, one-on-one with people, rather than embarrassing people in front of the team?)
These questions also suggest one way to broach the topic with a tech lead or people manager, if you don't yet know whether it's safe to speak more candidly: you could ask how your work is fitting the conventions of the organization, are you blowing through tasks too quickly, is there something you should be doing differently, etc.
Your mistake is caring. Are you being rewarded for working much harder than your colleagues? Are they being punished for working hardly at all? Why are you working hard for the benefit of the company's bottom line? It's a big company, why do you care about its bottom line? Your colleagues have the right attitude. They are doing the absolute bare minimum to collect a paycheck and go home. I suggest you do the same. Ca…
I need a job I can care about or else I struggle to do the work.