Live data from Hacker News

Boring work needs tension

iaziz786.com

11–20 of 77 posts

Re: Boring work needs tension

#11

> Your CI/CD takes a huge amount of time because you forgot to leverage caching. The bane of my existence are CI/CD systems that get caching 99% right. Chasing down the problems from that last 1% of strangely busted...well, lets just say that if you want TENSION at work, good way to get it. :/

with github actions... often caching is slow as well

Re: Boring work needs tension

#13
post #9

Earlier quoted context omitted.

Surely it was in jest. Tons of places are like that.

Perhaps tons of places are dysfunctional. Nothing says quantity makes right.

And when it's systemic, maybe you could say the industry has dysfunctions.

Re: Boring work needs tension

#15
post #7

Unless you work on a dysfunctional team and any non-tracked work is forbidden, and any work you try and get tracked requires 6 pages of justification and takes 10 weeks to get prioritized enough for someone to work on...

My team isnt dysfunctional but I always get hit on the head for doing work and not making a ticket. I don't get it, if I see something bad I'm not going to search which ticket would best fit this issue. Just reviw my PR ! Also, so far most of our projects start simple but end in chaos and deadlines on the minute. I feel like we could always do better.

I’ve been on both sides of this equation. If someone is dinging you for doing extra work, it could be a sign that your priorities are not aligned.

Like, if you’ve got a tight deadline coming up, it’s not the time to spend a week making CI slightly faster. On the other hand, if someone is telling you to not do work (right now), then they also need to help be responsible for finding time to do that work and understanding the impacts of that work never gets done.

I explain this to people as the tension between important urgent work. Some work is important but never(rarely) urgent. And if you ignore important work (like maintenance) it might become urgent at a very bad time.

Re: Boring work needs tension

#16

Unless you work on a dysfunctional team and any non-tracked work is forbidden, and any work you try and get tracked requires 6 pages of justification and takes 10 weeks to get prioritized enough for someone to work on...

You have a funny definition of "dysfunctional".

You can either laugh or cry about it. Laughing is more fun.

This is nearly the norm for ENTERPRISE software development, and it's such a tragedy.

Re: Boring work needs tension

#17
post #7

Earlier quoted context omitted.

My team isnt dysfunctional but I always get hit on the head for doing work and not making a ticket. I don't get it, if I see something bad I'm not going to search which ticket would best fit this issue. Just reviw my PR ! Also, so far most of our projects start simple but end in chaos and deadlines on the minute. I feel like we could always do better.

I’ve been on both sides of this equation. If someone is dinging you for doing extra work, it could be a sign that your priorities are not aligned. Like, if you’ve got a tight deadline coming up, it’s not the time to spend a week making CI slightly faster. On the other hand, if someone is telling you to not do work (right now), then they also need to help be responsible for finding time to do that work and understandi…

Also there is value in having an audit trail of who did what when and why, both for operations and system evolution, and for all the compliance junk. Not so much value that a tiny bit of cleanup needs a huge amount of overhead though.

Re: Boring work needs tension

#18
post #7

Unless you work on a dysfunctional team and any non-tracked work is forbidden, and any work you try and get tracked requires 6 pages of justification and takes 10 weeks to get prioritized enough for someone to work on...

My team isnt dysfunctional but I always get hit on the head for doing work and not making a ticket. I don't get it, if I see something bad I'm not going to search which ticket would best fit this issue. Just reviw my PR ! Also, so far most of our projects start simple but end in chaos and deadlines on the minute. I feel like we could always do better.

It takes like two seconds to write a ticket and then tag your commits with it.

You get credit for fixing the issue, avoid giant fix-along-the-way PRs, and future credit for people (maybe even you) understanding why you those changes were made.

Re: Boring work needs tension

#19
post #7

Earlier quoted context omitted.

My team isnt dysfunctional but I always get hit on the head for doing work and not making a ticket. I don't get it, if I see something bad I'm not going to search which ticket would best fit this issue. Just reviw my PR ! Also, so far most of our projects start simple but end in chaos and deadlines on the minute. I feel like we could always do better.

It takes like two seconds to write a ticket and then tag your commits with it. You get credit for fixing the issue, avoid giant fix-along-the-way PRs, and future credit for people (maybe even you) understanding why you those changes were made.

Except then you can get your wrist slapped for starting work on a ticket without prioritization. A rigid enough process slowly kills everything.

Re: Boring work needs tension

#20
post #7

Earlier quoted context omitted.

My team isnt dysfunctional but I always get hit on the head for doing work and not making a ticket. I don't get it, if I see something bad I'm not going to search which ticket would best fit this issue. Just reviw my PR ! Also, so far most of our projects start simple but end in chaos and deadlines on the minute. I feel like we could always do better.

It takes like two seconds to write a ticket and then tag your commits with it. You get credit for fixing the issue, avoid giant fix-along-the-way PRs, and future credit for people (maybe even you) understanding why you those changes were made.

I use MCP for this now.

A crappy form filled ticket by an AI is slightly better than no ticket.

Post reply on HN