Code is read more than written conveys that it's usually good to make the code maintainable by keeping it simple, writing tests and documentation, etc. It's a reminder that the person first writing a piece of code shouldn't buy convenience at the expense of the people who will have to read it and modify it in the future. It's about having perspective over the software development cycle.
This line of thought can be extended beyond code-writing and used as a rule of thumb to identify problems and make decisions.
Code is a means to an end. Software should have a purpose, it's supposed to provide a service to some user. It doesn't matter how well written or maintainable the code is, nor how sophisticated the technology it uses if it doesn't fulfill its purpose and provides a good experience to the user.
This is why, instead of guessing or asking what they need, it's best to put the program in front of the users early and frequently and to incorporate what we learn from their feedback.
View Full Article
No entries found