The Pragmatic Programmer

by Andy Hunt

Prototyping is a learning experience. Its value lies not in the code produced, but in the lessons learned. That's really the point of prototyping.

Important concept to undetrstand

This problem is a kind of "Heisenbug"—debugging that changes the behavior of the system being debugged

The O() notation puts an upper bound on the value of the thing we're measuring (time, memory, and so on).

Yep.

The O() notation doesn't apply just to time; you can use it to represent any other resources used by an algorithm. For example, it is often useful to be able to model memory consumption

Bring back memorie of other famous book :)

Don't be a slave to any notation;

Bloody impotant.

Requirements are not architecture. Requirements are not design, nor are they the user interface. Requirements are need.

Spot on!

Don't Think Outside the Box—Find the Box

Rigtho!!

Listen to Nagging Doubts—Start When You're Ready

Worth to ponder.

Let your instincts contribute to your performance.

This is how I backup myself.