• masinko@lemmy.world
      6·
      6 months ago

      Kind of will. There are already templates on demand for things like generating unit tests as you code. They’re pretty robust already, and have aside from a few things (or edge cases), I don’t have to do much code refactoring or fixing them.

      They already save me several hours a week from manually setting up full ones. Haven’t delved into other stuff they can do, but I’m sure it would only be more useful with time.

      I can very easily see companies looking at the time save and thinking “we can downsize”.

    • KindaABigDyl@programming.dev
      14·
      6 months ago

      This is already how the military works BC they lost the source code for ancient machines. They’ve gotta now hire reverse engineer researchers to help out

  • ulterno@lemmy.kde.socialEnglish
    28·
    6 months ago

    One of my previous employers once told me (abridged)

    It’s not like old times when we could slowly work to get a perfect result.
    Nowadays, we need perfect results, fast.

    They were asking me to do technical content writing for their website.
    I quickly realised that it’s actually the threshold for calling something “perfect”, that has lowered over time.

    Clearly, I was not fit for that work, because instead of just plagiarising and paraphrasing stuff from other websites, I insisted on reading up on material from multiple sources, understanding it well and then writing it down myself. That makes it pretty slow.

    That was a year before ChatGPT, or I would just have used that thingy.

    • KindaABigDyl@programming.dev
      13·
      6 months ago

      I agree. We’ve let the standards for what is good drop.

      I think it’s mainly because the “just works” mentality has become infectious among engineers. It’s one thing when just starting out, but as you learn more and gain experience you should care more.

      People do the designing and architecture and programming just because it all pays well, not because they have a love for the craft.

      I think the second, slightly less strong reason is because many engineers do not know how to effectively communicate with management when something will result in terribly written software and just do it anyway. Another skill I see less and less amongst my brethren.

      • ulterno@lemmy.kde.socialEnglish
        4·
        6 months ago

        People do the designing and architecture and programming just because it all pays well, not because they have a love for the craft.

        True.
        I like programming and tend to pride myself in making good code, but when I see other’s attitude at work, it makes me reevaluate what I care about.

        Perhaps this is the reason of the memetic difference between corporate code quality vs OSS code quality. When I contribute to Open Source (at least to other’s projects), I see myself try to be as considerate as possible of multiple factors that I wouldn’t even care of at work.

      • Baku@aussie.zoneEnglish
        1·
        6 months ago

        many engineers do not know how to effectively communicate with management when something will result in terribly written software and just do it anyway.

        I imagine this is partly a result of bad and misinformed managers too though. There’s a lot out there who have 0 clue wtf you do, just that you make computer do thing yet still act like they know your job better than you

        spoiler

        Not a programmer, but I see this all the time in other fields. And all it takes is someone in upper management only being focused on time or costs, or someone in middle management acting like they know better than everyone else.