• tomi000@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    6 days ago

    You forgot to mention that they will let you use it for cheap until everyone got used to it and then crank up the price by 500%

  • superkret@feddit.org
    link
    fedilink
    arrow-up
    93
    ·
    10 days ago

    Read “The Mythical Man-Month”.

    Basically, a team of 5-8 motivated developers can create high quality, medium complexity software extremely fast.
    But if the project is just a little too complex for one team of devs and you need more people, then you’ll need a lot more people. And a lot more time.

    Cause the more people you add to the project, the more overhead you have. Suddenly you need to pull devs off coding to bring new hires up to speed. You need to write documentation on coding style guidelines, hold meetings, maintain your infrastructure, negotiate with hardware suppliers, have someone fix the server room’s door locks, schedule job interviews, etc. etc.

    • darkpanda@lemmy.ca
      link
      fedilink
      arrow-up
      38
      ·
      10 days ago

      “What one programmer can do in one month, two programmers can do in two months.”

    • emergencyfood@sh.itjust.works
      link
      fedilink
      arrow-up
      7
      ·
      9 days ago

      Counterpoint: ‘The Brooks’s Law analysis (and the resulting fear of large numbers in development groups) rests on a hidden assummption: that the communications structure of the project is necessarily a complete graph, that everybody talks to everybody else. But on open-source projects, the halo developers work on what are in effect separable parallel subtasks and interact with each other very little; code changes and bug reports stream through the core group, and only within that small core group do we pay the full Brooksian overhead.’

      Source: http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s05.html

    • EnderMB@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      9 days ago

      It absolutely fucking BAFFLES me that Brooks’ Law isn’t known by every software manager on the planet.

      I’ve quoted it so many times at work, even in engineering focused teams in at least two big tech companies. It’s not a concrete fact, but it explains why so many teams are hilariously shit at delivering software.

  • starman2112@sh.itjust.works
    link
    fedilink
    arrow-up
    70
    ·
    10 days ago

    I love this meme because every app on my phone designed by a company worth more than a million dollars fucking sucks, and the best app on my phone is RIF, an app designed by a single developer, and reanimated into a lich by a team of programmers for free

  • HStone32@lemmy.world
    link
    fedilink
    arrow-up
    44
    ·
    9 days ago

    "Dear floss4life,

    Our developers have encountered an issue while using the open source framework you published on github. We have lost as many as 400 user accounts. The estimated cost of this error is $6800.

    This is unacceptable. Be a professional and fix it immediately.

    Chad Elkowitz, MBA, Gruvbert and sons Finance Lt"

    • enbipanic
      link
      fedilink
      English
      arrow-up
      18
      ·
      9 days ago

      That’s why the no warranty clause is by far the most important in any license granting access to the public

      • acockworkorange@mander.xyz
        link
        fedilink
        arrow-up
        3
        ·
        8 days ago

        And it’s also why many companies refuse to use open software. It baffles me that no insurance company saw this as a market opportunity to sell open source software insurance.

  • flashgnash@lemm.ee
    link
    fedilink
    arrow-up
    38
    ·
    9 days ago

    I’ve actually found a lot of the smaller foss tools I use are better than their proprietary counterparts because of the design philosophy and that people don’t cut as many corners on passion projects as when they’re on a deadline

    • tetris11@lemmy.ml
      link
      fedilink
      arrow-up
      6
      ·
      8 days ago

      For real. I just spent a decade in academia working dog hours with little pay keeping services running wondering how the true devs and sysadmins do it.

      I recently switched to the corporate world and have peeked behind curtain of competency: headless chickens running around, patching failing products rather than spending time to properly fix them because immediate results are the only metric that counts.

      Stability, scalability, reproducibility? Forget it, that’s someone else’s problem apparently.

      • flashgnash@lemm.ee
        link
        fedilink
        arrow-up
        3
        ·
        6 days ago

        The reason this bothers me so much is how hard it makes it to get a job

        I’ve seen people in other companies getting paid significantly more than me who just have zero clue what they’re doing

      • bastion@feddit.nl
        link
        fedilink
        arrow-up
        2
        ·
        8 days ago

        Late stage capitalism.

        The issue is that capitalism fundamentally requires forward thinkers and enlightened (or at least rational) perspective to function sustainably.

        But capitalism rewards short term thinking, everywhere from corporate leadership, to the workforce, to the consumers caught by ads designed to catch and hold their ever-shortening attention spans.

        Fundamentally, it needs regulation to thrive. The true cost of a purchase, including environmental and decommissioning/disposal costs must be tied to the initial purchase value. Through this, we might get a functional capitalism.

  • arisunz
    link
    fedilink
    arrow-up
    25
    ·
    10 days ago

    i want to boil people like this alive

    in minecraft of course

  • darkpanda@lemmy.ca
    link
    fedilink
    arrow-up
    16
    ·
    10 days ago

    “What one programmer can do in one month, two programmers can do in two months.”

  • emmie@lemmy.ml
    link
    fedilink
    arrow-up
    15
    ·
    edit-2
    9 days ago

    80/20

    I live by this rule, it made me gain so much credibility and money from people who don’t know any better. 80/20 <3

    20 percent of work nets you 80 percent of result (except no one knows what I did isn’t 100 percent) bam 4/5 of time saved. Everyone is happy and if something doesn’t work we can just blame it on client

    • FourPacketsOfPeanuts@lemmy.world
      link
      fedilink
      arrow-up
      18
      ·
      9 days ago

      I follow the 80/20 rule recursively. as soon as I’ve gotten 80% of the way there for 20% effort I immediately stop, and start a brand new project for the remaining 20%. Bam! 96% complete for only 24% effort.

      taps forehead

  • sunnie@sopuli.xyz
    link
    fedilink
    arrow-up
    14
    ·
    edit-2
    10 days ago

    the issue with this argument is that i don’t care about who made the app when it doesn’t work. that’s why i still have a chromium based secondary browser, it doesn’t matter that it’s the work of a billion dollar company trying to get a monopoly when the website i’m on is broken. yes, the blame is on who made the website, not firefox. i still need to be able to use it somehow

  • NigelFrobisher@aussie.zone
    link
    fedilink
    arrow-up
    10
    ·
    10 days ago

    “All-star” makes me worried there’s some hidden society of super competent developers remaining at the big software corps that we somehow never noticed.