Actually, if you looked at the code closely you'd probably find it littered with so-called “anti-patterns!” But here's the deal: the same goes for your code. And who wrote that code? Were they beginners, hobbyists, seniors? Perhaps you've seen code from all those people-chances are, they were all complex monsters. Think about it for a second-how much code have you seen that was easy to read, that was simple enough to understand? Probably not a lot. Good programmers write code that humans can understand. In fact, let me present you this quote by Martin Fowler:Īny fool can write code that a computer can understand. It requires knowledge of the code, the framework, and the language you're working with. It requires knowledge of the domain you're working on. Keeping things simple is, ironically, not simple! It requires abstract thinking. Duh, why would you write complex code? Maybe you even think of yourself as not being a good enough programmer to write complex code! Let me tell you why this is probably not the case. And now you're probably thinking you're already doing that.
Simple code is less prone to bugs, and is easier to read and understand for you and the people who'll be working on the code in the future (including yourself).
So what should I tell you about KISS? It really just means you have to keep it simple. No matter what your style of coding is, it should follow one rule: Keep It Simple, Stupid! Is it DRY-Don't Repeat Yourself? Or are you more a YAGNI-You Aren't Gonna Need It-person? Do you follow SOLID principles? Or are you really sick and tired of all these abbreviations we have in IT, and just use common sense instead?
#Keep it simple stupid the office software#
Let's talk about KISS, or “Keep It Simple, Stupid” as a principle for effective Software Engineering.īut before I go any further, just think a little about your favorite best practice when writing code.
0 kommentar(er)
