logoalt Hacker News

Fourier864 • today at 8:31 PM • 4 replies • view on HN

It took me several years to realize this wasn't the default. Once I was senior enough to start getting people under me, I would assign tickets like "Scientist Bob would like a better method to view missing data, work with him to develop that over the next 2 weeks", and assume that they, like me, would enjoy the flexibility and the ownership. I didn't care what they came up with; email notifications, enhancing the web tool we have, putting coverage data in our opensearch to query, etc.

After getting complaints, I started getting narrower and narrower in my ticket writing, until I realized many newer software engineers literally want tickets like "modify function x_y_z() in python_file.py so that it also returns..."


Replies

zabriel_goss • today at 8:43 PM

Curious if this is a culture issue or a volume issue.

In the distant past of a couple of years ago, I saw and gave tickets with higher ambiguity and opportunity for ownership and cross-team collaboration. There was breathing room to take that kind of time.

This year, however, as we're all aware, the expectation around speed is much higher. When more spinning plates are added, I want them to be more defined so they can be handled quickly. To be clear, though, I much prefer the former scenario.

rescbr • today at 8:44 PM

Yeah. There are some teams I work with that are exactly like that, and it pisses me off. If I need to write the ticket in such detail then it would be faster for me to write the code myself.

Now with AI coding, it pisses me off even more.

MaKey • today at 8:42 PM

I guess these software engineers aren't needed anymore now.

aerhardt • today at 8:43 PM

Well honestly, those people have reason to be worried...