A set of opinionated principles for writing disciplined C code, covering maintainability over cleverness, avoiding macros and magic abstractions, recognizing dangerous patterns like buffer overflows and unsafe string functions, organizing code into files and modules, sticking to standard (non-GNU) features, maintaining a disciplined git workflow with meaningful commit messages, thorough testing and code review, and learning from bugs by fixing the underlying process, not just the symptom.
Sort: