Too many tools and frameworks!

💖 Support the show by becoming a Patreon https://www.patreon.com/funfunfunction We discuss the frustration that a lot of developers feel around the massive amounts of tools and frameworks that are available, and how to deal with it. Basically, my stance is that there is no such thing as a best tool in general (think Leatherman vs a Power Screwdriver) so you have to know what needs your app specifically will have in order to pick the right set of tools. The problem is that you won't know what you're building until you've actually built it (Instagram was first called Burbn, and was a completely different service) so you need to build a prototype/MVP/thingee first - and to use that you should just use whatever the heck you know already. This is because you're picking tools in the dark anyway, there is a 99% chance the tools you're picking are going to be wrong, so you might as well pick the one that you know really well. After you have your prototype, you should analyze it in order to find out what your needs are, and then take those needs with you when you wade through the vast amount of tools available, which will allow you to find the ones that are best for your app, and it's going to be a set of tools, not a single god-Leatherman. Blog entry by Adam Morse that I refer to in the video: http://xn--h4hg.ws/2015/07/27/too-many-tools/ You might want to read this article I wrote: http://www.quora.com/Why-did-Twitter-switch-to-a-Java-based-front-end-after-successfully-using-Rails-with-200-million-users/answer/Mattias-Petter-Johansson?share=1 💛 Follow on Twitch and support by becoming a Subscriber We record the show live Mondays 7 AM PT https://twitch.tv/funfunfunction 💛 Fun Fun Forum Private discussion forum with other viewers in between shows. https://www.funfunforum.com. Available to patron members, become one at https://www.patreon.com/funfunfunction 💛 mpj on Twitter https://twitter.com/mpjme 💛 CircleCI (Show sponsor) Robust and sleek Docker-based Con