| ▲ | whycombinetor an hour ago | |||||||||||||
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? Even when the org was large to have an architect, they just were just a figurehead and designed the original system, and ongoing decisions were made by the dev who picks up the ticket. From that perspective, engineers are still engineers, just without the hands-on-keyboard coding. If that's all your job was, hands-on-keyboard coding with no decision making, yeah you're cooked and need to reskill. | ||||||||||||||
| ▲ | hinkley 42 minutes ago | parent | next [-] | |||||||||||||
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. | ||||||||||||||
| ▲ | rsyring an hour ago | parent | prev | next [-] | |||||||||||||
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. | ||||||||||||||
| ||||||||||||||
| ▲ | jimbokun 19 minutes ago | parent | prev | next [-] | |||||||||||||
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. | ||||||||||||||
| ||||||||||||||
| ▲ | boogieknite 22 minutes ago | parent | prev [-] | |||||||||||||
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 | ||||||||||||||