«
»

The simple is good

25th July 2008, 07:04 am

Sometimes we make things to fail due to our ability to complicate what we do. I’ve seen this happening many times. But I have a simple rule for this : If something is becoming too complicated to accomplish, then stop and try to think on a different way, because probably we’re trying to do something unecessary in the middle of the process. The best solution is always the simplest one.

Category: Uncategorized  |  Comment (RSS)  |  Trackback

4 Comments

  1. Carolina Mourao:

    Simple is beautiful, is clear and impressive!
    People would just be shocked by a simple solution and a simple logic.
    Love it!

    4 August 2008, 3:11 pm

  2. admin:

    Yeah… unfortunately people are not willing to have simple solutions. It seems that everybody is trying to build something humongous without even need it. Well, as I’ve said before, I usually use that rule : if something is becoming harder and harder, then it’s probably my way of thinking about the problem.

    4 August 2008, 3:24 pm

  3. Carolina Mourao:

    What do you suggest when you get into a hard solution? Re-think? Ask your buddy? Share with the development community? How can we measure that a solution is getting complicated? Time? Daily headaches?

    5 August 2008, 11:43 am

  4. admin:

    Re-think, refactoring, ask someone’s else opinion, look for something similar on a book, over the internet…. The good thing is that : more you know ( reading books, after years of experience ), easier will be to identify these things. I’m not saying that there is no complicated business logic in the Enterprise Software Development world, but there are many ways of doing the same thing.

    For example, if you are struggling to retrieve an information from your system, because it’s difficult to pick up some data and so on… So, there is a good possibility that your domain model was bad designed, or you didn’t build any mechanism to help you to do so ( a service layer, an integration layer, and so on…) Or if your system is hard to maintain, it’s a smell that there is a lot of code duplication it’s not modularized, and the responsibilities are not well distributed among your domain classes.

    5 August 2008, 12:21 pm

Leave a comment