why my separation of concerns Database/Business objects/Web service, makes me write more code ?
Your personal productivity is not the point. The point of separation of concerns is to increase the value of the software you produce by making it usable, maintainable and adaptable. I’m sorry if this makes you write more code, but your time is typically a tiny fraction of the life-time cost of using, maintaining and adapting what you’re writing. Separation of concerns is essentially for keeping the life-long total cost of ownership down. It has little to do with your personal productivity. If your boss is asking you for a pervasive change… well… it’s pervasive. I’m sorry it’s pervasive. Edit 1 The value of your software is the value that is produced by people using it. “Is it the purity/beauty of the code? To me, value is in simplicity and readability.” It’s neither. It’s the value created applying the code to real-world problems. If the code is hard to maintain, adapt or use, that devalues it. If the code is easy to maintain, adapt or use, then there are fewer barriers to getting
