Skip to main content

Blog Archive for jst during January 2009

For a while I was desperately expecting an important moment. Since I wrote the Practical API Design book, and since its amazon page was created, I've been waiting for first customer review. Almost daily, at least at the beginning, I was watching whether it had already appeared or not. I always opened the book's page being afraid of what I would find. I feared to see something like unreadable,...
When you maintain some code and you get a patch that you do not like, what can you do? Is the only option to refuse the change, or is there a better way? Of course, as this was just a rhetorical question, there is better solution: Just create a code slot!