Today I'm going to provide some thoughts after reading the Pragmatic Programmer book.
Here are the thoughts that caught me:
- Tag a commit, to see how many number of files affected by the bug fix.
- Find the opportunity to refine the code.
- Flexible, adaptable design.
- Deployment: stand-alone, client-server, n-tier model just by changing a configuration file.
- Domain specific language.
- Know your shell & text editor.
- Fix the problem, not the Blame.
- Bertrand Meyer.
- Design by contract for java.
- Perl for text processing.
- Pluggable exception handlers.
- Resources: memory, transactions, threads, files, timers, sockets.
- Metaprogramming.
- Large-Scale C++ Software design.
- The project needs at least two "heads" -- one technical, the other administrative. The technical head sets the development philosophy & style, assigns responsibilities to teams, and arbitrates the inevitable "discussions" between people. The technical head also looks constantly at the big picture, trying to find any unnecessary commonality between teams that could reduce the orthogonality of the overall effort. The administrative head, or project manager, schedules the resources that the teams need, monitors and reports on progress, and helps decide priorities in terms of business needs. The administrative head might also act as the team's ambassador when communication with the outside world.
- Tool builders -> Automation of project activities.
- Give each member the ability to shine in his or her own way.
- Unit testing: resource exhaustion, errors, and recovery.
- Surviving Object-Oriented Projects: A Manager's Guide: Alister Cockburn.
- Eiffel.
- Michael Holt. Math puzzles & games.
