Two days reading the first chapter Pragmatic Programmer's Road, feeling a lot.
Pragmatic Programmers pragmatic thinking from focusing on philosophy.
Pragmatic programmer features: their ability to deal with the problem, find a solution to the problem of style, attitude and philosophy. They can direct themselves to think beyond question,
And we can not, it is worth thinking about, always on the big issues in the context ,, always tried to catch the bigger picture ,, try to keep the bigger picture,
Not a larger context, there is no way to pragmatic, there is no greater way to do pure compromise longer-term outlook.
One of the reasons is that they are very successful programmer is responsible for everything, they will not look at the project landslides watts. Time-sensitive programmer responsible for their own career, and not afraid to admit ignorance or error, although there are thoroughly tested, well documented, and enough automation, things still go wrong, delivered late, there has never met the technical problem.
We are proud of our ability, but for our shortcomings - and our shortcomings - our ignorance and our mistakes - we have to be honest.
You take the initiative to assume responsibility for something. You committed to ensuring that something is done correctly, but can not control every aspect of the matter, in addition to do what we can, but must analyze whether the risk out of control. Impossible or too risky for something, it must judge based on guidelines criteria.
Although the software development is almost not bound by the laws of physics, the influence entropy is great for us ,, Entropy is a concept of physics, refers to the total amount of disorder in a system, unfortunately, the laws of thermodynamics guarantee the universe tend to maximize entropy, when no need to increase the software, referred to as software rot.
Development of mental decay will trigger the software, even though the person in charge to develop software, to develop the best plan, with better developer, the project is still likely to face destruction and decay in their lifetime.
Can not keep the "broken windows" (poor design, bad decisions, or poor code) do not repair, a repair found one, if there is no time to properly repair it with wooden planks and nailed it up. Clean, well-functioning system, once the windows began to break, the equivalent of a rapidly aging.
Team code neat and tidy personal code of impact, everyone do not want to be the first political destruction of people.
Demand for goods at writing software from clients ,, we usually ask customers want more than good software, and sometimes there is no choice, if teams like pacemakers, spacecraft, it would need a rigorous.