Code clean way programmers professionalism reading notes
Author [USA] Robert C.Martin
The book mainly to solve the problem
What is software professionals
Software professionals how to act
How to deal with conflicts software professionals to deal with a very tight schedule, and how to deal with unreasonable managers?
When software professionals should say "no"? How to say?
Software professionals how to cope with stress
The first chapter professionalism
1.1 What you should know
1.2 to assume responsibility
1.3 First of all, no matter the damage
1.4 Professional Ethics
Career development is your own business. Employers have no obligation to make sure you invincible in the workplace, there is no obligation to train you, send you to attend meetings or to buy all kinds of books you charge. These are your own thing. Their career employer hopes software developers will be miserable.
1.4.1 Know your field
Matters must be proficient in
1. Design patterns, GOF patterns 24
2. Design principles, must understand SOLID principles, but also a deep understanding of the principles of design components
3. The method, we must understand XP, scrum, Lean, Kanban, Waterfall, structured analysis and structured design
4. Practice. Must master the test-driven development, object-oriented design, structured programming, continuous integration and pair programming
The workpiece, the UML diagram, the DFD diagram, a structure in FIG, petri network diagram, state transition diagrams, flowcharts and decision tables
1.4.2 insist on learning
Learn other languages
1.4.3 Exercise
Kata is often in the form of a simple programming problem to be solved, such as writing an integer calculation to split the prime factor. Purpose of this exercise is not to find a solution, but to train your fingers and brain.
Might sooner or later be a 10-minute kata it, as is the warm-up exercises or elaborate process.
1.4.4 Cooperation
1.4.5 Guidance
1.4.6 understand business
1.4.7 consistent with the employer / client
1.4.8 humility
Chapter VI Exercises
Whether or fight programming, speed is the origin and practice. And both practice and did not make any difference. We chose a series of problems and solutions, again and again to practice until thoroughly cooked in the heart.
· Chapter IX Time Management
Split time and Pomodoro
Avoid: Priority confusion, dead end, mire
The Rule of Holes If you fell into the hole, do not dig