Why Simplicity is better than Complication

Ever hear a geek brag about how his or her website uses ten services or more just for the main site to load?

Well, even though this a geek(a.k.a. Know it alls…) bragging, they aren’t always right… Especially in the case of using multiple services and having very complex unneeded code…

What does being Simplistic mean?

Let me start off by defining my definition of Simple(I got it from Dictionary.com :)), to be simple is “easy to understand, deal with, use, etc.”. With this being said, I would say some examples of simple things would include everyday items such as; Pencils, Erasers, Gravity, etc… Now let me ask you this, would you rather have to write an essay on Gravity or write an essay on Molecular Dispersion?  You would always choose the easier option, probably because you know more on the topic, right??? Of course you would, that was just a very basic and plain text example…

Why simple is better than complicated

“Progress is man’s ability to complicate simplicity” –> Thor Heyerdahl

Now that we all know the meaning of simple things such as objects, it is time to identify the definition of complicated. To be complicated means to be “composed of elaborately interconnected parts; complex” (From Dictionary.com).  For example; who in the world would want to have a complicated LAN(Local Area Network) over a simple more reliable one??? More Reliable? Yes you read that right, a simple network is almost always more reliable than a complicated one because less things can go wrong thus, less problems.



A real life example: consider a mom that drives a Honda minivan opposed a mom that drives an 8 wheeler Mercedes with 500,000 different gadgets inside and outside the car… The mom that drives the minivan is making a better choice about a simple Honda minivan rather than a Mercedes because, for one; Honda’s are cheaper, Honda’s are very reliable, and Honda’s are much much cheaper to fix. As you can see from the listed out items above, a Honda minivan is definitely a better choice because it is more simplistic meaning that less things can go wrong with it and that it wont be as expensive to fix. This is probably because that less things can go wrong and Honda’s are more widely available and driven.

With that out of the way, it is time to list the advantages and disadvantages of being or having simplistic objects and theories…

Advantages

  • Easy to understand
  • More trust worthly
  • More reliant
  • Usually cheaper

Disadvantages

  • May not get the point across

Conclusion

As you can see in the above the list, the advantages undeniably outweigh the disadvantages 4:1. To summarize, simplicity is better than complication because a simple item is more reliable, trustworthy, and overall cheaper than a complicated item that is less reliable, less trustworthy, and more expensive…

I hope you enjoyed this post and as always feel free to leave a comment below and or to share this post via the share buttons!!! Have a great day! 🙂

6 Comments

  1. Ajer Boogel says:

    Wow, I was literally just searching for this post!!! Thanks and cheers mate!!!

  2. NerdOfLinux says:

    “Now let me ask you this, would you rather have to write an essay on Gravity or write an essay on Molecular Dispersion?”

    Answer: Molecular Dispersion because there’s more to write about 🙂

    1. NerdOfCode says:

      That is debatable, anyways I actually know that you know nothing of this topic so I would actually say I’m fairly certain you would choose the other… But you do make a good point that I didn’t cover…

      1. NerdOfLinux says:

        I know that you know that I don’t know anything about Molecular dispersion 🙂

        Please respond with:

        I know that you know that I know that you don’t know…

  3. NerdOfLinux says:

    How complex it is to load your site:

    Request to DNS -> Send RSA key to CloudFlare -> Get RSA key -> Share Keys -> Send RSA key to your server -> Server sends RSA key to CloudFlare -> Request gets sent to CloudFlare -> CloudFlare decrypts request -> CloudFlare send request to server -> server decrypts -> Server processes -> Server encrypts -> CloudFlare decrypts -> CloudFlare re-encrypts with your RSA key -> Your computer gets the data -> Your computer decrypts the data -> The browser process HTML, CSS, JS, etc.

    1. NerdOfCode says:

      You forgot a few steps in there… Such as Cloudflare reducing or “minifying” the HTML, JS, and CSS. And various other Cloudflare features… I believe you also forgot to mention PHP processing…

Leave a Reply

Your email address will not be published. Required fields are marked *

*

*

*