Live data from Hacker News

Crushing Jira tickets is a party trick, not a path to impact

seangoedecke.com

61–70 of 86 posts

Re: Crushing Jira tickets is a party trick, not a path to impact

#61

Earlier quoted context omitted.

Why are you so conditioned to think that fancier titles and more and more money is the end goal of it all?

I have this insatiable addiction to food and shelter. If I could get over my addiction, not only wouldn’t I care about money, I wouldn’t be working.

Your apparent "need" for food and shelter is a social construct! Get out there! And by "out there", I mean out in the cold!

Re: Crushing Jira tickets is a party trick, not a path to impact

#62

I was given high impact projects precisely because I crushed tickets as a junior. I demonstrated repeated mini-competencies (crushing tickets), gained credibility, then got to demonstrate macro-competency (deliver projects). Definitely agree that "crushed many tickets" is less effective in performance review than "delivered critical project". I'm not sure how one gets to be responsible for a project without first cru…

I suspect this is a very common experience. I don't think that 'crushing tickets' is a good metric of developer competency, but it's a very visible metric regardless and is therefore probably a good way to progress in many organisations.

But only to a mid level developer.

Re: Crushing Jira tickets is a party trick, not a path to impact

#63

Earlier quoted context omitted.

This is what bothered me so much about my last job. Thank you for saying it so succintly

I think it's one of the prime causes of burnout. Feeling like you have no real control over things, but having immense responsibility anyway. Fighting learned helplessness with an internal taskmaster. It's not good for the psyche.

The prime cause of burnout is not saying “no” to being pushed to work extra hours.

You do that by being able to communicate about the trade offs between the holy trinity of projects - on time, on budget and meets requirements.

Re: Crushing Jira tickets is a party trick, not a path to impact

#64

Earlier quoted context omitted.

I can’t exchange “pride” for goods and services. The people that hold the power to give you raises and promotions don’t care about “craftsmenship”

Why are you so conditioned to think that fancier titles and more and more money is the end goal of it all?

Because that's how the entire reward system is structured - ask management why they care about that stuff (money) and you will understand why people do it (money).

Re: Crushing Jira tickets is a party trick, not a path to impact

#65

Earlier quoted context omitted.

I think it's one of the prime causes of burnout. Feeling like you have no real control over things, but having immense responsibility anyway. Fighting learned helplessness with an internal taskmaster. It's not good for the psyche.

The prime cause of burnout is not saying “no” to being pushed to work extra hours. You do that by being able to communicate about the trade offs between the holy trinity of projects - on time, on budget and meets requirements.

I disagree with this. You can burn out when working less than 40 hours. You can not burn out when working way more than 40. It has a lot more to do with other factors, it's just that those factors will burn you out even quicker if you're working too many hours.

I'm incredibly burnt out currently, and I'm consistently at under 40 hours at my job.

Re: Crushing Jira tickets is a party trick, not a path to impact

#66
post #4

> If you ship a project and your management chain begins talking about the next thing, stop improving that project. and this type of advice is precisely why the whole industry completely lost its ability to produce usable things.

I agree with what John Carmack said about that.

https://news.ycombinator.com/item?id=26170052

Re: Crushing Jira tickets is a party trick, not a path to impact

#68

Another way to frame this is to not get too attached to your code. Tmrw it could be the cornerstone to a new line of business or it can be burned in the dumpster.

And this is one reason this industry can be so soul crushing. You're asked to demonstrate "ownership", but at any moment some person above you can take all your work away and make you do something entirely different. Somehow we're asked to care about our work and not care about it at the same time.

A good phrase to remember is “outcomes over outputs”

Re: Crushing Jira tickets is a party trick, not a path to impact

#69

Awesome article about how to get a promotion. Deserves a follow up article for “how software companies should actually be run to avoid promotion seeking behaviors like projects > all else” Most software companies just need 1 (or at most a handful) of really amazing products. Most products are composed of a handful of “projects”. I’ve worked at big and small tech companies where we were so busy building projects for p…

Spotify is one of the worst at innovation. They pushed out the team that made discover weekly by downplaying their pioneering work while executives focused on “health integrations”, and they’ve now laid off some of their most creative people, including the guy who worked on everynoise.com.

I would guess that bloat at Spotify is a direct result of empire building by the numbers.

Re: Crushing Jira tickets is a party trick, not a path to impact

#70

Earlier quoted context omitted.

This is what bothered me so much about my last job. Thank you for saying it so succintly

I think it's one of the prime causes of burnout. Feeling like you have no real control over things, but having immense responsibility anyway. Fighting learned helplessness with an internal taskmaster. It's not good for the psyche.

I've started to think the solution to burnout is to just up and quit your job wherever anyone tries to force you to do anything without a good explanation.

This is obviously not something everyone can do, but if you can, maybe it's worth it.

Post reply on HN