Kent Beck has a good article on Medium titled, Programmer Test Principles.
Some long time ago I was working on a large software development project, and I wasn’t happy with either the quality or the velocity of our programming effort. So one night I sat down and tried to work out an activity diagram to show what our software development process needed to be, to improve both speed and quality. It turns out that a lot of this is just common sense, but for some reason or another team members would try to circumvent the process, which always led to more pain for everyone involved.
Programmers can celebrate Christmas on Halloween:
31 oct = 25 dec
(3*8 + 1) == (2*10 + 5)
This is a page from my book, “A Survival Guide for New Consultants”
At this point the pure “consulting” portion of this book has ended. As a bonus section to this book, I’ve included a collection of short stories that are related to your “career” in general.
Because I worked at least ten different jobs before graduating college, then started my career as an aerospace engineer, then switched to being a Unix Administrator, then a Programmer, and then a Programming Consultant, I’ve had the opportunity to see hundreds of work situations, and I’ve thought a lot about what I wanted in my career.
“I’m not a great programmer; I’m just a good programmer with great habits.”
~ Kent Beck
“Besides a mathematical inclination, an exceptionally good mastery of one’s native tongue is the most vital asset of a competent programmer.”
~ Edsger Dijkstra
What programmers say vs what they really mean. From this Twitter post.
From the website:
“Dailyprogrammer is about challenging programmers of all skill level with weekly programming challenges. 3 challenges a week are posted at increasing difficulty. Solutions are peer reviewed and redditors can ask for the community for feedback and comments.”