As someone who spent years as a ‘big company engineer’, the reason I don’t write code until the bosses have clear requirements is because I don’t want to do it twice.
That and it isn’t just me, there’s 5 other teams who have to coordinate and they have other things on their roadmap that are more important than a project without a spec.
As another senior software developer, but at smaller companies, this was my answer as well.
If I start right away, the idea they had in their had but couldn’t put on paper will emerge as “No, that’s wrong” about a million times, trying to coax my idea into being their idea.
If I wait for their idea to be on paper, they’re stuck for it and if I do what they said, even if it’s awful, there’s no consequence to me. If I do what I wanted, even if it’s amazing, it’ll be destroyed in front of me and they’ll think I’m a screwup because I didn’t do what they wanted.
If you’re one of the people that control the company, you can afford complete creative freedom. If you aren’t, everything you do will be crushed in front of you, and you’ll just have to work harder to get back up to speed with what they really wanted.
And I don’t even have the “5 other teams” problem, since I’ve been in small companies. That would make it 10x worse.
I get it, but it seems frustrating to me. Another commenter suggested that a difficulty in non-game development is there is not really a right answer except the consensus answer. Unlike a game, it’s not something you can just feel on your own.
As someone who spent years as a ‘big company engineer’, the reason I don’t write code until the bosses have clear requirements is because I don’t want to do it twice.
That and it isn’t just me, there’s 5 other teams who have to coordinate and they have other things on their roadmap that are more important than a project without a spec.
As another senior software developer, but at smaller companies, this was my answer as well.
If I start right away, the idea they had in their had but couldn’t put on paper will emerge as “No, that’s wrong” about a million times, trying to coax my idea into being their idea.
If I wait for their idea to be on paper, they’re stuck for it and if I do what they said, even if it’s awful, there’s no consequence to me. If I do what I wanted, even if it’s amazing, it’ll be destroyed in front of me and they’ll think I’m a screwup because I didn’t do what they wanted.
If you’re one of the people that control the company, you can afford complete creative freedom. If you aren’t, everything you do will be crushed in front of you, and you’ll just have to work harder to get back up to speed with what they really wanted.
And I don’t even have the “5 other teams” problem, since I’ve been in small companies. That would make it 10x worse.
I get it, but it seems frustrating to me. Another commenter suggested that a difficulty in non-game development is there is not really a right answer except the consensus answer. Unlike a game, it’s not something you can just feel on your own.