I recently went through the RFC process, for the overall direction and technical solution to an internal application in my organization.
Writing a 'good' RFC
· 4 min read
I recently went through the RFC process, for the overall direction and technical solution to an internal application in my organization.
One of the first software development principles we learn is Don’t repeat yourself (DRY). It’s the principle that leads to cleaner, more compact and readable code bases. Or, is it the principle that leads computer science students and misguided programmers into redundant (over)abstractions, and code which is hard and complex to refactor?