wouldn't say it's a miss, I thoroughly enjoyed the article :) There is a warranted high emphasis during technical discussions in setting up frameworks / archit

wouldn't say it's a miss, I thoroughly enjoyed the article :) There is a warranted high emphasis during technical discussions in setting up frameworks / architecture for the objective measureable metrics, but not enough for the developer experience. Though it seems subjective, I do think developer experience has a direct correlation to employee retention and velocity. When I was at Meta, the dev ux there has to be one of the best i've experienced in the industry, it almost nails every point laid out in the article, errr except documentation, but with the consistency of tech used in the monorepo, you can figure things out really. As an IC, you do feel empowered to just build and create, the architecture supports such behavior and guard you from making dumb mistakes, guards such as static typing, code reviews, automated tests, etc. I stayed longer than I should because not only it was fun to build in that environment but with great dev ux, you will also have a higher baseline expectations of other engineer's work in terms of building tooling for other devs, self feeding loop, you'd learn to design your product in with dev ux in mind.