Good programming practices

by Volker Weber

Krzysztof Kowalczyk has a wonderful list of good programming practices. I keep mumling to myself " yes, yes, yes, maybe, yes, yes ...":

- Continuous releases and daily builds. - Rather than put a bug in the bug database, first try to fix it. Don't code first and ask QA to find bugs. - The engineer who wrote the code is mostly responsible for QA. - No code is finished until the unit test is finished. - Good design results from getting something going quickly, followed by lots of quick iteration. - The best architectures evolve for a long time. - Code reviews are a regular part of development. - Difficult parts of code are best done by a team of two people working closely together.

More >


Old archive pages

I explain difficult concepts in simple ways. For free, and for money. Clue procurement and bullshit detection.


Paypal vowe