I was quoted in the O’Reilly Media report, “The Secrets Behind Great One-on-One Meetings”. As an engineering manager, I appreciated it whenever my reports would bring a topic to the 1-on-1, whether it was a technical topic or a career or mentorship topic.
Cause and effect diagrams, also known as Ishikawa diagrams, are one of 7 basic tools of quality. Cause and effect diagrams are useful because they let you list out all the causes that you and/or your team can think of. Having a team think of possible causes is similar to the concept of peer review in software development projects. Where one person thinks of a few causes, another person will think of different causes. This gives a broader range of causes to investigate.
At its core, SEMAT consists of three layers: customer, solution and endeavour. Each “alpha” component of each layer has a checklist to see which progress level it is at.
JsonCpp is a good solid C++ library to work with. JsonCpp gives you the ability to open JSON configuration files.
The project was a software prototype for a restaurant ordering system. The goal was to design a user interface that allowed a customer in the restaurant to use their iPhone or some other smart phone to quickly order food. For this prototype, I used Squeak Smalltalk, the Seaside web framework, and the Magritte meta-description framework. As the database for this prototype, I used a class with only class methods. It used Dictionaries to store the data, just a plain key-store database.