Dream Break Code reading Note II

08 Dream Break Code read the second note

VI. Bundle the Geek and the dog

The task of management is to enable people to work together, to benefit their strengths, weak their shortcomings. Numbers are just a starting point for management, not an end point.

Software productivity is less reliable in terms of code lines.

Informal mechanisms are always there, and it is dangerous to change them if they are not really understood, to avoid disrupting systems that are running smoothly and that you cannot replace at the same cost.

Seven, the design plan

Don't be bigger than the project. Start with a small project, and never expect it to grow larger. If you think so (referring to big software), you'll do over-design and think of it as too important. Worse, you may be intimidated by the hard work you imagine. So to start from a small place, focus on the details. Don't think about the big picture and the design. If the project does not address certain requirements, it is mostly over-engineered.

Don't expect to achieve great results in a short period of time.

Each puzzle has its uniqueness, so it is necessary to learn and to do things in order to occupy a favorable position. Standing in the right place, you can decide what to discard-the code is worthless. But it often tells you what to do next.

Eight, detail view

It's written in the specs! Or, it's not written in the specs! This is the inevitable repetition of every software project that is hampered. Specifications translate the requirements-the goals or aspirations of a software developer's client-into a detailed March instruction for the command programmer.

The stamping mechanism is designed to give computer desktops a productive ambiguity that is closer to reflecting the way people think.

The tolerance of human language is strong.

Nine, the whiteboard on the instant sticker

Instant stickers on the whiteboard can save a lot of time.

Dream Break Code reading Note II