• fuckmyphonefuckingsu [comrade/them]@hexbear.net
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    1 year ago

    This is not a progamm8ng hot take per say, but it’s related and guarenteed to blow up my inbox 🎣

    People who put the title of “architect” in their programming/coding job titles are stealing valor from actual architects, and clearly doing it bc it sounds cooler than “software designer” or “coding technician” or whatever the more boring and appropriate job title would be

    This is now endemic in every field, not just the tech sector, and its largely thanks to the widespread use of the term “architect” in tech

    Middle-managment banking position with slight kickbacks? Please, no, I’m an “Investments Architect.” Me? No, no - I’m not just some chemist working for a shitty soda company, I’m a “Beverage Architect.” And so on

    We see you, fuckers owl-pissed

    • MrTallyman@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      I just put “software engineer”, or “senior programmer”. It’s all the same to me.

      Software Architect is an altogether different thing, although in my career I’ve had to do a bit of it, it was never a principal task. And these days that job is often driven by “Tech Director” or “Tech Lead” or the 20 other titles that don’t mean that much.

      After 15 years as a “Programmer”, I’ve done architecture, design, programming, debugging (so much debugging), instrumentation and iteration, integration, build management, team management, and lead/director tasks. Don’t care what my title is, just pay me what I’m worth, and let me code.