• Squiddlioni@kbin.melroy.org
    link
    fedilink
    arrow-up
    0
    ·
    2 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.

    • darkpanda@lemmy.ca
      link
      fedilink
      arrow-up
      0
      ·
      2 months ago

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

  • Transporter Room 3@startrek.website
    link
    fedilink
    arrow-up
    0
    ·
    2 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
    0
    ·
    2 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
      0
      ·
      2 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.