That new thing everyone is raving about? It's not so hot after all...

vorahsa profile image Jaakko Kangasharju ・1 min read

I'm sure you've heard of that new <best practice>? Everyone has been writing about it, saying how it's the best thing ever and you should immediately adopt it to remain relevant. Well, I've looked into it and I don't think it's that good. You probably shouldn't use it. Sure, sometimes it can be good but not always, so don't jump on the hype train without thinking.

So how can you tell when to use <best practice>? Turns out, it's quite simple. Look at your situation. Does <best practice> make sense in your situation? If it does, use it. If it doesn't, don't use it. It's that simple! Now that you have an easy way to make that decision, hopefully the hype dies down and we can adopt the good parts of <best practice>.

Posted on by:

vorahsa profile

Jaakko Kangasharju


I'm a generalist developer, preferring to have some skills in a variety of areas to being really good at only a few. I need to see how a technology solves real problems to really understand it.


Editor guide