読書の記録『97 Things Every Programmer Should Know』

97 Things Every Programmer Should Know

Kevlin Henney, , 2011-12-04,

Commit each logical change in a separate operation.

Accompany each commit with an explanatory message.

Avoid committing code that will break a project's build.

Sometimes the best thing you can do to solve a problem is to put the mouse down and step away from the keyboard.

So, the next time you feel the need to improve your programming skills, don't read another book. Read code.

Insofar as we insist on Aristotelian answers, we can't ask users the right question about the user's world, and will struggle to come to the common understanding we need.

Reinventing the wheel is as important to a developer's education and skill as weightlifting is to a body builder.