{"id":87,"date":"2016-07-19T12:33:30","date_gmt":"2016-07-19T12:33:30","guid":{"rendered":"http:\/\/dracony.org\/?p=87"},"modified":"2016-07-19T12:33:59","modified_gmt":"2016-07-19T12:33:59","slug":"should-you-reinvent-the-wheel","status":"publish","type":"post","link":"https:\/\/dracony.org\/should-you-reinvent-the-wheel\/","title":{"rendered":"Should you reinvent the wheel? Programming and cakes"},"content":{"rendered":"
The “Not invented here” mindset and it’s counterpart “Don’t reinvent the wheel” mindsets are probably causing thousands of discussions every day. Almost every week you see a question pop up in programming subreddits where people ask whether they should use a framework or a library for something or roll out their own solution.<\/p>\n
To me the answer has always been rather obvious and easily explainable with a simple analogy. What if instead of programming you would be cooking a birthday cake. How would you approach it? Your options are pretty much the same:<\/p>\n
If I told you that I’m going to improvise a cake without any prior experience and use expensive ingredients for it, you’d say I was bound to fail and waste a lot of money in the process. Can you see the analogy now? This is what I hear when a person with no substantial experience says they rolled out their own framework, router, ORM etc.<\/p>\n
On the other hand ready made recipes only get you so far. Their very nature of catering to the majority of people makes them lean towards being simple and easy. You won’t just google a recipe for this cake (yes it is cake and is completely edible):<\/p>\n