I've spent the last couple of months working on an API written using Python, Django, and Django REST Framework (DRF). The latter is a popular, well-established framework for building APIs in Python, so I assumed it would have decent documentation surrounding relational fields, which is a fairly common situation in any model-view-controller (MVC) framework. It turns out that was a faulty assumption.
If you're wondering whether this blog post is really for you, ask yourself a few questions. Is my core codebase written in a language, framework, or tech stack that is 10 or more years old? Have we been struggling to hire Junior devs, seen a slide in motivation among our in-house folks, or even lost some engineers?
Most of us love a good personality assessment. They’re usually fun, can help us understand ourselves better and, at times, may even have implementable tips for us. But, there are unspoken pitfalls that we need to watch out for.