nulldiver

Keybase proof

I hereby claim:

• I am nulldiver on github.
• I am nulldiver (https://keybase.io/nulldiver) on keybase.
• I have a public key ASC6qoXPcF-WHsiyc6rgzR-Dl56TaR2zh715QdxXZdBx8Ao

To claim this, I am signing this object:

nulldiver

What tools can allow a team of a dozen devs to successfully ship a much larger (more ambitious, higher quality, bigger scope) game than could normally be attributed to a team that size? What about an even smaller team? A half-dozen people? 3-4 people? What does an ideal production plan look like with such small teams and large games? What new strengths surface when an entire production team can sit around a small table or talk through a challenge in a meeting where everyone can participate? If decisions are all able to be made closer to the people implementing the decisions, what does this do to iteration times? If Iterations times can be tightened, can we blur the the lines between traditional production phases? How do we play to the strengths of doing so? How do we mitigate the risks? What are the implications for the type of game that can be created  What about a team with no full-time engineers? Or, generally, if the shift moves from technical competency to creative competency? How does a "writers room" m

nulldiver

aspe:keyoxide.org:I7YAOKGZPZAFK476HRBGLS5WOM