I don’t entirely subscribe to the first paragraph – I’ve never worked at a place so dear to me that spurred me to spend time thinking about its architecture (beyond the usual rants). Other than that, spot on

  • pelya@lemmy.world
    link
    fedilink
    arrow-up
    6
    arrow-down
    5
    ·
    7 months ago

    I believe the author got the wrong job position. If your job title is something like ‘software developer’, yeah you are measured by the amount of lines of code. You should aim for a senior role such as ‘system architect’ or ‘technical lead’, then you have some kind of guidelines from the sales side of business, and your job is to turn them into requirements and produce the final product, and you choose the tech stack and other details that are inconsequential for sales bug will get the programmers flinging keyboards.

    • Clent@lemmy.world
      link
      fedilink
      arrow-up
      4
      arrow-down
      2
      ·
      7 months ago

      I agree.

      One can’t claim to love programming while calling the act of writing code being a code monkey. Whatever they actually love about the process may not exist in the industry.

      I would suggest they explore alternative roles and perhaps alternative industries. They sound like they are new to the industry so their ability to land a senior role is likely to lead to different disappointments.

      The best way to do something, often isn’t the best way to implement something. That’s why this is a senior role. The author does not appear to understand this concept and will be horribly disappointed when their perfect architecture is ignored by the realities of development.

    • Kissaki@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 months ago

      This description is so foreign to me. I guess you’re talking about big [software] companies?

      Nobody in my company, a software development company, measures by lines of code. We bring value through the software we develop and the collaborations we do.

    • rebelsimile@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      7 months ago

      yeah and/or if he wants to delve deeper into the why’s behind decision making and why we are making the software the way we are making it, he’d probably be better off in product or design.