3.1. Prototype to Learn.
Prototyping is a learning experience. Its value lies not in the code you produce, but in the lessons you learn.
3.2. Program Close to the Problem Domain.
Design and code in the language of the problem domain.
3.3. Estimate to Avoid Surprises.
Estimate before you start. You’ll spot potential problems up front.
3.4. Iterate the Schedule with the Code.
Use experience you gain as you implement to refine the project time scales.
3.5. Keep Knowledge in Plain Text.
Plain text won’t become obsolete. It helps leverage your work and simplifies debugging and testing.
3.6. Use the Power of Command Shells.
Use the shell when graphical user interfaces don’t cut it.
3.7. Achieve Editor Fluency.
An editor is your most important tool. Know how to make it do what you need, quickly and accurately.
3.8. Always Use Version Control.
Version control is a time machine for your work; you can go back.
3.9. Fix the Problem, Not the Blame.
It doesn’t really matter whether the bug is your fault or someone else’s—it is still your problem, and it still needs to be fixed.
3.10. Don’t Panic.
This is true for galactic hitchhikers and for developers.
Thanks for reading, happy coding 😀
Top comments (0)