code_monk
code_monk
Jul 21, 2017 · 1 min read

I think it originates from something more primal. learning about big problems with big solutions can be intoxicating (Dynamo, MapReduce, etc), and when we are intoxicated we loose our ability to think critically.

The opposite problem happens too. Engineers choose the shiny new framework that seeks to abstract away all your complexity at the cost of performance. It will create a REST API for you. It will configure your back-end for you and write schemas for you. All you have to do is write high-level models, and then chase bugs into eternity.

It’s especially bad when they combine both types of antipatterns into Frankenstein stacks that are both resource hogs, hopelessly slow, and destined to be abandoned by their maintainers when they get bored.

)

    code_monk

    Written by

    code_monk

    internet geenius