We promoted developers into architects without informing them

(manidoraisamy.com)

517 points | by QueensGambit 21 hours ago

67 comments

  • whycombinetor 20 hours 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.

    • alphazard 19 hours 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?

      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 better at 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.

      • spiralpolitik 17 hours ago
        Good architects delegate down and are there to ensure the big picture remains consistent while leaving the teams to sweat the details because they are closer to the problem.

        Bad architects try to micromanage and those are the cases where you end up with systems that are slow and unworkable with processes that have too much ceremony.

        • mordae 3 hours ago
          Truly horrible architects tour conferences, make their orgs purchase unnecessary proprietary tech stacks sold at those conferences and then force new projects to utilize them, adding busywork both while adding support and then ripping it out once it is clear that 90% of the stack won't even support that cringe proprietary tech that's out of fashion the next year.

          They also say stuff like "Dont't even joke about using PG. We've just sunken $xM into Oracle licenses and HW and it would make us (me) look bad."

          • philipallstar 3 hours ago
            This is a totally different type of architect, the "enterprise architect".
        • lokar 16 hours ago
          When in that role I focus on supporting the team. Mentoring, resolving disagreements, providing broader context, suggesting more options to consider (often stuff we could copy from older systems), etc.

          The main area where I spend influence on really shape the outcome is on process and team culture, not any specific technical decision.

          • wreath 10 hours ago
            Thats a technical lead,no?
            • lokar 56 minutes ago
              There is a lot of overlap, at least there should be.

              The goal is to steer the high level design of the system over years. You could do it by dropping docs on people with little interaction (arch by decree), or you could steer the teams and people. Help them get to the right answer “on their own”.

            • imdsm 4 hours ago
              Yep. Most people had job titles that didn't fit their roles, and then assume that is what those positions meant. I've had people tell me they're architects and they were middling devs at best, but everyone is limited by their own ceiling
            • szundi 5 hours ago
              [dead]
        • cebert 16 hours ago
          I really hope AI eliminates enterprise architect roles. It is uninspiring to get direction from people who don’t do anything or build anything.
          • hdgvhicv 5 hours ago
            AI will allow them to implement their vision without pushback and complaints.
            • raffraffraff 3 hours ago
              Absolutely. I've seen Claude polish turds really really shiny.
              • ffsm8 2 hours ago
                I've also had coworkers produce garbage and then be totally proud of it.

                may not be related to the way it was developed and more about the perspective of the person looking at the code

            • LtWorf 2 hours ago
              I'm sure they will blame all the inevitable issues on the AI.
          • theK 16 hours ago
            I think it won't. At least I don't see how.

            AI still doesn't really teach anything on the org-dev level. Organizations that where dysfunctional in the past will keep growing these structures only that now the complexity will increase much much faster because teams can do (vibecode) so much more.

          • rat9988 7 hours ago
            The agent won't complain about being uninspired, so I guess it is your role that is going to be cut while he just gives the direction.
        • suzzer99 16 hours ago
          Bad architects insist you add things like websockets because they already put it in the Powerpoint.
        • passwordoops 2 hours ago
          Bingo. Same thing with product managers. My worst experiences as a PM were when my boss insisted I had to call the shots on every technical decision... Like, bro if this is how you've been operating all these years maybe there's a reason the stack is a complete disaster? Leave the engineering to the engineers, we're here to make business-level decisions and ensure the product works as intended.

          Unfortunately, that seems to be the general direction product people took... Glad I'm out

      • monocasa 19 hours ago
        I've always treated the architect role as more setting broad goals, defining boundaries for individual ownership, and technical dispute resolution. Sort of what you see with a lot of directors of movies where you get the best work by empowering individuals to completely own a carefully built little box that is a brick in the larger work.

        Those could be done by normal management, but I've found it better to separate those discussions from management style discussions. Sort of like how the BDFL role in a large open source project is rarely anyone's actual boss.

        Albeit, I'm still recalibrating what all this means in an agentic world. It makes sense with the little swarm I directly command, but the pressures for downstream ICs to ignore the art and taste of what they're doing is more than a bit unfortunate since the core of what I'm saying is to empower them to give a shit and be proud about what they built.

      • benji8000 17 hours ago
        > architect always ends up knowing less about the system

        I guess that depends. In automotive, at least in my case, the SW architect on our team knows so much more about how our SW module interacts with the overall system, it's almost awe-inspiring. My guess is, they have all this knowledge because they're continuously interacting with other architects and teams to talk about the big picture.

      • jeremyjh 16 hours ago
        A lot of organizations don't know how to hire and task architects appropriately. I had the same opinion until I worked in an org where they actually functioned the way you'd think they should. Then I saw the chief architect's name in a 20 year old commit. They had no idea how to hire new ones, but they'd figured out how to grow and task them, which is a good substitute.
        • mmsimanga 1 hour ago
          That is about the only type of useful architect. The ones who worked on the system in the past and understand the system and product. Bringing in someone from the outside with no knowledge of the system is the reason many devs don't think much of architects. You spend most of the type explaining the system to the architect.
          • jeremyjh 1 hour ago
            They don't need all the same knowledge of the developers, but they need relevant domain knowledge, they need to know the existing systems architecture and an outsider is always at a disadvantage to senior developers who are also quite often very good at architecture.

            In a Service-Oriented-Architecture it is important that the service boundaries are controlled by someone without a feudal stake in the implementations. But probably the only architects who could come into a new org and do that would be ones who grew up in the same domain in a different org.

      • theK 16 hours ago
        > Architects are a bad meme, along the same lines as scrum masters and product managers

        I think it says a lot about our culture that, even though xore agile literature and practices like XP and DX have again and again shown what works, the IT world stubornly keeps gravitating towards taylorian structures.

        • antonvs 11 hours ago
          > the IT world stubornly keeps gravitating towards taylorian structures.

          A big reason is that they're always trying to hire the cheapest possible developers, with corresponding skill levels, so a big part of the architect's task becomes to try to impose some sanity on the collection of issues that result.

        • sjpb 16 hours ago
          What do you mean by "taylorian structures" please?
          • theK 16 hours ago
            My notion here is that Taylorism's defining principle is the separation of conception (planning, design) from execution (doing).
      • andrekandre 14 hours ago

          > 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
        
        preach brotha!
        • sirsinsalot 2 hours ago
          I feel like this is repeated by people who've not seen these roles done well. I have, and good product managers, scrum masters and architects can be worth their weight in gold.

          Most of the time I see these roles not operating well, the same way any role can suffer incompetent middling behaviour. There's plenty of terrible SWE as well.

          As a lead developer I'd take a good product manager, scrum master and architect in a heart beat. A bad one, never.

      • jameshart 11 hours ago
        All software development is architecture. Decide to implement a change by adding an if block to some code, by adding a function, by creating a new module and implementing it there, locally in the browser or on the server… those are all architectural decisions.

        Large scale software development is just a nested series of architectural choices from top to bottom.

        That some organizations choose to give some software developers the job title of architect is not a ‘bad meme’, it’s a reaction to the realization that there’s a lot of architectural decisions being made and it might be nice if all the people making them had sufficient information to make them right.

        Good ‘architects’ focus on making sure developers who are making all those architectural decisions have the right context to make them.

        Bad ‘architects’ try to make - or preempt, or second guess - all those decisions that have to be made. That doesn’t scale and doesn’t work.

      • mschuster91 14 hours ago
        > 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.

        A good architect is IMHO someone who can get the bullshit out of your way. Think like interfaces with third parties (or even other departments at your average megacorp), it certainly doesn't hurt if someone else has both the awareness and the technical knowledge about dependencies I have or others have on me, and can take care of dealing with the associated bureaucracy.

        (And no, that's not a PM role because most PMs can't tell JSON apart from XML...)

        • com 1 hour ago
          A good software architect isn’t appointed. They are raised on the shields of their colleagues, like battlefield Roman emperors.
      • mepiethree 12 hours ago
        I’m sorry you’ve clearly never worked with a decent product manager
    • alibarber 1 hour ago
      Reading this thread has been music to my ears because I really have almost been having a crisis of late with people forever banging on about "AI is doing all the software and whatever", and I have always been of the opinion that the software isn't really the core part. Sure it's important to do it right and have pride in your craft, but actual work for me has always been, 'go and find people with interesting problems and help them solve this problem and make our company money in doing so'.

      I've literally worked in feature film production, spacecraft, and now optics and medical device industries. My education was in straight computer science - but my opinion is that it behooves you to basically be learning from other people all the time and bringing your ideas to the table, and you're paid to help the company succeed at a high level. I always called myself a software engineer because that's what I felt most formally confident at, but honestly I don't think my day-to-day matches what other people mean by it.

      • javiramos 1 hour ago
        This is what I consider the right mentality
    • Fourier864 19 hours ago
      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..."

      • weitendorf 18 hours ago
        I think this is an underratedly common experience. What makes it such a whiplash is that you're probably both at the beginning of a rather steep learning curve, but only just realizing that learning curve even exists. And 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.

        Same goes for interacting with enough non-developers and business people/customers/higherups to get some about the purpose of your role. Your role is downstream of what you do for them.

      • rootusrootus 14 hours ago
        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.

      • rescbr 19 hours ago
        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.

        • teiferer 17 hours ago
          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.
          • theamk 9 hours ago
            The problem with those kind of people is you spend your time writing out detailed tickets and _still_ have to deal with the long tail of fallout.

            Because if someone requires instruction on the level of "modify function x_y_z() in python_file.py...", then it's highly likely they won't be able to fix the failing tests without making things worse, nor would they able to address to other teams' concerns.

            In the less extreme cases, people might be able to do follow-up work, but since they do not understand the reasons for the design, they won't be able to do it properly. Eventually system will become so wrong, it will fail, and you will again have to spend lots of time studying how it evolved and writing those super-detailed tickets.

            Still, is it worth delegating the tasks? Before the AI, the answer was yes. Sure, you might be losing time by delegating simple tasks, but the other person is getting more experienced, and there is a chance they might become a proper software engineer. With AI however I seem to see some people just stop learning new stuff, being a human AI wrapper, which is very troubling.

      • necovek 6 hours ago
        I think this comes up when both engineers and their managers are asked to estimate and measure — against all of our collective wisdom going back to Mythical Man Month.

        Your example is great, but if you also ask an engineer when can that be done, they need to already work out the approach, analyse any gotchas, maybe even build a PoC — easily taking 50+% of the effort to give you a response.

        This is more of a comment on the industry as a whole, but your approach is the sweet spot IMHO: do something that fits in two weeks.

        This encourages people to figure out small incremental steps that leave less important stuff for the end — as they probably won't get done — but not everybody is fine with this open-ended approach. Because taking ownership also means assuming accountability.

        • yurishimo 4 hours ago
          Maybe it’s just because I hold a “senior” title but this seems like the logical result of a career as an engineer. You start with small tasks and are gradually asked to assume more responsibility as you gain knowledge about the system and demonstrate your competence.

          If someone never shows that initiative though, I’ve never known a manager to push them more than once or twice. Eventually everyone in a team finds a rhythm that produces some amount of forward momentum and that status quo stays until someone decides to shake things up again. The shake up might not even be big but it also doesn’t have to be world changing.

          I’ve had to recognize this in myself over the years. If I want to have more responsibility in most western organizations, I need only reach out and take it. Everyone has exactly as much work as they want (which for some people might not be very much at all!) and once that clicked for me, I stopped letting the acts of others at work control how I feel about my own performance or output.

          To tie it back in, I personally see those small steps of tasks as the ladder towards responsibility. But if someone has never climbed a ladder before, it’s important to remember that climbing is exposing them to a new level of risk that everyone will respond differently to. Some people like taking risks! And they are often rewarded for it, but I can also respect someone who responds to that risk differently.

          • zeryx 3 hours ago
            Why bother hiring the people who are so responsibility adverse? Why not only hire people like you?
      • SkiFire13 5 hours ago
        > many newer software engineers literally want tickets like "modify function x_y_z() in python_file.py so that it also returns..."

        These aren't software engineers, they are just people that know a programming language syntax.

      • socalgal2 13 hours ago
        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”
      • dalmo3 18 hours ago
        > 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.

      • zabriel_goss 19 hours ago
        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.

        • rizzom5000 18 hours ago
          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.
      • MaKey 19 hours ago
        I guess these software engineers aren't needed anymore now.
      • onthrowaway457 17 hours ago
        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.
      • aerhardt 19 hours ago
        Well honestly, those people have reason to be worried...
      • antonvs 11 hours ago
        > 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.

    • hinkley 20 hours ago
      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.

      • perlgeek 2 hours ago
        This isn't the default, but there are other ways to employ and train junior developers. What we try to do is to give junior developers more autonomy, but not within our core product.

        We develop an internally-used information system (think of like a CMDB, some automation around it, plus some other parts that aren't typically part of a CMDB, like employee timesheet). There are semiregular requests for automations at the edge, for example a non-technical user might need to create several hundred objects, and there's no existing tool for it, but there is an API. We could task the junior developer with writing a tool that does an excel import and creates the objects through the API. Stuff like that.

        They can then decide if they just write the tool, or also talk to the stakeholder and get some feedback and/or suggest different file formats that work better for this application, and so on. Plus they develop experience with our API. They also get feedback through code review.

        When that works well, we try to bring them closer to the core business logic. There they have less autonomy at the start, but it increases when they show good judgement.

        This might not work for everybody, and we certainly wouldn't have enough work to employ three juniors with such tasks. But in our niche, it's successful.

        • hinkley 11 minutes ago
          In the projects I run this way, it’s modules rather than programs. A good architecture doesn’t just isolate responsibilities (SRP) it also isolates complexity so that the majority of developers aren’t digging next to the fiber trench, as it were. Certainly read and trace that code as you will, but if you need to touch it for your story then we fucked up in Planning because we shouldn’t have given you that story yet.

          It’s a better way to get a bus number of three for the mission critical parts of the code and let the rest go higher, and reduces bottlenecks in the backlog. It was in part a reaction to how poorly I saw Gantt charts behave in practice. I felt it was better to remove the obligation to use them rather than to keep tolerating the farce.

      • hdgvhicv 4 hours ago
        AI will be enshittified yes. But even if it wasn’t, there’s still a. Problem. AI eliminates the inexperienced juniors, where do next replacement seniors, architects etc come from?

        AI is great when you know what is needed. But even if squeezing some more juice doesn’t happen, even if capabilities improve, and somehow the economy doesn’t collapse, the utopian world will be far more idiocracy than Star Trek. AI may run the world in a fairly benevolent way but the population won’t have a clue what to ask for, or be able to anticipate the problems their requests make.

        Or perhaps enshittifation destroys the AI world and everyone moves on.

    • sdevonoes 18 hours ago
      In 15 years of career, I have never seen or worked for a place that had only “coders” (people who were just typing code and not thinking or pushing back or giving their opinions about tech and product).

      So whenever i hear that coders are out of job because of AI, I always wonder where were those “coders”. Never met one

      • hibikir 13 hours ago
        This exists on certain large companies that rely on very cheap labor, ofter overseas contractors. You have 2 or 3 people who understand the system and are actually trying, and people who want to communicate via jira tickets, and care little about whether what they are doing helps the company in any way, or has wide repercussions. In those companies, a Claude agent is still cheaper, and more reliable.

        At good firms that try to pay competitively, of course this doesn't happen much at all. But yes, it's unsettling to get to work, and have someone tell you that what they want is 3-4 well defined tickets that they'll write in the next two weeks, and don't want to engage even a little bit more.

      • marssaxman 17 hours ago
        That was the role Microsoft seemed to expect of me, back in 2008-2009. Here's the spec, go type in the code, the suitability of the design is not your concern.

        I did not like that very much, and did not stay too long.

        • steelframe 11 hours ago
          I was there during that same period of time. What you experienced was largely due to the PMs wresting control of the company from the engineers under the direction of Ballmer. The result of that was Windows 8.

          I recall sitting in an all-hands once where the engineers were bleeding out their eyes about the abomination that was the new start screen, while the head PM just kept repeating, "This is the right decision. WE HAVE THE DATA."

          • antonvs 11 hours ago
            My headcanon is that the reactions to Ballmer's monkey dance and "Developers, developers, developers!" pissed him off, so he started to look for ways to make them less important.
      • 43920 14 hours ago
        I've worked at one or two places that were like this, where I was expected to just do what the ticket said and not push back on anything. Thankfully, it's not too common, and most places I've been at seem to be pretty receptive of ideas traveling upward from individual developers to management.

        Separately from that, pushing back is often uncomfortable and unrewarding. Even in places that do expect developers to have autonomy, it seems like there's usually some people that choose to just follow directions because it's easier and there's no consequences for doing so.

      • switchbak 18 hours ago
        I've worked with folks who seem to identify as that being their job - but I don't think anyone ever wanted them to work that way.

        Rigid roles are a reflection of a human desire to put people in tidy boxes, that doesn't mean those boxes map to reality in a useful way.

        • Pokepokalypse 10 hours ago
          After you've worked at large companies (who tend towards defined roles: tidy boxes), and small start ups where - you do what needs being done; sometimes that even means a coder is doing demos to potential customers, or even investors.

          It's a sharp contrast, and a weird contrast, and in the latter case, you're constantly challenged, constantly finding yourself outside your comfort zone, learning your limitations, what you like, what you dislike. I'm really really glad I didn't end up landing at a large company like I used to work (Symantec). Some people like that structure. I can't stand it.

      • duskdozer 7 hours ago
        The word "coder" here didn't really have that same clear meaning to me, although it's right. If I ever heard your last sentence, I heard it the same as replacing "coder" with "software developer" or pick the synonym
      • onion2k 17 hours ago
        The belief is that prompting AI for some code gives you good architecture as well, because the AI magically knows what you aren't telling it. Or, maybe more generously, because a good vibe coder will give the AI a prompt that includes enough to derive what the architecture should look like.

        If your use case is very ordinary it does work that way. It's only at the bleeding edge or in a weird edge case that performance or optimization stops being a problem you can solve by paying for a bigger box. The performance rarely matters for a SaaS CRUD app until you hit a scale where you've got a team of experienced devs, so most people vibing their next 'unicorn app' don't care.

        • spiralpolitik 16 hours ago
          The AI has been trained on what the statistical common practices are. In most cases these are the best practices. What the AI lacks is the ability to spot the cases where the best practices don't work or need tuning. That's where experience comes into play.
          • necovek 6 hours ago
            I think that differs between ecosystems. Eg. having done a lot of Python, I find that common practices and common idioms work for "scripting", but not for software you want to be evolving and maintaining over years.

            Eg. some of that flows into Python proper (see eg lazy imports), but with the amount of Python code, I believe LLMs will continue offering suboptimal, non-engineering Python for the foreseeable future, and prompting them to do otherwise is an uphill battle.

            I believe similar holds for JavaScript — incidentally two of the most popular languages in the world.

    • rsyring 20 hours ago
      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.

      • CSSer 20 hours ago
        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.
      • hinkley 20 hours ago
        We call those body shops. Probably because sweatshop sounds overwrought if you know what those are actually like.
    • denkmoon 15 hours ago
      When I was a SWE at IBM, Architect was a serious seperate role. There was no scope for me to design the solution - if something didn’t work I could provide feedback to the Architect but only they could change the design. I took a word doc and turned it into code, that’s it.
    • mnahkies 6 hours ago
      Every job I've had has also followed this way of working, though I did get a bit of a peek into an org that did not work in this way.

      As best I could tell in that org the tickets were highly detailed and rigid - data model, API calls (both interfaces and expected external calls) with technical product manager and tech lead basically creating these. The rest of the team then seemed to just be plumbing/following the script. I only got a brief glimpse so it's possible that I got the wrong impression, but it felt jarring.

      Agree that anyone working in this way should be looking to make a change, as it's really not a leap for those tickets to be implemented autonomously now.

    • orwin 6 hours 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

      No, but AI and overzealous juniors made this way harder to argue about overengineering, technical debt and bad/hard to handle architecture. Plus our team manager/PO changed a year ago for one who really like 1 on 1 calls, so that you learn about the new hire is working on during the daily. The stuff you argued during your own 1 on 1 call was a bad design.

    • rtkwe 12 hours ago
      The division at my current job in the data and reporting world in fintech is architects get involved at the highest level on new projects or new patterns, basically strategic decisions approving novel implementations or doing POCs on them. Then down at the team level you have the tech leads and individual SWEs making decisions on how to build individual requirements.
      • bonesss 5 hours ago
        If you have a broad product portfolio, and don’t want silos recreating the wheel at every opportunity, and want to extract synergies and re-use from concurrent efforts, there needs to be a reconciliation and alignment of tasks, task execution, and technology decisions… that is more than just development and involves planning and coordination.

        In the real world you have mechanical, civil, electrical, and structural engineers who need collaborative and clear points of interface and agreement. That and coordination of individual deliveries and customer need mapping, are what Architects do.

        The title is misused in many software contexts, but the fundamental job is real, and necessary, and profitable.

    • brightball 18 hours ago
      In 25 years I've only worked 1 place where there were truly architects handing structure down the chain and people were expected to just implement it...and it was a train wreck of an environment.

      Every good place I've ever worked, the teams doing the implementation itself discuss it and agree on it in conjunction with some higher lead ensuring that there's no red flags to the implementation. If you're handing things down from on high, you're sending a lot of signals about what you think about the ability of the rest of your team...and none of them are good.

    • jojogeo 18 hours ago
      The way I've always seen it in my mind; "hands on just doing coding" work is a Developer, and actually thinking about a problem and requirements etc, and composing a specification => code to solve a problem is Software Engineer.

      Tbh I've always hated the developer role, they tend to be ticket bangers who don't give a shit about what they produce; as long as the sprint targets are achieved, (who gives a shit if a tonne of bugs come back in the next sprint(s) eh?).

      • Scarblac 18 hours ago
        I've been programmer, developer, software engineer, they were all exactly the same thing.
        • jojogeo 17 hours ago
          Depends on the org IMHO; I've always found that Developers appear in large quantities, usually hired from a "low cost economic zone", and are only interested in banging out code to achieve the stated goals in the JIRA tickets.

          No independent thinking, no "Actually it would be better if we did X", they simply translate someone else's requirements into code which (allegedly) meets those requirements.

          I agree though that the definition is vague, and orgs use the terms interchangeably. If you can't see the difference, then I'm sure that you're an excellent engineer and on the SWE end of the scale :)

    • omgwtfbyobbq 9 hours ago
      Totally normal. I wouldn't say that architects were figureheads, but for the most part they did the majority of their work standing something up. Once it was running, system architecture was done by a mixture of developers, analysts, and business folks based on needs/wants and the reality/practicality of the system.

      To be fair, I've also seen some pretty bad decisions by original architects/developers, although it's easy for me to criticize in hindsight.

    • Aurornis 18 hours ago
      > If that's all your job was, hands-on-keyboard coding with no decision making, yeah you're cooked and need to reskill.

      I didn't understand this framing where a person is either a coder OR an architect, but not both, until I ran into a company that operated this way.

      All of my jobs expected software developers to make and own their decisions, as well as ship at least some code related to the decisions they made.

      The first time I encountered the coder-OR-architect separation was at a company that hired way too many people and held way too many meetings. They separated every responsibility out into different roles and then assigned those to different hires. There were so many roles that they couldn't even correctly identify the right boundaries between, for example, the Product Manager and the Product Designer, or the Project Manager and the Program Manager and the Engineering Manager.

      The most surprising thing was how many people at that company liked it that way. The product managers liked writing up PRDs and then making them someone else's problems. The architects would translate those into big documents, then it was someone else's problem. The project managers would do elaborate ceremonies to turn them into tickets which became the coder's problem. The coders took the tickets and wrote enough code to close the ticket, then it became someone else's problem. Eventually the end product became the customer's problem.

      I could see how comforting it was. You could settle into a constrained role and, as long you dutifully produced the artifacts of that role, it then left your plate and became someone else's problem. No one person held enough of the responsibility to be accountable for anything, because you could always point up and down the decision pipeline at someone else.

      I think these people actually love AI, because it's yet another tool to defer work and responsibility to. They're the people who now point to Claude when something breaks, saying they'll get right on to having Claude fix it. It's one more step in the handoff pipeline and separation of accountability.

    • trentnix 18 hours ago
      At one of my previous gigs the CTO would, in one meeting, bemoan that none of the engineers were willing to make decisions and, in the next meeting, cut your knees out from under you for trying. Even today that same CTO is still in charge and his engineering team is still, for the very same reasons, unable to ship anything.

      I'm very grateful that I'm now in a position where not only am I given as much rope as I'm willing to pull, it's expected of me.

    • markus_zhang 12 hours ago
      It depends on what “architecting” means. In all companies I worked for, the fundamental architecture rarely moved. I added pieces or swapped pieces out, but we rarely made big, substantial architectural changes.

      But if architecting means making decisions for anything, like how to approach any ticket, then yes we very often made decisions.

      I had trouble aligning with the second definition and that was probably the reason I bombed a final round previously. The hiring manager asked what is my architecture experience, and I answered that we have principles and staffs so they usually architecture stuffs and we built on top of it. Apparently I should just boast about my 1000 “architecture” experience.

      My understanding of architecting is very narrow —- only company level design is architecting to me —- for example designing the whole data platform is architecting to me.

    • Fr0styMatt88 18 hours ago
      My jobs have always been the same, except maybe the first entry-level job I had out of uni. Even then, while I might not have been driving major architectural decisions, there was definitely _always_ the element of requirements gathering, verifying, etc. Never had a job in which someone has said "This is how it is to be done, no questions". There's _always_ questions even with formal requirements.
    • mshish 18 hours ago
      Agree, regardless of your engineering level, you need to own the security/performance within the scope of your change / ownership. Without that ownership, we're back to the old days where we ship things without caring about how they operate. I don't think that's where agentic coding tools are taking us.
    • bluegatty 19 hours ago
      If the new Engineers are making architectural decisions without a guiding Principal then it's a new job.
    • sanderjd 19 hours ago
      Yeah agreed, I have not experienced this as a change in my job expectations, I just have different (better) tools now. It would have been a change if this hit during my first or maybe second job, but not for a very long time now.
    • boogieknite 20 hours ago
      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
    • jimbokun 20 hours ago
      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.

      • 0x445442 19 hours ago
        We used to call that role a Software Engineer.
    • LtWorf 2 hours ago
      I had an architect with 2 years of experience as a developer.

      Needless to say we completely ignored him and just spoke to the product manager and created our own tickets.

    • ratelimitsteve 18 hours ago
      I always thought of myself as a subcontractor under a GC. It's his job to make overall decisions, build blueprints, shit like that. It was my job to know the vagaries of plumbing well enough to either build what he told me to build or be able to articulate a really good reason why I can't. I might be the plumber one day, the drywall guy the next, the electrician on day 3, etc. Now with the LLM's help I'm the plumber for two hours, the drywall guy 'til lunchtime then I come back and I'm the electrician.
    • whoanoway 18 hours ago
      [dead]
  • nixpulvis 20 hours ago
    I strongly believe good software teams (very rare) require members to play many roles. Sometimes you're a PM, sometimes you're an architect, sometimes you're the systems engineer. Enough people have enough context on the bigger picture that it's stable and there's a shared vision.

    More often than not, one person does the majority of this, and does their best to break up the responsibilities. A good CTO does that at the top, and it flows down through the ranks depending on how big the org is. Perhaps it's just a CTO and 5 engineers, perhaps it's a CTO with 5 divisions, each with 10 groups, with many teams.

    Flatter structures of engaged members works best from what I've seen, but you need to have a critical mass of people not only willing to take initiative, but empowered by leadership.

    • markus_zhang 12 hours ago
      Some people are not interested in some roles. I feel so disgusted trying to get the exact requirements from a stakeholder that I really hate my job. I’d argue it’s also a very bad use of my ability. It’s a lot easier to train someone who vaguely knows what they want to clarify what they want, then someone who doesn’t know what others want to clarify what others want.

      I don’t hate the PM role but some stakeholders are so…ah don’t want HR to find me here, right?

      The more I play this game the more I want to squeeze into lower level programming careers where stakeholders are more technical.

      • Gareth321 3 hours ago
        I greatly sympathise, but I caution you that I think coding only roles are disappearing. Increasingly, time with stakeholders to translate requirements and help with change management and onboarding is becoming the valuable technical skill. I think we’re about to see a lot of very unhappy developers in the near future.
        • markus_zhang 2 hours ago
          I do agree with you. Honestly I’m doing OK despite my reply above. Everyone is friendly so as long as I can deep breathe and explain things face to face, it’s good enough. Plus the pay is better than average. I consider myself lucky. But if the revenue doesn’t turn around, they are going to lay off a lot of people next people AfAIK.
      • toenail 9 hours ago
        Have you told any of this to your manager, or are you just suffering in silence?
        • markus_zhang 2 hours ago
          Yes we know about that, but there is not much to be done here. This is not a company that switching careers is easy because we are not hiring anymore, except for sales. This is a company that awaits someone to buy it (but couldn’t find one).
  • bikeshaving 20 hours ago
    I’ve found that the “job” of using AI is mainly foible management. What the author describes here is a habit of coding agents to excessively use and create logging infrastructure, and sloppily leave it in production code even when unnecessary. For instance, I created an IPA IME keyboard (https://ipabet.org/), and I found in review that Claude would leave the debugging tooling around unflagged, which essentially made the program a key-logger.

    These foibles come and go: early Claude Code refused to let programs crash, mangled all the comments in your codebase, and then one week you find that it insists on ending all functions with `Of` as in `layoutOf()`, `viewOf()`. Finding and mitigating these annoying habits becomes part of the job. Code review becomes articulating with this entity why certain patterns in the code are silly and should be changed.

    The author mentions performance and security issues as the domain of “the architect.” For performance, I’ve found that Claude Code has more or less solved this domain, and can profile and optimize code across a variety of stacks and languages using sophisticated, ad-hoc workflows. For security, it’s just an ever-ending nightmare where random habits and sloppy implementation create random vulernabilities, compounded by the fact that Anthropic has added “safeguard filters” whenever you naively say you’re looking for them. Nevertheless, I’m not sure the architecting role as they describe won’t be automated in the near future.

    • weitendorf 18 hours ago
      I would be cautious deferring to LLMs' judgment in long-horizon architecture or the more procedural, threat-modelly/incentives side of security, or any other large scale judgment calls, because they simply have no experience with them.

      RLVR in these domains (which I think is mostly synthetic end to end, including grading) is turning them into Idiot Savants so jagged in understanding and performance that they defy human expectations for what kind of knowledge and behavior correlate (causally). A human engineer superhuman at hill-climbing low level performance would be at least 95%ile at at general architecture, since they're the same problem just at larger and slower scale.

      There's no hyperbaric benchmaxxing chamber devised for tasks of this scope or ambiguity yet. They fall back to platitudes and best practices (the "Reddit"/HN part of the weights). In my opinion, they are just kinda "ok" at architecture. When you're in the pocket of what they've spent more time learning in parallel than any (or all) humans could, they just let their freak flag fly, and you know it when you see it.

      Here is Claude from this morning writing and pruning a pure x86 ASM implementation of symmetric DTLS/symmetric UDP, down to a 3.8KB binary, completely from scratch, in 3hrs of nonstop work: [0]

      No human has or will ever be able to do this. But any who could even appreciate the difficulty of it would think "why TF did you do all that work before implementing certificates!" But Claude has literally never been trained on >1M tokens of consequences so

      [0] https://claude.ai/share/90de9350-81f9-46ea-a628-be625e8b9a7a

      • Creamsicle47 16 hours ago
        Who do you think a business leader will listen to, someone disagreeing with them or an omnipotent super intelligence that validates every idea of theirs?
        • weitendorf 16 hours ago
          That sounds like a false dichotomy with a bit of emotion behind it, and I'm not really sure what it has to do with long-horizon jaggedness.

          I do think that once long horizon software architecture can be brought in-distribution with larger memory pools and better architectures for long context, RL will be just as effective at teaching them to be superhumanly better at it, or to at least have vastly more breadth of knowledge to draw from, as long as the cost of bad decisions can be used to provide feedback to the model in a tight enough loop.

          Investing and business decisions have just as verifiable and large scope + a tighter verification signal (profit), so it seems arguably equivalent in scope and difficulty as general economic decision making.

          At that point you might as well ask why boards even have CEOs or why shareholders would rather have humans interfering with their assets rather than just asking something super-intelligent.

          I could be misreading your comment, but I think if you want to be who a businessperson turns to when they need help with something important, you should at least be able to articulate and show where and why you can provide better guidance than SOTA AI.

          If someone snarkily dragged their feet on AI as a source of knowledge at all, even as it becomes obviously more skilled in at least very-adjacent areas of work, without justifying why, I think that would be discrediting. If someone felt like you were on their team, and generally perceiving the same reality as them, but perhaps having useful insights that AI (and everybody else with access to it) doesn't also have, I don't see why they wouldn't listen to you. Basically, you should give people a reason to want your expert opinion if you want your job to be providing expert opinions

    • ricardobeat 16 hours ago
      > I created an IPA IME keyboard

      > and I found in review that Claude would leave the debugging tooling around unflagged

      Why is Claude to blame for that particular decision, if you created it? That's what this is about - you need to constrain the design space to take responsibility. In this case, understand the debug tooling and what it should be doing. Negative prompting is rarely a good solution.

    • hinkley 20 hours ago
      I can generally tell which PRs are AI on the OSS projects I do reviews for because the release notes are a Steinbeck novel instead of written as a one line description meant to be read among a litany of others. But then they sort of do that for everything don’t you think?
    • lerouxb 4 hours ago
      I have never seen any AI code review tool miss that you're leaving debug logging in. They are extremely picky about what you even put in the logging in the first place. Even when you're just working on some PoC locally they are reluctant to write that code by default. Any AI review of a PR or when analyzing a codebase shouts and screams at the top of its lungs about this sort of thing.

      You'll get review comments, alerts, static analysis reports, secbug tickets, etc coming out your ears with even a modest amount of modern tooling.

  • pjmlp 21 hours ago
    The problem is that usually each team only needs a single architect.

    What is happening is no different when developers got promoted into team lead of the offshoring team.

    Which also didn't require that many team leads onsite, and off they were, everyone else that wasn't leading any offshoring team.

    • mablopoule 19 hours ago
      Agreed, and another point that I haven't seen in the article : 'architect' as a separate software engineering role was a bit of a bad word, even if everybody agreed that architecture was important.

      It was mostly because in some companies there was a cast of 'architect' who were seen as above coding, and who mostly delivered out of touch UML diagrams, or ill-fitting data-structure. The core of the issue was that even good programmers would rust and get incapable of understanding the ground truth if the organization discourage them to also be in the implementation side.

      Here it's not exactly the same thing with AI, since the loop is dramatically shorter, but the (lack of) feedback issue remains.

      I really believe that my added value as a programmer was fundamentaly to evaluate technical tradeoff of the different options to solve a business issues, and them to implement them. Now with Claude code I'm infinitely faster at the implementation part, but I'm also eroding my capacity to evaluate those tradeoff.

      Programming is a medium, and you also need to work with it from time to time in order to keep some level of competency. And yet in many companies we are basically forbidden to do that.

      I feel that we have been given cars, but have also been forbidden to ever walk again; Sure the car is more efficient most of the time, but there's a an almost-vital reason why we have to do jogging to compensate.

      • pjmlp 19 hours ago
        It is still present tense for architects, hence Technical Architect, Solution Architect, Business Architect role variants.

        And yes walking is refreshing and should not be taken away.

    • water42 8 hours ago
      There's no reason for me to give feedback to junior engineers when I can just prompt Claude myself, instead of them passing my feedback into Claude.

      People who did not have the opportunity to grow and learn how to think about problems are in a bad spot right now.

      • pjmlp 8 hours ago
        Even for those that can master Claude, their place on the company is not guaranteed, as the teams now deliver the same with less humans.
    • esseph 20 hours ago
      > each team only needs a single architect

      Are they peer reviewing themselves? Who's pushing back on their ideas and decisions?

      • pjmlp 19 hours ago
        Usually the developers, which are now a bunch of agents instead.
    • lerouxb 4 hours ago
      This is nonsense. No team should delegate thinking to one person who should then think for everyone else.
      • pjmlp 3 hours ago
        It is like construction work, coders are the brick layers, in corporations mindset.

        They aren't the ones holding the vision how the blueprint is going to materialise.

        The cogs in the machine, thankfully for c-suits, now they can be replaced by real cogs in the agentic software factory.

        • lerouxb 3 hours ago
          Not really experiencing this. Senior devs seem to have far more agency than ever in my 26 years of experience.
          • esseph 1 hour ago
            You'll see it a lot in non-tech Fortune 500 type companies that have been around a long time.
            • lerouxb 22 minutes ago
              I've been in various categories of companies. See what?
    • jimbokun 20 hours ago
      But during that time the number of software engineering and development jobs and compensation levels continued to increase.
      • pjmlp 19 hours ago
        Where outside startup scene?
    • roshan7058 9 hours ago
      [flagged]
    • jwilliams 19 hours ago
      [flagged]
  • uptrails 21 hours ago
    No one is getting promoted. The most likely future is that your job will pay less and will be less fun, as you're increasingly just a "liability sink" for decisions made by an LLM.

    Try that with photography, painting, or music: "AI music has promoted musicians to architects".

    • t-writescode 18 hours ago
      You kinda can, though. What do you think DeadMau5 and other House creators do? They’re musicians for sure, but a lot of their music is 100% in FL or ProTools or Ableton.

      DeadMau5 barely even uses his midicontroller as a keyboard to my knowledge, he makes one note at a time I believe.

      They’re still musicians and DJs and similar, but they’re one layer removed from pure playing an instrument.

      • core_dumped 17 hours ago
        That isn't a great comparison. While composing in a DAW is probably far easier than traditional songwriting, the artist is still the one making decisions about what instrument is playing, what notes it's producing, and when it plays in the track, not to mention deciding how to structure automation clips. In essence what Deadmau5 is doing is functionally similar to programming. LLMs (unfortunately) can also produce these patterns, and at that point there's no human making decisions about the details of the track. Sure you could prompt the machine with exact specifications of the song you'd like to hear, but ultimately the "decisions" are made by the model.
        • t-writescode 3 hours ago
          With the robustness of some of the audio configurations, like Native Instruments' instrument packs, you can get quite a lot of music from relatively little "actual playing".

          You're still in the driver's seat, sure; but I think for many uses of AI for coding, you're also still in the driver's seat

      • GalaxyNova 14 hours ago
        How is this comparable in any way? A better analogy would be a musician that now has software that generates short sequences of the song and they choose whichever fits.
        • jrajav 13 hours ago
          That's exactly what musicians who purely use software do already. No one hears a song in their head and programs it note for note. They constantly add small elements, tweak them, and then listen to what was added or changed, over and over. They are hearing short sequences of the song and choosing what fits, according to their taste.
      • Lucasoato 1 hour ago
        Deadmau5 has racks and racks of modular analog synths, I’m sure he’s going to sleep well tonight even if he’s not using the midi controller live to record the midi tracks.
      • sneak 14 hours ago
        Wait until you hear about the theremin.
        • acobster 12 hours ago
          I know this is a joke, but anyone who can actually play theremin is probably in the 99th percentile of musicians in terms of practice hours and raw skill.
    • shimman 20 hours ago
      It's weird seeing software devs, a highly educated workforce, get labor relations and labor history so wrong. The idea that our industry will keep paying high six-figure salaries will quickly come to an end unless we collectively act together.

      The idea that rationalizing a job more (relying on metrics, measurements, statistics, predictions) will lead to better labor outcomes is foolish. We are only paid well as devs because we have comprehensible jobs (ones that require specialized knowledge and understanding).

      We have over 200 years of history regarding what happens to labor when their industry becomes more rationalized and it has never ever benefitted labor once in the history of capitalism.

      • packetlost 20 hours ago
        Yeah, it's incredibly bizarre that people are like "no we will get more valuable, see how much more we can do, we're more productive than ever!!!" when what's actually happening is the thing that you previously had a monopoly on (skilled software engineering) is vaporizing in front of you and the people writing paychecks haven't quite figured out how to value your role. It will leave a very large number of people behind entirely.
        • win311fwg 18 hours ago
          A matter of perspective.

          Imagine, as the tractor was arriving on the scene, a farmhand saying "we will get more valuable, see how much more we can do, we're more productive than ever!!!". You seem to be saying the tractor will make their farm labor less valuable. Which is true. But they're saying that the tractor freeing them from the field allows them to move on to more valuable activities, like software development. It is undeniable that software developers have been far more economically valuable than they would have been as farm laborers if the tractor was never invented.

          Of course that is conditional on "software devs, a highly educated workforce" being true. If it is true then "we" are well poised to leave software behind to jump on the next big opportunity, but I suspect it isn't actually true.

          • packetlost 18 hours ago
            > You seem to be saying the tractor will make their farm labor less valuable

            It did, it lowered the price of the end product, so the scale needed to increase to make the same amount of revenue with the ultimate consequence of there being less farmers necessary to sustain the demand for their crops.

            > they're saying that the tractor freeing them from the field allows them to move on to more valuable activities, like software development

            Surely you see the issue with this reasoning. In aggregate it allows society to 'rebalance' where labor is deployed over generations of time, but at the individual level it just leaves people jobless and eventually poor.

            > Of course that is conditional on "software devs, a highly educated workforce" being true. If it is true then "we" are well poised to leave software behind to jump on the next big opportunity, but I suspect it isn't actually true.

            Or it results in a further shrinking of the middle class and dramatic increases in inequality.

            The real question is at what point does software saturate the demand. I personally thought that the market was already heavily saturated before AI, which does not bode well for career software engineers.

            • deeringc 17 hours ago
              Also, if AI can write software, create art, run a business and detect cancer in scans, better than any human what exactly is left for humans to move "up" to? The transition from farm labour to software was just blue collar to white collar, physical to intellectual. But if machines have taken the physical work and AI has taken the intellectual work, what exactly is left for us to pivot towards?
              • pigpop 16 hours ago
                Taste was the answer that we agreed on a few years ago. Being able to choose the best output or know when things are off. Having design sense and the tenacity to dogfood the output in order to fix the things AI can't see. It's like a combination of a design lead role with a QA role, you have to know every feature from the perspective of a user, sense where there is friction and confusion and know how to do it better. Maybe calling it a "director" role would be more apt since that combines creative vision with hands on, detail oriented work and directing the work of others to redo the product until it is right.
                • archagon 16 hours ago
                  I would strongly argue that you can’t cultivate taste without having done, and continuing to do, the low-level work.

                  Few creative insights come from management.

                • aquariusDue 12 hours ago
                  I suppose the coding ninja and programming rockstar will be joined by the new vibecoding auteur.
              • Creamsicle47 16 hours ago
                AI has solved software. Bugs are not yet solved. Humans still need to ship a fix for that.
              • 9rx 14 hours ago
                > what exactly is left for humans to move "up" to?

                Same place the economy has already been going for a while: Looking the other way.

                In other words, those with resources get to buy the ability to do things that are unacceptable or illegal for everyone else. The job is to accept it.

          • ThrowawayR2 17 hours ago
            In that analogy, current developers are more like the horses that pulled plows than the farmhands. Anyone noticed any horses on the gigantic industrial farms doing "more valuable activities" lately because the tractor freed them from plowing?

            The farmhands are closer to product managers and architects but none of them are former horses.

            • 9rx 17 hours ago
              Do you consider horses (any horse) to be highly educated? The earlier comment already recognized that the lowly educated are unlikely to find their way.
              • est31 52 minutes ago
                The horses aren't highly educated but they are very strong. The tractor replaced muscles, not brains. Now it's the brains that are being replaced.
                • 9rx 12 minutes ago
                  Brains were never all that valuable, though. Most of us were writing software at five years of age. It is no great feat. Almost none of us were writing software professionally at five years of age, however, because adults don't want to build relationships with children. Relationships are where the value has always been.

                  It is true that the poorly educated don't understand how to build meaningful relationships. They are destined to become the modern horse. But the highly educated aren't sought after for their brains. They are sought after because they're fun to be around and can share compelling conversation over a beer at the bar. There may be an AGI future where it too can build relationships, but AI is not that.

          • rpcope1 12 hours ago
            On the highly educated workforce thing, I think that's at least a little overstated if you think about the median front end or enterprise developer (maybe underrepresented on here), and also kind of confused being "educated" with being able to adapt and change quickly, which again from what I've seen, there's a lot of software engineers not only have literally no idea what happens in adjacent roles like sysadmin nor skill, but also seem to lack a lot of broader inclination or general skills (hard to become an electrician if you don't know what a DMM is or have never changed a lightbulb; hard to become an actuary if you never made it past trig).

            I would also ask, even for those who can adapt, what exactly comes next? It's not remotely clear where and what could absorb the legions of "tech people". It's kind of like the people that jerk off self driving trucks, when you realize how many people are employed as truckdrivers (hint: in many states it's the most common profession) and ask "where the fuck is this horde of people supposed to go?"

          • themgt 18 hours ago
            If it is true then "we" are well poised to leave software behind to jump on the next big opportunity, but I suspect it isn't actually true.

            Much like discretion is the better part of valor, if your plan in 1916 is doing a gallant feathered cap cavalry charge at the machine gun nests, don't worry too much about whether high command will promote you up the ranks later.

        • ok_dad 18 hours ago
          Luckily that’s applicable generally to most desk jobs with AI replacements, as long as you accept the shit ass quality that clankers produce when unsupervised.

          Either the AI bubble will pop because unsupervised clanker quality never reaches supervised levels or we’ll ALL be out of a job and then it’s the everyone’s problem when society crumbles.

          • packetlost 18 hours ago
            Quality has been niche since the invention of automation.
      • raincole 17 hours ago
        The only way to keep programming a high-earning professional is to make it a licensed job. Like doctors. You'll have to have a formal degree and get a license to push any code to production, or you go to jail. That's the only possible future where programmers still earn significant more than most desk jobs.

        That'll force most of us to leave the industry, of course.

        • moduspol 14 hours ago
          That only works with jobs that can't be outsourced.
          • vineyardmike 11 hours ago
            That's just another export control law away....

            "you can't sell phones without X% domestic software", "you can't share security vulnerabilities overseas", "part of X compliance policy is domestic sign-off", etc

            is this a good idea? Different answer than if it'll work. But a market like the US has limited window of time where it's a sufficiently major economy that putting tariffs and policy up to protect an industry may pay off. The US has by far the biggest software industry, so protect it (the labor force) while you can.

            • ifwinterco 5 hours ago
              Or even "we have capital controls, it is not permitted to send USD out of the country or convert USD to INR to pay anyone without permission".

              Sounds crazy to anyone who grew up in the post-1990 economic system but that is how it worked for the UK and other countries under Bretton Woods

        • Buttons840 15 hours ago
          So I couldn't just casually make an app? That's always been the problem with licensing. Some company has a bunch of licensed engineers buildings some software app, and then a bunch of kids comes along and makes something similar and it's better so people give the kids their money instead of the licensed engineers.
          • raincole 13 hours ago
            > I couldn't just casually make an app?

            You can, but you can't sell it on major platforms. Just like you can build your own house on your own land without a contractor license, but if you sell this service to someone else a license is needed.

        • seanw444 16 hours ago
          That also sounds objectively worse. This is why we can't have nice things.
      • drak0n1c 19 hours ago
        Detroit and many other factory and heavy industry jobs collectively acted through the 20th century, which raised costs, slowed production, and simply accelerated their downfall. Introductions of any significant trade protectionist follow-ups ended up being scorned by the public (see the popular reaction to Trump 1, Biden, and Trump 2 tariffs regardless of efficacy).

        The medical industry achieved some protection through regulatory capture, licensure, and throttling education. Doctors have very high salaries now but there's a shortage and they're overworked. Innovation is also throttled in that space as a result. Socialized systems aren't faring any better, the doctors I know in Canada and Japan are just as overworked, have to rush cancer patients through 5 minute appointments, and are paid far less.

        There is no magic bullet for making a large profession sufficiently protected by mystification (anti-rationalization?).

        • shimman 19 hours ago
          Of course there is:

          https://en.wikipedia.org/wiki/Workplace_democracy

          I reject the notion that only the elites know how to run these society impacting technology companies. These people are anti-human and should be imprisoned. Workers of these companies should be able to elect their own leaders, their voices are worth more than the investors or shareholders.

          The economy is the only place in our society that we allow tyrants to openly reign freely. We only have our entire existence as a species to know that monarchies, oligarchies, and authoritarians have hindered our capabilities to thrive as a species. There's no reason why these companies shouldn't be subjected to democratic norms too, they couldn't exist without our democratic societies in the first place; the expectation that only a select few elites should dictate the direction of technology in the US is deeply concerning and should be rejected with something better.

          Workplace democracy is better.

          ---

          Fun fact, Congress can impose that corporations become workplace democracies and it's totally legal. Whoa!

          Don't let the anti-humans tell us how to run society. Society can be so much better if we rid these anti-humans from our ranks.

          • bijowo1676 17 hours ago
            workplace democracy already exists, its called Partnership (LLP).

            consultants, laywers, bankers, accountants, auditors, some other high flying professions organize in a Partnership format.

            its functionally no different than being a cofounder of a startup

            • anon7725 13 hours ago
              Partnerships lead to an aristocracy/peasantry split. Large partnerships employ many non partners.
              • ahartmetz 6 hours ago
                So it's like the original Greek democracy.
            • stuaxo 7 hours ago
              Cooperatives are a thing (I don't know about the US but certainly elsewhere).
      • pjmlp 19 hours ago
        In most countries no one earns those figures, it is an office work like everyone else with higher education on the room.
        • shimman 18 hours ago
          This still applies to any capitalist economy on the planet. Don't worry, your job will be degraded too.
          • pjmlp 17 hours ago
            Not all capitalist economies are born alike.
            • shimman 15 hours ago
              No, but they all degrade workers just the same.
              • pjmlp 8 hours ago
                Some of them have unions that work, unlike US.
      • bijowo1676 20 hours ago
        why do you think helpdesk or call center employees were not able to unionize and protect their jobs?

        in the age of AI, the helpdesk/call center is really not different from that of a software engineer. The only diff is Helpdesk operator talks to a human. SWE are now just talking to LLM.

        the job is perfectly mobile, can be offshored, outsourced, replaced, and million other ways to destroy any attempt to unionize.

        unless, the society-wide labor unites as a single voting block for more redistribution from capital towards labor and universal federal ad-valorem wealth tax, instead of income tax

        • andersonpico 17 hours ago
          > the job is perfectly mobile, can be offshored, outsourced, replaced, and million other ways to destroy any attempt to unionize.

          "The emancipation of labour is neither a local nor a national, but a social problem, embracing all countries in which modern society exists."

          • bijowo1676 16 hours ago
            yes, its gotta be either total socialist/peasant revolution against the Big International Capital or nothing.

            International Capital has advantages: it has power, it is fluid and mobile, can work across geographies, tax codes, it has natural cooperation incentives against the labor

      • lkjdsklf 19 hours ago
        > The idea that rationalizing a job more (relying on metrics, measurements, statistics, predictions) will lead to better labor outcomes is foolish.

        The interesting thing is that this exact thing happened before in the software industry. It's what killed the "old" software giants of the 90s. Only really microsoft was able to pivot and recover.

        "Big Tech" became big tech by bucking that trend and being much more empowering to "low level" employees. Allowing talented people to build good things. They ditched the measuring productivity with "lines of code" and tickets closed and all that nonsense that was common place before that.

        The current batch of tech CEO are going down the same path of morons like Jack Welch and we're all going to pay the price for it. I guess, if I were them, it's a reasonable choice. Despite leaving a wake of carnage and turning great companies into shells of themselves, they'll be billionaires before anyone figures out how utterly fucking stupid they are.

        It's just very odd how, as an industry, we learn nothing from the past. Not at the executive level and not at the worker level. It reeks of arrogance at all levels.

        • 2OEH8eoCRo0 19 hours ago
          I'd argue that our industry is so arrogant that it hates the past. They know better!
      • IshKebab 19 hours ago
        > unless we collectively act together.

        I don't think that's going to work. There's no barrier to entry for vibe coding. Your union would have to include everyone in the world.

        • hosteur 17 hours ago
          Not now. But 20 years ago surely.
        • win311fwg 19 hours ago
          You'll notice the parent didn't saying anything about unions. Unions cannot help here, but collectively working to establish a legal professional designation (think doctors, lawyers, etc.) can.
          • ThrowawayR2 17 hours ago
            Those professional designations maintain value because they have a very, _very_ high bar for getting and keeping a license and also are burdened with liability for malpractice. Most current developers would be filtered out.
            • rpcope1 12 hours ago
              You say this like it's a bad thing.
          • bijowo1676 17 hours ago
            frontier labs are the ones who are working collectively to kneecap competition (open weight models), and ensure regulatory capture towards themselves (employees of the frontier labs)
      • 0c3ca83 18 hours ago
        It will come to an end regardless, as the deskilling of the work happens.
      • sirmike_ 19 hours ago
        you are barking up the wrong tree with that unionization horse apples. Unions plus technology do not go together. i’d rather take my chances on my own than deal with all that nonsense. What’s up with the the streak of communism in the comments lately?
        • noah_buddy 19 hours ago
          When you look at everything and only see communism, you just don’t actually have a cogent definition of communism. It’s a common problem in American political discourse. Anyone left of Clinton is called a communist in American politics.
        • vrganj 18 hours ago
          > Unions plus technology do not go together.

          That is hilarious seeing how unions literally became a thing as a result of the industrial revolution.

          Unless you're arguing that the industrial revolution had nothing to do with technology?

    • ihsw 20 hours ago
      [dead]
    • lerouxb 4 hours ago
      Promoted to what? Engineering Manager? Product Manager? Staff? Who wants to be that right now anyway? Never been more fun to be an engineer.
    • staplehorse6553 9 hours ago
      >The most likely future is that your job

      That is where you're wrong, kiddo

    • seer 20 hours ago
      Well no, ai music has promoted musicians to publishers, designers to art directors and developers to software engineering managers.

      It’s just creating your own team of little robots working for your own personal “department”.

      Though what I am seeing is that increasingly I am “setting up teams of agents” which each have their own “lead” and I just talk to these “leads” not individual agent “developers” . Effectively becoming a “VP” of engineering of my own private little “consultancy” … maybe next year (or month?) I will manage a bunch of “vps” as the “ceo” of said mini organisation … a product engineer indeed.

  • lerouxb 5 hours ago
    This is gatekeeping. Everywhere I've worked every candidate goes through systems design interviews and it is expected that every employee pushes back on and considers architecture and system design.

    The market for dedicated architects has always been vanishingly small.

  • JKCalhoun 1 hour ago
    I found that over my 40+ years as a programmer, I became an architect after having worked with several dozen API over the years and having written (and maintained) several dozen apps and frameworks over that time.

    It does seem to me that had I been vibe-coding this whole time, it is unlikely I would have improved as an architect.

    • jeremyjh 1 hour ago
      Yes that is the foundational concern. I'm pessimistic about the prospects of new computer science majors not because humans will become irrelevant (maybe we will, but then there will be no safe quarter and career choices don't matter) but because I don't see how they can really learn this trade when they are expected to use AI for most of the coding. Its possible they will find other paths but so far my experience with the couple juniors that I have is very discouraging, they aren't learning the job at nearly the rate and depth that their peers did four years. Actually most new seniors are not learning the domain nearly as well - the best ones can still do it because they remember the value of the early struggles in a new codebase and force themselves to find ways to recreate much of that essential learning (agents can also help with this, if you can find the key moments to engage your own brain).
  • mellosouls 21 hours ago
    A dev moving down to architecture is not a "promotion".

    Architecture is no more immune to AI than software engineering.

    OP is describing somebody using AI poorly, and seems not to have a great handle on the way all jobs are impacted and boundaries being wiped away.

    • roncesvalles 43 minutes ago
      Exactly, OP's colleague is just a bad dev. I think without AI they would've still written a solution like that.
    • QueensGambit 21 hours ago
      OP here. You may be right about architecture being wiped away in the future, but we have to ship with today's tools. Also, architecture is about tradeoffs and could have longer staying power:

      > AI coding tools are tuned to implement your functional requirements and two non-functional requirements, i.e. security and backward compatibility to avoid breaking your app. This invariably leads to:

      - Architecture that trades off performance for security and slows down the app.

      - Multiple versions of datamodel design with redundant tables, columns and code.

      • knollimar 18 hours ago
        I give an LLM like 4 constraints and it implodes trying to balance them. It feels very bad at architecture
        • nomel 14 hours ago
          I'm also still seeing really poor performance with architecture, with Opus 4.5. I feel architecture is the only remaining use for me, besides the project management aspect of it all.

          I give that a bit over a year, then me typing, or even reading, the code will just slow things down.

          It's incredible!

    • rektomatic 18 hours ago
      >somebody using AI poorly

      I see this sentiment a lot. "AI will replace us but only if used correctly". The "only if used correctly" is the SWE+Architect part that people miss. So effectively, you may be contradicting yourself in this single comment.

      • Palomides 17 hours ago
        we went from "humans transform vague requirements into semi-technical requirements into code" to "humans translate vague requirements into semi-technical requirements that AI turns into code", the next step seems hardly different to me
        • rektomatic 16 hours ago
          >the next step seems hardly different to me

          That's where we disagree

    • esseph 20 hours ago
      > A dev moving down to architecture

      Heh, at every company I've ever been at, an Architecture role is about the same as a non-banking VP, definitely not a demotion. It's often substantially more pay with substantially less work.

      • varjag 19 hours ago
        Architect very often was a coveted sinecure for failed programmers. It didn't necessarily pay better than a senior IC and they normally had no reports.
  • dhpe 20 hours ago
    It took me years to learn that an architect is a different job role than a developer. I always thought every developer must understand software architecture deeply to do their job. Later I discovered that there are architects who just draw diagrams. I was blown out.
    • markus_zhang 12 hours ago
      Honestly you can’t understand architecture deeply if you have never done so. It’s a catch 22.

      I’d say very few developers are really good architects because they rarely had the opportunity to grow and trial.

    • aeonik 19 hours ago
      We call them "marketects", and they practice "marketecture".
    • bijowo1676 20 hours ago
      architect with diagrams is like McKinsey consultant with powerpoint slides.

      functionally similar

  • ChrisMarshallNY 4 hours ago
    > But AI will never make that call for you, because it doesn’t know your users and it won’t push back on your requirements.

    In my case, I have been able to mitigate this. I have an LLM (ChatGPT, but I don't think it matters that much, anymore), that I load with vast amounts of information about the end-users of my apps. It generally makes excellent decisions, and often pushes back on my requests, if they may not deliver a good result. I sometimes think it knows more about my users than I do. One example, is that it does a very good job on translation. The feedback has been overwhelmingly positive. It blows away the stuff I used to have done by professional translation agencies.

    I still feel that I need to design the overall architecture, but I sometimes wonder if that's just because I'm a control freak.

    • plasticchris 4 hours ago
      Transformer models were originally developed as machine translation tools after all :)
  • kaffekaka 18 hours ago
    I've heard words from colleagues to the effect that us devs should not be involved in projects until all the requirements are done, and that we should not come with proposals and pushback. "We should just build the dumb client."

    It seems insane to me. I want to be even more involved in architecture, design and strategy now that AI speeds up the typing part. I can't understand their reasoning.

    • anal_reactor 15 hours ago
      I've spent 4 years in a team of idiots who earned twice my salary because they were hired when company was desperate, while I have lower position and salary because I was late to the party. We spent countless hours doing stupid shit that was never meant to work and nobody wanted, and we shot down projects that later upper management deemed priority. I am tired of fighting people who never fucking listen and aren't capable of long-term thinking. Oh wait, they are. Because most management roles are a game of hot potato where the goal isn't to defuse the bomb, it's to make sure the shit doesn't blow right into your face. A random guy making the right calls is a danger to a team of useless fucks. They understand that very well. Another colleague who is highly skilled was literally told "go find another job if you want to make a career".

      I am out of fucks to give. My goal is to minimize the amount of energy I put into work. I don't push back, I do what I am told to do, and I take my sweet time to do it. Of course I cannot jump ship because job market is not what it used to be. Hashtag fuck work.

      • kaffekaka 8 hours ago
        Sorry to hear that. My job is not bad, my colleagues are competent, it just surprised me they come to the opposite conclusion than me.

        I might be native but I believe things will improve/stabilize and we won't have the apocalyptic disaster often described. Hang in there and some new possibility will show up eventually.

      • whoanoway 15 hours ago
        [dead]
      • mjburgess 12 hours ago
        Welcome to the species.
  • Oarch 1 hour ago
    I straddle construction and SWE and briefly struggled with this title. Both developers and architects have wholly different meanings!
  • teekert 8 hours ago
    Every dev has a bit of an architect in them, you have to. But non-devs probably don't.

    I feel that, indeed I'm fast-tracking into the architect role (already started with some courses years ago but started my own company and went back to dev + sys-admin, arguably that latter is also a bit if an architect role), but the big models are also reasonable architects! Opus or Mistral Large 4, will often come with pretty smart suggestions on preventing cases like the one from tfa. Not always and when I am architecting webapps with databases with "complex" datamodels, the LLMs really help with the big picture view, steered by me (meaning I'm often struggling with walls of text explaining pros and cons of decisions), and I don't write any of the code anymore. It just makes edits in 5 places for things I want. I am the gate before comitting, I do stakeholder management, but I rarely find anything weird in proposed code. Usually I only push back when it wants extra dependencies I feel we don't need.

    And the whole thing is so rapidly improving, the view in tfa is useful, but maybe outdated in a couple of months?

  • wasabinator 15 hours ago
    This whole promotion stance is nonsense. Nobody is getting promoted, they are getting devalued. More for less will be what happens. Technologists are probably the biggest lemmings when it comes to security of their own labour. Now that they are all talking about software factories it's the end game for not being needed.
  • MomsAVoxell 17 hours ago
    I wouldn’t say we promoted developers into architects - its more that we exposed developers who are poor analysts, requiring that they do more architecture to cover their asses.
  • Blackarea 2 hours ago
    This example would fit for a junior engineer more than an architect where i come from
  • spacebear 19 hours ago
    A basic prompt like “is this code performant?” would probably catch this problem with current models.
    • duskdozer 3 hours ago
      If that's true, then prompters won't have jobs much longer than anyone else.
    • classabove 17 hours ago
      Has this really been your experience, in practice? With prompts this vague, I often see massively complicated preemptive optimisations.

      If you feed in the right info on what sort of performance optimisations make sense given the context of the system, and provide the mechanisms to measure them, then yea.

      'make sense given the context of the system' doesn't feel solved to me.

      • spacebear 15 hours ago
        With Opus 5.5, it really has. I’m pretty sure if you fed the code the article was written about to it and gave it that exact prompt, it would flag the extra API calls. More context is better of course, but I’m regularly amazed how little context you need these days.
  • silver92bullet 11 hours ago
    My biggest question is how are we going to pass down the tricks of performance to juniors if they are overly reliant on the AI. It seems like this would be a good spot for mentorship to help a junior engineer build intuition and pick out when the AI is wrong and a better design.
  • hoppp 19 hours ago
    Yes. I have been an architect all along, but I needed to write the code. Now that coding is solved I can fully devote my attention to architecture.
  • stuaxo 15 hours ago
    I've always had to do some of the things mentioned.

    On the other hand... there are jobs out there that are proper SW architect job, how does one even transition from dev to architect - is it even a thing a dev wants to do ?

    Is it something where you really need a mentor ?

  • ramesh31 17 hours ago
    I'm just tired. This job used to be so cozy. Take your time to think deeply about a problem, and fully understand the solution. Now it's just an inch deep on 20 things at once, while being responsible for doing the job of what used to be a whole team. I know most of us are just lucky to still be employed at this point, but it's completely exhausting. If coding is no longer part of the job then why even bother anymore, and just become one of the people that talk and send emails for a living.
    • bitwize 17 hours ago
      The people who "talk and send emails for a living" are the ones actually driving value in the company and always have been. And they've been trying to automate your job away for decades.
      • ramesh31 13 hours ago
        >"The people who "talk and send emails for a living" are the ones actually driving value in the company and always have been. And they've been trying to automate your job away for decades"

        Trust me, I know. But for a long time they needed us to do this thing we really enjoy doing, and paid us well for it. I don't care about driving value for the company. I don't want to be one of them. I want to do something I enjoy and get paid for it, not pretend to care about something I don't. So now I have no idea what to do.

        • YZF 9 hours ago
          But now you can do bigger things. The reality of being paid to code is that you often have to do things you don't like. At least for most of us. Now AI let's you delegate the things you don't like, or are less important, to your army of interns Claude and Codex and then spend more time on things you do like? If you feel like coding some bits by hand while Claude and Codex churn out the parts that are less critical, why not? And without them you could not get everything done yourself anyways?

          I used to get my dopamine rush from coding. But coding today isn't what it used to be - even before AI. It has become more of a jigsaw of many systems where you're mostly plumbing pieces together. Way back, we wrote entire systems from scratch building on top of very little. Today hardly anyone does it. Now AI gives me the power again to translate big visions in my head into working systems. I don't have to write all the code myself. But without AI I might not be able to do the things I can do today.

          • stuaxo 7 hours ago
            Really excited to graduate onto only doing things I don't like.

            Now I'm in an AI first job, but before that I was still doing ones where coding was pretty good - building interesting complex things and always finding new things to learn.

            I'm really not sure what I think about promoting all day.

            I need to work out how to optimise the work to be fun somehow, I don't know if it's even possible.

        • markus_zhang 12 hours ago
          Damn well said. But I guess the cozy days are gone and we better cope.

          I cope by hacking on educational kernels. I still use AI but only for discussion or I couldn’t figure out something after exhausting every other venue after say a few hours (if it’s a tool issue) or a few days (if it’s a programming issue).

          Just spent a few hours trying to figure out why the Makefile doesn’t work. I’m much happier now. I don’t need to talk to a stakeholder to fucking understand the business logic of a 37 lines of CASE WHEN THEN ELSE END. I just need to understand the kernel and tread lightly. I scratch my hair way more often for the kernel but I feel young.

      • seanw444 16 hours ago
        Their jobs aren't far behind. At this point, I'm all for AI accelerationism. Let it all burn down. Nobody cares until it's their life on the line anyway.
  • bengold14 18 hours ago
    Couldn't agree more except that these are architects that are actually implementing and need to deal with the pesky details of building. Engineer-Architects.

    The problem is the abstraction we still expect them to use is code. In most companies architects didn't use code at all. We need a new abstraction that focuses on architecture.

    (full disclosure I work in this space https://www.archme.io)

  • water42 8 hours ago
    This article is wrong; frontier models are absolutely good enough to realize blocking code is bad. Show me the prompts!
  • hosh 15 hours ago
    Roy Fielding and Christopher Alexander has quite a lot to say about architecture.

    AI models already have their works in training data. I spend much of my time in conversations about architecture as a grammar — a pattern language, not just patterns

  • cluckindan 17 hours ago
    ”AI … is also sycophantic and tries to execute your requirements exactly without pushing back”

    In my experience, this is not true. Multiple times I’ve asked it to do things against guidelines and plans, and every time it has pushed back.

    • catlifeonmars 17 hours ago
      I had this happen as recently as today. Clearly we’re both working off of anecdata and should take the experiences with a grain of salt.
    • sick_of_slop 16 hours ago
      [dead]
  • smrtinsert 19 hours ago
    We were always architects. They just dont want to pay us for it.
  • bluefirebrand 20 hours ago
    I don't view becoming an architect as a promotion :/
    • hinkley 20 hours ago
      I don’t view it as being a job title either.

      Architecture is a responsibility shared between your project leadership, whether you call them leads or principals.

  • sneak 14 hours ago
    Every programmer is and was a systems architect whether they knew it or not. Many are just bad at it, and still are.

    Programming is a lot more than knowing syntax and APIs.

  • DeathArrow 8 hours ago
    >Why AI won’t push back

    That's a false assumption. I got AI pushing back a lot of times. Maybe the author is not familiar with using AI? And you can, of course, instruct AI to be even more pushy.

    >AI is great at writing code. But it doesn’t know if you are launching the app or have millions of users,

    But it does know if you inform it.

    Also, humans do not always push back. They either don't care or the pushback can be detrimental to their own goals.

  • DeathArrow 8 hours ago
    >Why AI won’t push back

    That's a false assumption. I got AI pushing back a lot of times. Maybe the author is not familiar with using AI? And you can, of course, instruct AI to be even more pushy.

    >AI is great at writing code. But it doesn’t know if you are launching the app or have millions of users,

    But it does know if you inform it.

  • LeafItAlone 19 hours ago
    > Since logging was the first line to execute after installation, the welcome screen took 15 seconds to load

    If you go from a (presumably) reasonable load time to one of 15 seconds and it’s not caught before getting merged, you have bigger problems than developer vs. architect and AI coding.

    The premise of the post has merit, but the example is a terrible choice.

    • jpollock 19 hours ago
      It's a pretty normal failure mode in teams. The abstraction breaks because the developer doesn't know the things that drive their latency.

      Is it database requests? RPCs? Is there a function call which is computationally expensive?

      Teams then respond by making rules to help make slow things stand out "no RPCs in functions, no synchronous RPCs, only 1 database read per request, don't call this code in a loop", etc.

      Caught before merge? Only if you have someone really familiar with all the abstractions _and_ the team's previous failures reviewing it. Otherwise, developers are always finding new ways to write slow code. :)

      But, that's why we have feature flags and incremental launches.

  • 6thbit 20 hours ago
    Sorry but Nah. Architecture has always been a part of the job.

    If you weren't doing it, you were doing it wrong.

    • hinkley 20 hours ago
      That’s not just a continuum but also a timeline. Junior devs need to be encouraged to start thinking about why as much as what, and what more than how.

      But they don’t teach you that in school. You get how and a bit of what. Maybe a little why in a sales pitch or an aside from a professor who hasn’t worked in industry except in research which is prototyping and we all know how people who only do prototypes are about rigor.

  • lordnacho 18 hours ago
    If instead of becoming a software engineer, you became a civil engineer, you would not be pouring concrete and tightening steel cables.

    Until very recently, a software engineer did the equivalent things: looking for small coding errors, hooking up libraries, writing unit tests.

    Now, those things can be done by an LLM. All that is left for a software engineer is to do the actual understanding of architecture, and to be responsible.

    Of course I can understand that people mourn being able to look over their implementation of some algorithm deep in the bowels of the product. That used to be fun. I can understand that young people in the field now face uncertainty, because doing the little things used to be how you paid your dues so that the seniors could explain to you how the big things were done.

    It was like a deal, you would join the firm and do the stuff that was necessary, in exchange for training. You had time to learn the big things, because the little things took time.

    There's another business that I started in where the gap also went away. In the old days, traders used to do their work on paper. There would be clerks who would note down trades, and check that the firm's positions were in fact what the senior trader thought. Pretty mundane stuff. But at the end of the day, you would sit with the boss and he would explain what had actually happened while you checked things.

    I happened to land just as the transition was finishing: instead of taxing your physical conditioning by having you jog around the floor in a coloured jacket, the work went on a computer. The computer would let you solve the small things faster and better than you could ever do yourself. But it would also be the end of that guy who was just a good grinder. Now you had to use the machine to do new things in the market, and people started needing degrees to get the job in the first place.

    The very nature of the entry-level job changed. The job itself opened up as well, though the fundamentals at a high level remained.

    • duskdozer 3 hours ago
      >Until very recently, a software engineer did the equivalent things: looking for small coding errors, hooking up libraries, writing unit tests.

      Well, if this is what people were doing, I'm not surprised they think that "software development is solved" or whatever the current line is.

  • croes 9 hours ago
    Promoted? So they get more money?
  • zug_zug 21 hours ago
    Exactly. You are now PM, Architect, and QA but get paid the same salary

    [and your director now is convinced all his stupid ideas are both brilliant and very safe]

    • heisenbit 17 hours ago
      You clearly have not got the memo about taking over the operations and finops.
    • htrp 20 hours ago
      tell your director he can do it himself with AI.... and see how far he gets
      • consumer451 20 hours ago
        If the pace of advancement of the last year continues, how many years until that's exactly what happens in >50% of software creation?
        • prmph 16 hours ago
          "AI, create or improve software to make money for the company. I repeat, the ultimate goal is to make money. I don't care about any details, like architecture. Now start!"
      • IshKebab 19 hours ago
        Depends what "it" is, but for a lot of web SaaS companies, probably quite far. Think about thinks like Trello, Workday, Greenhouse, Zendesk, Jira etc. Definitely doesn't take much technical expertise to vibe code replacements for those.
      • hinkley 20 hours ago
        All the way to a class action suit and jail.

        The thing is that most of us don’t have the patience to wait for the toddlers in ties to fuck around and find out. We have tuitions to pay and retirement funds to fill and we don’t want to be subpoenaed.

  • jimnotgym 18 hours ago
    "Monitoring new customers is the most important part of running a business"

    I'm afraid I can't let that one slide. Where do we start with this.

    Is it more important than having a good product to sell, for instance?

    Is it more important than maintaining your existing customers?

    Is sounds so creepy to me, monitoring customers...

  • gavinray 15 hours ago

      > "Since logging was the first line to execute after installation, the welcome screen took 15 seconds to load."
    
    Apparently written by a dev that never got the email that computers can do more than one thing, nowadays.

    The logging could have taken 1,500 seconds and it wouldn't be a big deal if it had been punted off the main/UI thread...

  • martini333 5 hours ago
    Why is a LLM not concerned with performance again? Just tell it to be.
  • hden 14 hours ago
    Nah. We demoted them to glorified crane operators without informing them.
  • throe839384949 20 hours ago
    I think we should not promote existing developers!

    If AI is even remotely capable, we should fire all staff, and hire the same number of people in Nigeria! Diverse workforce is by far the most important goal! And it reduces CO2 emissions from commuting! And we save money!

  • Animats 20 hours ago
    > Monitoring new customers is the most important part of running a business...

    Priorities.

    Useful question for "analytics" people. If you only collected data for every thousandth customer, would you have less useful insights?

  • giantg2 21 hours ago
    It seem I was not only "promoted" to architect but also to PM/BSA. I'm having to gather requirements straight from managers and end-users and document everything, in addition to developing and leading another developer under me. The really interesting part is that my new role (after being pushed out of a Dev role) isn't even in the development/architecture family of jobs. Fuck corporations.
    • hinkley 20 hours ago
      Backlog grooming has always felt like devs forcing other people at the company to do their jobs. But then Agile was always that even outside of Scrum.
      • giantg2 19 hours ago
        This isn't even backlog grooming. It's up to me to create the backlog and all the analysis that goes with it, plus the stakeholder management that PM are typically supposed to do.
        • hinkley 18 hours ago
          I think I’ve attended a lot more dysfunctional grooming sessions than you have. Magic thinking is very common and you have to send a lot of feature requests back to specification until they get the message and stop coming to you with hot garbage.
          • giantg2 17 hours ago
            I've had good PMs that have managed this. On one team it was so bad the PM told the business they had to do an ROI study for any suggested change. What a glorious time as a dev.
    • Seattle3503 20 hours ago
      In addition to that and reviewing other people's AI slop MRs, I've also been promoted to devops. So many promotions.
      • giantg2 19 hours ago
        True, I didn't mention the ops part. But at my company that stuff was lumped in my least 5 years ago, if not more.
      • prmph 16 hours ago
        > We're gonna get promoted so much, you may even get tired of being promoted. And you'll say, 'Please, please. It's too much promotion. We can't take it anymore...'
  • mannyv 17 hours ago
    Don't forget, they've turned everyone into architects and QA people.
  • cush 8 hours ago
    AGENTS.md

    This app has millions of users…

    Solved.

  • bill10 10 hours ago
    Or AI did
  • BatchJob 12 hours ago
    I refuse to reframe my worldview of software just because of some LLM sycofants comments.
  • jon128 16 hours ago
    From a cloud hosting provider perspective, the office of the CFO specifically, the vibe coding is great.
  • debo_ 16 hours ago
    You asked developers to be adults without informing them
  • themgt 19 hours ago
    Yesterday, I was debugging a performance problem with our Google Forms addon. It turned out my colleague had vibe coded the logging part, so that he could monitor the new installs every week. ... All of these are one line of code, but internally each of these makes multiple API calls to Google servers. Since logging was the first line to execute after installation, the welcome screen took 15 seconds to load.

    AI is great at writing code. But it doesn’t know if you are launching the app or have millions of users, which it needs to make the right architecture call to log a timestamp vs email. It is also sycophantic and tries to execute your requirements exactly without pushing back, which means you end up with a slow app that takes 15 seconds to load a static welcome screen.

    It is so paranoid about security that it will never write code to accept an unauthenticated payload. Even if you write it yourself, it will rewrite it into an authenticated payload and screw up performance or force users to sign in again on your app.

    Just incredible seeing this post at the top next to "Unforced Navier-Stokes singularity, and the Generalized Riemann Hypothesis". We're at the "Japanese soldier who kept fighting 29 years after WW2" stage of AI denialism.

    • lordnacho 18 hours ago
      Yep, I regularly get into conversations online where people are claiming that AI can't do their work, and theirs is a complex and important problem in the real world.

      Chances are, if you can't get AI to do it, it's because it's a problem with internal contradictions that can't be resolved in any logical way. For anything else, there's AI.

  • j45 20 hours ago
    The role of developer is evolving, and it doesn't means developers scale into architects automatically. They get to learn, which is great.
  • slj 17 hours ago
    As an aside from the contention of the article, while I don’t intend to enrage anyone here, could we please all refrain from the Generic He pronoun? Singular They has been a feature of English since the 1400s iirc, and to me using these it comes across as being intentionally pompous
    • thin_carapace 16 hours ago
      may i ask what benefit you envision from your suggestion? im not seeing the negative aspects of using a masculine pronoun in referring to a male humanoid.
  • gspr 19 hours ago
    "Promoted". Some people wanna do.

    Jesus, this is gonna end up being middle managers all the way down. Get a grip!

  • 0c3ca83 18 hours ago
    Architect was long considered a bullshit job for the out of touch.
  • 6510 14 hours ago
    into astronauts
  • viklove 21 hours ago
    > If you are a senior developer or architect who understands the number of API calls behind each method, you would have:

    Lol, sounds like something only a junior developer or intern would say.

  • arbor-group 1 hour ago
    [flagged]
  • rainbowroadprep 11 hours ago
    [flagged]
  • charliehsy 15 hours ago
    [flagged]
  • yoy0721 16 hours ago
    [flagged]
  • heybax 17 hours ago
    [flagged]
  • chmorgan_ 18 hours ago
    [dead]
  • atombytede 17 hours ago
    [dead]
  • sick_of_slop 20 hours ago
    [dead]
  • tschellenbach 20 hours ago
    Actually, you should always hill climb security and performance. AI can optimize these things if you ask it to.
    • hinkley 20 hours ago
      Architecture is not hill climbing. Confusing the two is why software becomes slow and bloated - you believe low hanging fruit can fix all problems. They all end in local minima that I suppose is fine if nobody knows any better but users aren’t stupid. They can see that a similar app works 3x faster.
      • woadwarrior01 3 hours ago
        The age old BDUF vs XP debate.
        • hinkley 21 minutes ago
          You cannot make Scrum work without also doing most of what Kent Beck espoused so as far as I’m concerned, XP won.
      • QueensGambit 17 hours ago
        Exactly. Architecture is about tradeoffs. If you dont compromise on one of properties in CAP theorem for your database, then AI will reinvent Google spanner and expect you to have Google scale data center to run it.
    • baq 20 hours ago
      That’s just one prompt in a loop though.
  • solyin 21 hours ago
    > You got promoted. Nobody told you, so I am telling you.

    Love that attitude!

  • chao86825 13 hours ago
    [flagged]