• Squiddlioni@kbin.melroy.org
    link
    fedilink
    arrow-up
    96
    ·
    7 months ago

    It’s called Brook’s Law. It takes a lot of time and effort getting people up to speed, and that takes experienced devs away from coding. You also have to get them credentialed, teach them the tools, need extra code reviews/testing/bugfixes while they learn the quirks and pitfalls of the code base, etc. In the long term you’ll be able to get more done, but it comes at the cost of short term agility.

    • kibiz0r@midwest.social
      link
      fedilink
      English
      arrow-up
      30
      ·
      7 months ago

      but it comes at the cost of short term agility

      Often long-term agility, as well.

      Big teams are faster on straightaways. Small teams go through the corners better. Upgrading from a go-kart to a dragster may just send your project 200mph into a wall. Sometimes a go-kart is really what you need.

    • darkpanda@lemmy.ca
      link
      fedilink
      arrow-up
      25
      ·
      7 months ago

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

    • Tar_Alcaran@sh.itjust.works
      link
      fedilink
      arrow-up
      17
      arrow-down
      1
      ·
      7 months ago

      Yeah, it happens everywhere, all the time. And the main cause of it is, surprise surprise, people who have no technical understanding of the subject matter.

    • Ephera@lemmy.ml
      link
      fedilink
      arrow-up
      15
      ·
      7 months ago

      Currently in a project, where for strategic and unrelated reasons, we ended up with 4 new juniors and had to hand off one senior. In a team that consisted of merely 3 people before.

      So, it’s just me and another guy having to constantly juggle these juniors to push them back into the right direction and review whatever code they ended up with.
      It’s so frustrating, because while I’ll gladly pass on my knowledge, the project has basically ground to a halt.

      There’s so many tasks me and the other senior would like to just quickly tackle. Which should just take a few days, no big deal. Oh no, I rarely get a day’s worth of work done in two weeks. The rest is just looking after the juniors, who cannot tackle many of the actual crucial tasks.

      And it’s not even like the juniors are doing a bad job. Frankly, they’re doing amazingly for how little support we can give them. But that doesn’t stop the project from falling apart.

      • Squiddlioni@kbin.melroy.org
        link
        fedilink
        arrow-up
        28
        ·
        7 months ago

        Maybe “credentialed” wasn’t the right word. I was thinking of software licenses and access to third party tools and systems. Probably not as big a mess in game dev as it is in government.

        • IsThisAnAI@lemmy.world
          link
          fedilink
          arrow-up
          14
          ·
          7 months ago

          You mean you didn’t enjoy sitting there when your thumb up your ass while you wait 6 months for a background check and another 6 months to get your GFE? Crazy!

  • Transporter Room 3@startrek.website
    link
    fedilink
    arrow-up
    39
    arrow-down
    1
    ·
    7 months ago

    Wait, people are complaining about manor lords already? So far I like it and haven’t come across anything bothersome yet. I haven’t played a ton, but I’m getting a good village going.

    If anyone thinks hiring 50 people will get them an update in a week, they’ve never worked on a group project at all, let along a comolicated one. They’ve been working on it for what, 5 years now? And it’s just gotten what is essentially a beta buukd?

    These people need to chill out and let a good game slowly unfold, not take a promising start and try to speed run into the trash can.

    Luckily the devs are a lot smarter than the average 11 year old.

  • firadin@lemmy.world
    link
    fedilink
    arrow-up
    27
    arrow-down
    2
    ·
    7 months ago

    I mean no, but also… yes? Like having a one person dev team is a little ridiculous for a game selling as well as Manor Lords. 50 people is a lot, but do you really think the game would have less features a year from now if the dev hired like 3 people to help?

    Obviously development would slow down in the short term, but a one person dev team is asking for disaster

    • Aquila@sh.itjust.works
      link
      fedilink
      arrow-up
      3
      ·
      7 months ago

      Ideally the solo dev and visionary would cease development and move into a product owner role. Bringing other devs up to speed on the code base while also maintaining quality, vision, and cultivating a team is no trivial task. Not to mention this particular dev may not want or be able to such things.

  • dream_weasel@sh.itjust.works
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    7 months ago

    9 women cannot have a baby in 1 month obviously, that’s an assembly problem.

    What you need is 1 woman and 9 men.

  • Crampon@lemmy.world
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    7 months ago

    I bought it to support it. Haven’t played it yet, but i will sooner or later. Let the guy cook.

  • 𝓔𝓶𝓶𝓲𝓮@lemm.ee
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    7 months ago

    Quality over quantity. I have seen people who have done things better and faster than a whole team. I am almost one of them but alas I only work for few hours before deadline. If I could work like this every day I would single handedly build everything. It kinda bugs me what stuff I could do if I didn’t suffer and delay it all feeling mix of guilt and shame.

  • yamanii@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    7 months ago

    People were very critical of valheim too for not updating faster, they really don’t care.

  • FiniteBanjo@lemmy.today
    link
    fedilink
    arrow-up
    2
    arrow-down
    2
    ·
    7 months ago

    The Open Source development approach makes it a lot easier because you don’t necessarily have to train devs at all you just need to review pull requests and examine some of the forks.