On being a faulty cog in a machine when the machine itself is faulty

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

  • onlinepersona@programming.devEnglish
    4·
    6 months ago

    I disagree, because it’s my current job. Writing code is fun when on personal projects, but at work it’s just a slog. And it’s mostly a slog because management “just wants stuff done”. And of course it’s with the demand “no bugs” aka “we want perfect systems from faulty beings”.

    I also find it wrong to measure by “lines of code”. That’s nearly the most simplistic and addle-brained measure one could assign to software developers. If there are actual software developers out there who believe in that sort of KPI, I sure don’t want to be on the same team as them.

    Anti Commercial-AI license

    • pelya@lemmy.world
      21·
      6 months ago

      That’s exactly the difference. The business needs to sell shit, so your management needs you to get the shit done, just good enough quality to sell it, because otherwise you’re burning them money in salary.

      Take any of your hobby projects, and ask yourself - ‘How do I sell this thing?’. You’ll arrive at all the same problems you are seeing in your company. Good managers will explain this and let developers make their own decisions and take part in business processes, bad managers will just dictate which buttons you need to press on your keyboard.

      Lines of code is a really ancient metric for managers who are totally ignorant of technology, I was just putting it here for emphasis.