{"id":322,"date":"2015-08-05T12:32:50","date_gmt":"2015-08-05T12:32:50","guid":{"rendered":"http:\/\/www.scrummable.com\/?p=322"},"modified":"2017-06-06T13:05:34","modified_gmt":"2017-06-06T12:05:34","slug":"mnmlsm-simplify-simplify-some-more-then-start-simplifying","status":"publish","type":"post","link":"http:\/\/scrummable.com\/mnmlsm-simplify-simplify-some-more-then-start-simplifying\/","title":{"rendered":"MNMLSM: Simplify, simplify some more, then start simplifying"},"content":{"rendered":"
Minimalism is an interesting thing – far from meaning as stark as possible, minimalism is the idea of removing anything unnecessary for base level functionality. Imagine a human face. Now remove all of the details you can until it still resembles a human face. If, for example, you took the eyes out and it looks wrong, stick them back in. Once you’ve finished you have minimalism. Buildings<\/a>, paintings<\/a>, web design<\/a> can all implement (and benefit from) minimalism. So can code.<\/div>\n When I started coding for a living I had no idea about loops. The last year of solidly building WordPress sites has taught me a lot. I still start my code the same way I used to code though. I write everything out longhand, then work out the commonalities and parse them as variables, arrays, and loops. Then I start cutting out the duplicated code. Once I have this, I can start working out what I can cut from where to make my code as small and as simple as possible.<\/p>\n Every single developer! The reuse of code improves performance, makes updating easier – especially if the project gets passed to someone else when you’re inevitably hit by that bus that everyone goes on about, and benefits\u00a0consistency across the design.<\/p>\n “Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.”<\/p>\n<\/blockquote>\n Everyone knows that deadlines get in the way of perfection and sometimes it’s necessary to chuck something in that works rather than delay everything to produce code that will make other developers moist. This is where Technical Debt comes in. Set aside some time after deployment to tidy up your code. Think of it like throwing all of the stuff from your floor into a wardrobe when your mum visits. Your flat will pass muster for the duration of her visit but, if you don’t go and sort that wardrobe out once she’s gone, you’ll be in for a world of pain later on!<\/p>\nWho wants a DRY KISS*?<\/h3>\n
\n