Hype Driven Development
bad examples.<p>I don&#x27;t think microservices, react, functional programming or no sql are examples of &#x27;hype&#x27;; I think those are good engineering decisions (depending on the problem domain).<p>I also <i>completely</i> disagree that hackathons are good places to try out new technologies to see what&#x27;s good for good engineering decisions; hackathons let you dip your fingers in the water and see the shiny cool bits and pieces without having to suffer through any of the long term maintenance or scale issues with the technologies. If you&#x27;re looking for a bad decision, picking something to run with that &#x27;seems pretty good&#x27; after a 2 day hackathon &lt;--- that&#x27;s your bad decision right there.<p>I mean, I get what the article is saying, yeah yeah, avoid the hype, don&#x27;t drink the &#x27;webscale&#x27; cool-aid...<p>...but hey, the internet is full of really talented smart people who do excellent engineering work.<p>You&#x27;d be stupid to not look at what the best and most successful companies <i>in the world</i> are doing with their engineering teams and take note of it.<p>Even if it means picking up new technology: that&#x27;s not bowing to the hype; it&#x27;s being pragmatic.<p>Still, it&#x27;s super easy to cherry pick some things and go, oh hey, this is a bad idea. Much more interesting would be some examples of <i>good</i> engineering choices.