upvote
> Am I an outlier in that every SWE job I've had has expected you to push back on requirements and design the data model for tickets you are handed?

Yes, that is how most functional organizations operate.

Architects are a bad meme, along the same lines as scrum masters and product managers. Good software engineers spend more time on design than implementation, and the best are helping their teammates with design, and auditing designs of adjacent teams to ensure integration success. So architecture is an important part of the job, but that doesn't mean that you can automatically declare a role with the title "architect" and make the whole organization do better design.

Architect roles are a bad meme because the architect always ends up knowing less about the system and how it is used than the engineers and support staff, yet they have more influence over the decisions affecting those things. That's the essence of an organizational anti-pattern/bad-meme any time it shows up: influence over resources anti-correlated with decision quality. Additionally, architects often report to non-technical folks fairly high up the chain. Those people are bad at screening for such a technical role, sometimes even making the mistake of replacing an architect with an external hire.

reply
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..."

reply
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.

reply
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.

reply
I guess these software engineers aren't needed anymore now.
reply
Well honestly, those people have reason to be worried...
reply
I would say that I expect senior engineers to have autonomy, and autonomy means not doing strictly what you are told. So if you’re not being told exactly what to do, that means you have to figure it out for yourself. Which leads to steering task direction, which leads to pushback on requirements.

And that’s why junior engineers are fucked at companies that can afford to send all their proprietary information to Anthropic. But since they are public now, they will violate that trust as soon as major shareholders learn to word it so that it sounds like a stranded asset that any responsible C Corp would be expected to rescue. And then everybody’s fucked.

reply
I run a development firm so we've had all kinds of clients and interacted with various external dev teams over the last 20+ years.

You aren't an outlier exactly, but there are way more devs than you are probably aware who are just told what to build and then have to go build it. So they don't have or never developed the consulting, planning, and architecture skills and experience.

The more our clients tend towards wanting a process like that, and the less they treat us like valued expert software consultants that can help shape their solution for the better, the worse the outcomes usually are.

reply
I'm a self-taught woman who started work in agencies doing front-end work, then moving on to progressively more complex tasks, eventually becoming a lead and doing all of the things you mentioned. Your experience maps to mine 1:1. I've had a lot of imposter syndrome and challenges around this, and I had to go through a similar realization at some point in my career. It sort of sucks because I am just not good at being that kind of blinders-on developer. I also mention my sex/gender because I've had lots of borderline offensive assumptions made about me in certain situations related to what you've described.
reply
We call those body shops. Probably because sweatshop sounds overwrought if you know what those are actually like.
reply
deleted
reply
If the new Engineers are making architectural decisions without a guiding Principal then it's a new job.
reply
I'm seeing the Architects who only ever handed off a design based off of requirements to the dev and never implemented anything is equally cooked, in a different way.

There's really no sense in handing off the design to a dev to implement, who just copy pastes it into Claude's prompt. The "Architect" now needs to be fully responsible for what goes into production, instead of being able to blame some poor dev who faithfully implemented a flawed architecture design.

AI is flattening architecture and development into a single role.

reply
We used to call that role a Software Engineer.
reply
counterintuitively, i push back less now that im worried about standing out as "in the way of progress" when management is telling me to push their client manager nephew's vibe code to main
reply