3 ms·
So the guru stage involves no unit tests? I have to admit that when I program on my own I never write unit tests. But in a corporate environment it's blasphem
by logn 14y ago
So the guru stage involves no unit tests? I have to admit that when I program on my own I never write unit tests. But in a corporate environment it's blasphemy. Plus on my own (solo) projects I know the app like the back of my hand and it's a reasonable size so I can keep everything smoke tested. But on large corporate projects it's really easy to add a showstopper you never notice. I'd like to hear the author talk more about this (or commenters).
- thedudemabry 14y agoI'm nowhere near the guru stage, but I'm definitely down with convention over conviction. No matter what stage you're in (or even alternate paths), making your code communicate your intent to your coworkers is much more important than penning your magnus opus. It's okay for freshly-minted programmers to blindly follow the patterns of the grey-hairs and for the zealous to write heathen code, depending on who will be maintaining the project in six months. The equilibrium of the team will balance as everyone learns through building good product. I agree with you on personal projects, as well. Do whatever lets you meet your goal, whether that be learning how to hardcore TDD or getting a horribly-written, hacky project out to your friends.