News for hackers. Stuff that matters.
Re:We promoted developers into architects without informing ... by Fourier864 on Friday November 20, 2026 @03:31PM (#50581570)
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..."

Re:We promoted developers into architects without informing ... by MaKey on Friday November 20, 2026 @03:42PM (#50581754)
I guess these software engineers aren't needed anymore now.
Re:We promoted developers into architects without informing ... by zabriel_goss on Friday November 20, 2026 @03:43PM (#50581771)
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.

Re:We promoted developers into architects without informing ... by rizzom5000 on Friday November 20, 2026 @04:53PM (#50582796)
It's cultural from what I've seen. Especially where development time is micromanaged, story points mean minutes and hours and estimates are put under a microscope. In short, low trust environments where managers have never developed software and probably have no idea what is going on i.e. situationally unaware management.
Re:We promoted developers into architects without informing ... by aerhardt on Friday November 20, 2026 @03:43PM (#50581774)
Well honestly, those people have reason to be worried...
Re:We promoted developers into architects without informing ... by rescbr on Friday November 20, 2026 @03:44PM (#50581783)
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.

Re:We promoted developers into architects without informing ... by teiferer on Friday November 20, 2026 @05:30PM (#50583271)
In my experience, that is still a little shortsighted. If you actually end up giving up and "just do it yourself" then you can often end up spending lots time with a long tail of fallout this entails. Suddenly some tests failing, some other team unexpectedly getting disrupted by your change and having to follow up on that and dealing with them, some follow up requirements revealing themselves... It is all those things that you are only on the hook for once you actually do it that often makes it worthwhile to instead dump all your thoughts into the ticket and then let somebody else do the grunt work, LLM-assisted or not. And it should add some humbleness to the attitude you just expressed.
Re:We promoted developers into architects without informing ... by theamk on Saturday November 21, 2026 @01:29AM (#50586575)
[delayed]
Re:We promoted developers into architects without informing ... by dalmo3 on Friday November 20, 2026 @04:57PM (#50582858)
> work with him to develop

Woah, no designer, no BA, no PO, no SME, no legal? I'm envious.

Aside, I've been thinking of the "reverse Uncle Ben": With great responsibility comes great power. Or should come. I've seen places where ICs were expected to "own" the work, as you mentioned, except they had no autonomy to actually make decisions, those would come by committee or from above. No wonder people didn't want the responsibility.

Re:We promoted developers into architects without informing ... by nomel on Friday November 20, 2026 @05:18PM (#50583119)
I've seen the opposite of that, too. In one position, I was told that results don't matter. It's the planning and process, presented through meetings, that everyone wants to see. Taking full responsibility, working with the actual people the work was for, directly, and delivering on time and with minimal issues during testing, giving them exactly what they wanted, with everyone actually involved happy, wasn't all that important.

Burned out from the misalignment of purpose of my work I couldn't stomach, then moved on.

Re:We promoted developers into architects without informing ... by weitendorf on Friday November 20, 2026 @05:03PM (#50582924)
I think this is definitely a very common experience. What makes it such a whiplash is that you're actually both at the beginning of a rather steep learning curve, but are only just becoming aware that the learning curve even exists / reluctant to consider the implications because of the impact it would have on your existing world model.

For inexperienced engineers it's that "your job is figuring shit out, not typing the code in", which for some people is like telling them that their dream job doesn't exist/the mental model most of their peers operate under isn't true.

For a manager it's that you can't really assume that everybody has the same personality/relationship to work/experience as you do, and that you might have even forgotten what it was like to be in their position, or not noticed how different some of your colleagues were from you. Which is also like telling them, "it turns out the best manager for your team is not the one you would want for yourself, and this job is going to be very different from what you thought".

I think it's very important to have a large enough sample of non-reporting colleagues across the range of experience. It helps you passively form a model of what normal career and even just life development looks like, and when you're in situations like this where you're not sure whether you're the asshole, or the other person is, or just confused, you can kind of in retrospect see how the near-peer may have navigated the same thing. Including business people. Our job is to add enough value to someone else's life that they're willing to pay us to stick around.

Re:We promoted developers into architects without informing ... by onthrowaway457 on Friday November 20, 2026 @05:17PM (#50583107)
Similar. As a PM I try to learn how much direction each person is cool with in this moment of the career. I don’t mind specific details if the person needs them, but I love it when the dev knows the domain, the problem space, etc and we talk about outcomes and capabilities then off they go, driving the momentum and making recommendations about scope reduction or additional features that I’d never have thought of in advance. Then I’m mostly breaking ties and figuring out the next important thing to build.
Re:We promoted developers into architects without informing ... by rootusrootus on Friday November 20, 2026 @08:13PM (#50584742)
Yes this has been a long time irritation for me. By the time I spec the feature to the degree these juniors require, I could have just done it myself. When I try to raise the level they work at, they just fall back to asking me incessant dumb clarification questions, refusing to take any ownership. No matter how often I have coached them on what the expectations is.

And now, I'm trying to get them to understand that if they persist in just being basic coders, they are shortly going to be replaced with an LLM.

Re:We promoted developers into architects without informing ... by socalgal2 on Friday November 20, 2026 @10:03PM (#50585489)
The problem for me is other people’s code. I don’t know what they want or what they will approve so I can’t just give them a solution that they’ll disapprove of. Having enough rejections leads to “tell me what you want me to type so that you’ll approve the pull request”
Re:We promoted developers into architects without informing ... by antonvs on Friday November 20, 2026 @11:11PM (#50585861)
> many newer software engineers literally want tickets like "modify function x_y_z() in python_file.py so that it also returns..."

...which makes them very replaceable by a coding agent.