An approach to software development that is pragmatic and grounded in experience.
Rule 15. really is the Unix way. There is an important distinction between philosophies and rules and how to get the most out of them. My approach is:
- rules should be automated. Coding standards, naming, and similar
- philosophies should be taught through example and company culture
I agree, I'd probably not have called them rules, but I didn't write the book :)
Rule 15. really is the Unix way. There is an important distinction between philosophies and rules and how to get the most out of them. My approach is:
- rules should be automated. Coding standards, naming, and similar
- philosophies should be taught through example and company culture
I agree, I'd probably not have called them rules, but I didn't write the book :)