If a woman can produce a baby in nine months, 9 women should be able to deliver a baby in one month.
Literally just used that today in an argument lol. I just know execs are going to be mad we’re running behind, I said it to suggest we do bring one person on now so they can be fully ramped up in a couple of months. Of course shot down by them
deleted by creator
deleted by creator
Edit: never mind. Reading your other comments it occurs to me you really are that obtuse.
9 women can’t deliver a baby in 1 month
They can, but the babies are probably not gonna be fine.
Tell that to Apple
deleted by creator
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.
deleted by creator
It’s not an argument it’s an analogy, that can help understand the argument.
straw man argument
You keep using that term, I don’t think you know what that term means.
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?
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
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 :
The capitalist, it is said, paid for the workers’ days; to be exact, it must be said that the capitalist paid as much ‘one day of work’ that he employed workers every day, which is not at all the same thing. Because the capitalist did not pay for this immense force which results from the union and harmony of workers, and the convergence and simultaneity of their effort. Two hundred grenadiers in a few hours erected the obelisk of Luqsor on its base; one cannot assume that a single man, in two hundred days, would have achieved the same feat.
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
lol whoever suggested that isn’t an engineer
Hiring 50 people. The most effective way to ensure a 3 month delay minimum in whatever it’s you’re trying to accomplish. More realistically between 9 and 18 months of delay. As training, project restructuring, familiarization, meetings and change management meetings take control of all the company’s time, as restructuring always takes longer than pessimistic forecasts. Also known as the MBA induced death spiral.
I’ll remember that. The MBA induced death spiral.
The only way hiring people will help you develop faster is if either:
- ramp up time is insignificant compared to project time and you don’t hire so many you hit communication overhead.
- you’re hiring people to do all the other stuff the people working on the project were also doing. I don’t think game devs typically have four systems in the maintenance lifecycle while they also develop new stuff, so that means you’re hiring a few IT folks to wrangle the weird office issues programmers wander off and deal with, a sysadmin, and like, 45 lunch delivery people.
I’ve had the first one work once, when we had a year+ project timeline. Hired one person, took them a week to get started, a month to be properly contributing and maybe another to be up to speed. We were a four person team, so not much overhead.
The second one is the dream of every manager who finds themselves with a contractor budget. I have yet to see it work the way they want. The only way I’ve seen it work is when you tell an established team that some other teams maintenance project is now their maintenance project, and eat the sharp increase in timelines for that maintenance work.Not to mention the layoffs as the game naturally dwindles from age.
That’s the interesting part. Massive layoffs is not a rare or extraneous result, it is the only possible result from the “hire 50 people now to get it done faster” mentality.
I mean. The diminishing returns on larger teams in software development is an absolutely proven idea. But according to what I’m reading, the game is made by one person, which is probably not the ideal size for a game of these characteristics that becomes a hit. Still, expanding a 1-person team is going to be a slow process no matter what, especially for a project like this and right after a successful launch.
Yeah, these projects done by one or two people could be better with a larger team, but it’s definitely not a matter of hiring a big pile of people suddenly.
The ideal size is probably a couple dozen people, but scaling up to even that will take months since the one person currently in charge has to do a lot. And it’ll almost fully pause work on the project for a while.
Cause if there’s one person, they’ve got to find all the candidates, do all the hiring, then bring people up to speed.
The real problem is if the person who made it doesn’t have the skills to manage even a small group of people.
Lol, remember when everyone was hyped about Valheim? It still isn’t finished. (Next biome is coming out soon though!)
Should I take my hype off the shelf yet? I’m still in swamp.
I’m eager for the update, I love Valheim.
Always a good idea to start a new world with each big patch too, to make sure map generation occurs properly.
Swamp is where the game starts to get hard. You need to begin using your skills for parrying and dodge rolling.
Block at the perfect time for a parry, and jump while blocking to roll.
Rolling is super powerful. If you time it the same as a parry, you’ll get invincibility frames.
Those damn deathsquitos have killed me too many times. I like the black forest.
Removed by mod
“let him cook,” says publisher
Since we’ve already bought the game. We can only be patient. I’m going to trust that it becomes a complete game in a few years.
It’s a great way to see who understands what working in IT is like. Whoever gave that advice is new to it.
Yeah for real, whoever said that is such an idiot. If he hired 5000 people instead they could get the work done 100 times faster.
And then when they lay those 50 people off in a year “Its just greed! They should be ashamed of themselves!”
