Nothing is true or false when dealing with software engineering, maybe even more when dealing with object oriented software engineering. There are so many way to solve a single problem. No single solution can be named the right one without prior knowledge of the context and constraints, and even then. This blog does not claim to bring good solutions, but juts to provide feedback and to share ideas.
Feedback can take so many forms, from tests to end user demonstrations. How could there be quality without feedback? How to identify something to be right or wrong without feedback? And who knows except the end user what is good for him or her? As software engineers, our goal is (or should be) pleasing the end user, otherwise why writing software?
Pleasing the user includes both meeting the expectations and meeting them as fast as possible. Not saying to spend all nights working, but to focus on value, to automate the non valuable activities and to spend time on the one that really make the difference. Listening to the needs, designing a proper solution, writing these very user specific pieces of code that cannot be generated, providing things that are really useful, and reducing the time spend on other part of the job.
Optimizing the time to Tested Running Features (TRF comes from a reading about Scrum). Pleasing the end user / client. Everything is there, just being pragmatic.
