3 ms·
That's exactly what I meant. Ideally, I first write classes public interface (it's especially easy in C/C++, it's just an almost complete header file), then wri
by golergka 12y ago
That's exactly what I meant. Ideally, I first write classes public interface (it's especially easy in C/C++, it's just an almost complete header file), then write some code that uses it to ensure that it is easy and intuitive to use, then unit tests, and only after that get to implementation. It's not always possible to follow this flow all the time (I work in the game industry and unit testing is seldom used, unfortunately), but I always find that I write better code when I follow it.