• themaninblack@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 hour ago

    Being obtuse for a moment, let me just say: build it right!

    That means minimalism! No architecture astronauts! No unnecessary abstraction! No premature optimisation!

    Lean on opinionated frameworks so as to focus on coding the business rules!

    And for the love of all that is holy, have your developers sit next to the people that will be using the software!

    All of this will inherently reduce runaway algorithmic complexity, prevent the sort of artisanal work that causes leakiness, and speed up your code.

  • vane@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    edit-2
    3 hours ago

    Quality in this economy ? We need to fire some people to cut costs and use telemetry to make sure everyone that’s left uses AI to pay AI companies because our investors demand it because they invested all their money in AI and they see no return.

  • The_Decryptor@aussie.zone
    link
    fedilink
    English
    arrow-up
    6
    ·
    3 hours ago

    The calculator leaked 32GB of RAM, because the system has 32GB of RAM. Memory leaks are uncontrollable and expand to take the space they’re given, if you had 16MB of RAM in the system then that’s all it’d be able to take before crashing.

    Abstractions can be super powerful, but you need an understanding of why you’re using the abstraction vs. what it’s abstracting. It feels like a lot of them are being used simply to check off a list of buzzwords.

  • PattyMcB@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    4 hours ago

    Non-technical hiring managers are a bane for developers (and probably bad for any company). Just saying.

  • geoff@midwest.social
    link
    fedilink
    English
    arrow-up
    11
    ·
    6 hours ago

    Anyone else remember a few years ago when companies got rid of all their QA people because something something functional testing? Yeah.

    The uncontrolled growth in abstractions is also very real and very damaging, and now that companies are addicted to the pace of feature delivery this whole slipshod situation has made normal they can’t give it up.

  • afk_strats@lemmy.world
    link
    fedilink
    English
    arrow-up
    13
    ·
    7 hours ago

    Accept that quality matters more than velocity. Ship slower, ship working. The cost of fixing production disasters dwarfs the cost of proper development.

    This has been a struggle my entire career. Sometimes, the company listens. Sometimes they don’t. It’s a worthwhile fight but it is a systemic problem caused by management and short-term profit-seeking over healthy business growth

    • ryathal@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 hours ago

      There’s levels to it. True quality isn’t worth it, absolute garbage costs a lot though. Some level that mostly works is the sweet spot.

    • dual_sport_dork 🐧🗡️@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      7 hours ago

      “Apparently there’s never the money to do it right, but somehow there’s always the money to do it twice.”

      Management never likes to have this brought to their attention, especially in a Told You So tone of voice. One thinks if this bothered pointy-haired types so much, maybe they could learn from their mistakes once in a while.

      • ozymandias117@lemmy.world
        link
        fedilink
        English
        arrow-up
        7
        ·
        5 hours ago

        We’ll just set up another retrospective meeting and have a lessons learned.

        Then we won’t change anything based off the findings of the retro and lessons learned.

        • PattyMcB@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          4 hours ago

          Post-mortems always seemed like a waste of time to me, because nobody ever went back and read that particular confluence page (especially me executives who made the same mistake again)

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

            Post mortems are for, “Remember when we saw something similar before? What happened and how did we handle it?”

    • HertzDentalBar@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      3
      ·
      6 hours ago

      That applies in so many industries 😅 like you want it done right… Or do you want it done now? Now will cost you 10x long term though…

      Welp now it is I guess.

      • PattyMcB@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 hours ago

        You can have it fast, you can have it cheap, or you can have it good (high quality), but you can only pick two.

    • Blackmist@feddit.uk
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      2
      ·
      4 hours ago

      The sad thing is that velocity pays the bills. Quality it seems, doesn’t matter a shit, and when it does, you can just patch up the bits people noticed.

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

        This is survivorship bias. There’s probably uncountable shitty software that never got adopted. Hell, the E.T. video game was famous for it.

  • chunes@lemmy.world
    link
    fedilink
    English
    arrow-up
    23
    arrow-down
    1
    ·
    9 hours ago

    Software has a serious “one more lane will fix traffic” problem.

    Don’t give programmers better hardware or else they will write worse software. End of.

    • nelson@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      ·
      8 hours ago

      This is very true. You don’t need a bigger database server, you need an index on that table you query all the time that’s doing full table scans.

      • GenosseFlosse@feddit.org
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        edit-2
        4 hours ago

        You never worked on old code. It’s never that simple in practice when you have to make changes to existing code without breaking or rewriting everything.

        Sometimes the client wants a new feature that cannot easily implement and has to do a lot of different DB lookups that you can not do in a single query. Sometimes your controller loops over 10000 DB records, and you call a function 3 levels down that suddenly must spawn a new DB query each time it’s called, but you cannot change the parent DB query.

  • panda_abyss@lemmy.ca
    link
    fedilink
    English
    arrow-up
    45
    ·
    11 hours ago

    I’ve been working at a small company where I own a lot of the code base.

    I got my boss to accept slower initial work that was more systemically designed, and now I can complete projects that would have taken weeks in a few days.

    The level of consistency and quality you get by building a proper foundation and doing things right has an insane payoff. And users notice too when they’re using products that work consistently and with low resources.

    • Telorand@reddthat.com
      link
      fedilink
      English
      arrow-up
      14
      ·
      10 hours ago

      This is one of the things that frustrates me about my current boss. He keeps talking about some future project that uses a new codebase we’re currently writing, at which point we’ll “clean it up and see what works and what doesn’t.” Meanwhile, he complains about my code and how it’s “too Pythonic,” what with my docstrings, functions for code reuse, and type hints.

      So I secretly maintain a second codebase with better documentation and optimization.

      • panda_abyss@lemmy.ca
        link
        fedilink
        English
        arrow-up
        6
        arrow-down
        1
        ·
        9 hours ago

        How can your code be too pythonic?

        Also type hints are the shit. Nothing better than hitting shift tab and getting completions and documentation.

        Even if you’re planning to migrate to a hypothetical new code base, getting a bunch of documented modules for free is a huge time saver.

        Also migrations fucking suck, you’re an idiot if you think that will solve your problems.

  • IrateAnteater@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    57
    ·
    12 hours ago

    I think a substantial part of the problem is the employee turnover rates in the industry. It seems to be just accepted that everyone is going to jump to another company every couple years (usually due to companies not giving adequate raises). This leads to a situation where, consciously or subconsciously, noone really gives a shit about the product. Everyone does their job (and only their job, not a hint of anything extra), but they’re not going to take on major long term projects, because they’re already one foot out the door, looking for the next job. Shitty middle management of course drastically exacerbates the issue.

    I think that’s why there’s a lot of open source software that’s better than the corporate stuff. Half the time it’s just one person working on it, but they actually give a shit.

    • MotoAsh@piefed.social
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      6
      ·
      edit-2
      10 hours ago

      Definitely part of it. The other part is soooo many companies hire shit idiots out of college. Sure, they have a degree, but they’ve barely understood the concept of deep logic for four years in many cases, and virtually zero experience with ANY major framework or library.

      Then, dumb management puts them on tasks they’re not qualified for, add on that Agile development means “don’t solve any problem you don’t have to” for some fools, and… the result is the entire industry becomes full of functionally idiots.

      It’s the same problem with late-stage capitalism… Executives focus on money over longevity and the economy becomes way more tumultuous. The industry focuses way too hard on “move fast and break things” than making quality, and … here we are, discussing how the industry has become shit.

      • Croquette@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        4
        ·
        4 hours ago

        My hot take : lots of projects would benefit from a traditional project management cycle instead of trying to force Agile on every projects.

        • MotoAsh@piefed.social
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          1
          ·
          57 minutes ago

          Agile SHOULD have a lot of the things ‘traditional’ management looks for! Though so many, including many college teachers I’ve heard, think of it way too strictly.

          It’s just the time scale shrinks as necessary for specific deliverable goals instead of the whole product… instead of having a design for the whole thing from top to bottom, you start with a good overview and implement general arch to service what load you’ll need. Then you break down the tasks, and solve the problems more and more and yadda yadda…

          IMO, the people that think Agile Development means only implement the bare minimum … are part of the complete fucking idiot portion of the industry.

      • sp3ctr4l@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        9
        ·
        edit-2
        9 hours ago

        Shit idiots with enthusiasm could be trained, mentored, molded into assets for the company, by the company.

        Ala an apprenticeship structure or something similar, like how you need X years before you’re a journeyman at many hands on trades.

        But uh, nope, C suite could order something like that be implemented at any time.

        They don’t though.

        Because that would make next quarter projections not look as good.

        And because that would require actual leadership.

        This used to be how things largely worked in the software industry.

        But, as with many other industries, now finance runs everything, and they’re trapped in a system of their own making… but its not really trapped, because… they’ll still get a golden parachute no matter what happens, everyone else suffers, so that’s fine.

        • MotoAsh@piefed.social
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          6 hours ago

          Exactly. I don’t know why I’m being downvoted for describing the thing we all agree happens…

          I don’t blame the students for not being seasoned professionals. I clearly blame the executives that constantly replace seasoned engineers with fresh hires they don’t have to pay as much.

          Then everyone surprise pikachu faces when crap is the result… Functionally idiots is absolutely correct for the reality we’re all staring at. I am directly part of this industry, so this is more meant as honest retrospective than baseless namecalling. What happens these days is idiotry.

          • sp3ctr4l@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            2
            ·
            5 hours ago

            Yep, literal, functional idiots, as in, they keep doing easily provably as stupid things, mainly because they are too stubborn to admit they could be wrong about anything.

            I used to be part of this industry, and I bailed, because the ratio of higher ups that I encountered anywhere, who were competent at their jobs vs arrogant lying assholes was about 1:9.

            Corpo tech culture is fucked.

            Makes me wanna chip in a little with a Johnny Silverhand solo.

            • MotoAsh@piefed.social
              link
              fedilink
              English
              arrow-up
              1
              arrow-down
              1
              ·
              1 hour ago

              Fuck man, why don’t more ethical-ish devs join to make stuff? What’s the missing link on top of easy sharing like FOSS kinda’ already has?

              Obviously programming is a bit niche, but fuck… how can ethical programmers come together to survive under capitalism? Sure, profit sharing and coops aren’t bad, but something of a cultural nexus is missing in this space it feels…

      • WanderingThoughts@europe.pub
        link
        fedilink
        English
        arrow-up
        3
        ·
        10 hours ago

        That’s “disrupting the industry” or “revolutionizing the way we do things” these days. The “move fast and break things” slogan has too much of a stink to it now.

        • MotoAsh@piefed.social
          link
          fedilink
          English
          arrow-up
          4
          arrow-down
          1
          ·
          edit-2
          6 hours ago

          Probably because all the dummies are finally realizing it’s a fucking stupid slogan that’s constantly being misinterpreted from what it’s supposed to mean. lol (as if the dummies even realize it has a more logical interpretation…)

          Now if only they would complete the maturation process and realize all of the tech bro bullshit runs counter to good engineering or business…

  • kayazere@feddit.nl
    link
    fedilink
    English
    arrow-up
    16
    ·
    edit-2
    10 hours ago

    Another big problem not mentioned in the article is companies refusing to hire QA engineers to do actual testing before releasing.

    The last two American companies I worked for had fired all the QA engineers or refused to hire any. Engineers were supposed to “own” their features and test them themselves before release. It’s obvious that this can’t provide the same level of testing and the software gets released full of bugs and only the happy path works.

  • panda_abyss@lemmy.ca
    link
    fedilink
    English
    arrow-up
    16
    ·
    11 hours ago

    Fabricated 4,000 fake user profiles to cover up the deletion

    This has got to be a reinforcement learning issue, I had this happen the other day.

    I asked Claude to fix some tests, so it fixed the tests by commenting out the failures. I guess that’s a way of fixing them that nobody would ever ask for.

    Absolutely moronic. These tools do this regularly. It’s how they pass benchmarks.

    Also you can’t ask them why they did something, they have no capacity of introspection, they can’t read their input tokens, they just make up something that sounds plausible for “what were you thinking”.

    • MelodiousFunk@slrpnk.net
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      1
      ·
      10 hours ago

      Also you can’t ask them why they did something, they have no capacity of introspection, (…) they just make up something that sounds plausible for “what were you thinking”.

      It’s uncanny how it keeps becoming more human-like.

      • MotoAsh@piefed.social
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        9 hours ago

        No. No it doesn’t, ALL human-like behavior stems from its training data … that comes from humans.

    • FishFace@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 hours ago

      The model we have at work tries to work around this by including some checks. I assume they get farmed out to specialised models and receive the output of the first stage as input.

      Maybe it catches some stuff? It’s better than pretend reasoning but it’s very verbose so the stuff that I’ve experimented with - which should be simple and quick - ends up being more time consuming than it should be.

      • panda_abyss@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 hours ago

        I’ve been thinking of having a small model like a long context qwen 4b run and do quick code review to check for these issues, then just correct the main model.

        It feels like a secondary model that only exists to validate that a task was actually completed could work.

        • FishFace@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 hours ago

          Yeah, it can work, because it’ll trigger the recall of different types of input data. But it’s not magic and if you have a 25% chance of the model you’re using hallucinating, you probably end up still with an 8.5% chance of getting bullshit after doing this.

  • Pika@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    16
    ·
    12 hours ago

    I’m glad that they added CloudStrike into that article, because it adds a whole extra level of incompetency in the software field. CS as a whole should have never happens in the first place if Microsoft properly enforced their stance they claim they had regarding driver security and the kernel.

    The entire reason CS was able to create that systematic failure was because they were(still are?) abusing the system MS has in place to be able to sign kernel level drivers. The process dodges MS review for the driver by using a standalone driver that then live patches instead of requiring every update to be reviewed and certified. This type of system allowed for a live update that directly modified the kernel via the already certified driver. Remote injection of un-certified code should never have been allowed to be injected into a secure location in the first place. It was a failure on every level for both MS and CS.