My first proper job was as a coder on a computer game. My first task was to program the way that characters turned their heads. I decided to do it so that each eye’s direction was processed independently, because I was determined that the eyes would focus properly. But the game was so zoomed out that you never saw the difference between the eyes anyway. I didn’t last long as a computer game coder.

if it’s a big system then i’d try to identify the large seperate blocks and try to keep them separated as much as possible… other than that, we just start implementing use cases within those blocks and try to avoid problems as much as we can

as for design: DDD could be useful in that situation, but not necessarily… if your really big project is just big but not very complex, then maybe DDD would be overkill… then again, maybe not. it always kinda depends.

as for the sprinter thing… a really big project is more like a marathon, starting out with a sprint is gonna make sure you’re going to have a hard time reaching that finish line . The only thing you can do is try to make sure that your progress is always sustainable.

definitely, though i don’t make promises

PS: Do you accept suggestions for BPosts