• Zarobi@aussie.zone
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    11 hours ago

    Most of my career I was allowed to write code how I wanted. I made it beautiful and nice to read. It was genuinely fun to find the best way to implement each feature.

    My final job, I was forced to add semicolons on new lines for each if else statement, even for early returns, remove hyphens from my comments because they were “improper grammar”, put a useless giant copy pasted comment at the start of each file so you can’t even see any code without scrolling, one separate file for each class even if it’s an internal helper class used nowhere else, and use interfaces and MVVM for literally everything, even when it was severely over-engineering (or should I say overengineering). It just felt soul crushing to make this ugly ass code that took forever to write, just because the style guide said so.

    Then A.I. happened and I quit being a software engineer completely. Telling an A.I. to do my work for me is just depressing. What’s even the point anymore? I still code for fun but I’m done with the industry.

    • vinnymac@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 hours ago

      These days it’s very common to write whatever code you want, and a formatter automatically rewrites it to conform to the projects rules during precommit.

      Which is great because it allows you to focus on intent instead of format, and completely avoids any team disagreements or change rejections for trivial bullshit.

      • Zarobi@aussie.zone
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 hours ago

        My favourite part is when your style or the auto formatter changes over time and you have to decide between:

        • running the auto formatter on 200,000 12 year old code files
        • doing them one by one
        • formatting them when you have to change that file
        • or ignoring all the warnings forever (it’s this one, this is what you do)

        Plus it doesn’t fix the problem of auto formatters writing ugly code. You can’t easily tell the auto formatter that early returns can be bracketless for brevity, but nothing else can be. Unless you add a comment like \\ ignore-rule-2753674 which makes me want to throw up

    • Bobby Turkalino@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      8 hours ago

      I wish I could work somewhere like your first paragraph. My career has been your second paragraph, probably because I’ve only worked on medical devices and we gotta have higher standards than a lot of developers. It also got taken a bit too much to the extreme tho

      • Zarobi@aussie.zone
        link
        fedilink
        English
        arrow-up
        2
        ·
        7 hours ago

        Believe it or not my first paragraph was working on medical software lol. It was good though, I liked the feeling of helping doctors help people, making the world a better place.

    • Mereo@piefed.ca
      link
      fedilink
      English
      arrow-up
      4
      ·
      10 hours ago

      If you don’t mind me asking, to which career did you switch to?

      • Zarobi@aussie.zone
        link
        fedilink
        English
        arrow-up
        5
        ·
        edit-2
        7 hours ago

        Unemployed / disability lol. But if I could still move around I’d probably get into something outdoorsy. Park ranger or the like. Keeping a candle lit though, in case one day I miraculously recover or medical science advances or something.

        Edit: actually it’s the reason I did software engineering in the first place. But actually this industry is now hostile to people with disability. Can I work from home because leaving the house is hard? No, everyone must be in office chained to your desk 9/9/6. Can I be neurodivergent? No, everyone must have constant in person meetings and work in open plan offices.