The way Monet designs software

I have been to art gallery, recently. The topic of my last visit was great impressionist of XIX century. I was standing in front of Monet's "Japanese footbridge" and seeing how that picture transports me into an actual moment that existed in the past. The artist and me (the sitter) encountered each other in a real time and place.

Imagine you are in the place when the portrait was being painted. What was happening in the place? Imagine the conversation between artist and the sitter. Conjure up the smells and the background noises. 

Step back in the time and ask yourself a question. Is your code base screaming out a design, a business need your code is fulfilling or it is just an awkward technical mumbling? If code base you are working with reflects model, view, controller, utilities etc. parts as separate packages or entities, the only thing it does, is wrapping business needs into technical bits. This is wrong! The driving factor for organizing code base should be business need. Only then, your code, which is a design, will be screaming business use cases to all of us.