this post was submitted on 04 May 2024
255 points (98.9% liked)
Games
16785 readers
837 users here now
Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc..
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc..)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Some tasks are serializable other tasks are sequential.
A lot of game dev tasks are sequential, the code to do thing X has to be developed before feature Y can be implemented. And you can only have one dev working on one feature at a time, even version control has its limits.
It's not an argument it's an analogy, that can help understand the argument.
It's an argument about critical paths in a project. Also, is no-one going to credit "The Mythical Man Month" where this quote comes from?
You keep using that term, I don't think you know what that term means.
How is it a strawman to compare one set of serial tasks to another? Do you not understand what a strawman actually is? Can you elaborate on your logic?
It seems like both of your analogies are strawmen. Game development is likely to be not like pregnancy or moving stones, in terms of its ability to be sped up by adding manpower. It's obviously much more complicated than manual labour like moving stones, but not as immune to assistance as passively 'being pregnant'.
A metaphor is not a strawman.
Super, a super simple task you can throw more people at.
The cake one I like because it highlights that this is a complex task where more people are going to get in the way. If you throw 5 more people into baking a cake halfway through it's going to take 5 times as long because now you have to explain to them what you were doing, what your system is, how they should work together as a team. The overhead of adding them isn't worth it, and you'd probably just say "go stand over there I'll finish it"
Now, if you knew ahead of time you had an order for 50 cakes and you were given 5 people, now that's a completely different problem to solve. You now have a leader, tell this person is on mixing, this person is on frosting, etc etc.
So, in short, it's clear you aren't an engineer, and it's extremely clear you don't know what a strawman is
It's not even that more people get in the way. A cake, and a baby, and in some ways dev work, take a set amount of time under which you just can't do, or you get an undercooked baby, or a miscarried cake.
They could, but they wouldn't, they would organize their work to be more productive and achieve the stone moving faster.
Paraphrasing Proudhon's What Is Property :
Hiring 50 people to work on a project fundamentally changes the way the project is led compared to how it was by a single person, suddenly you will need additional workers to plan for the work to be done, to organize each task, to keep track of what's being done, and whatnot. Howard claimed there were 450 people working at Bethesda, and look at the state of Starfield ; Larian Studios allegedly grew from 100 to 400 people, and look at the state of Baldur's Gate 3 ; ZA/UM reported laying off 25% of their workforce, implying they were a team of 100, and look at the state of Disco Elysium (on release and/or Director's Cut, the ongoing legal battle is a whole other subject), it's a lot more complex that just numbers