That's the point, the policy is to retain the original title, no matter how nonsensical. And here the original title was perfectly correct and concise.
That being said it's incredibly hard to follow this advice in environments which encourage a polyglot stack and 'the best tool for the job' mindset. The moment you have more than one language in your stack it becomes easier to build services than to maintain libraries in each language. You can of course write native C libraries with bindings to different languages but that's a bit weird.
It's also requires more discipline to maintain abstractions and boundaries properly with libraries in large code bases but that's another story.
Hey, author here and I completely agree. One of the things that I meant to express in the article but couldn't was when as someone approaches a problem with an understanding of the context (business, people etc) they will be more likely to understand what's important, what's not and when good is good enough.
As a side note, I shared this article with Jessica as a draft and she shared it with her followers before I could add a few more things. Still my most successful post yet and comments such as these make me understand there is a lot of material for new blog posts.
Bought at least one book clicking through from this post, so thanks! It's a tough area, and something I'm stressing about a lot as I try and build as many career paths as possible for engineers at my current company.
I really enjoyed reading this article. One key takeaway for me was how its in the interest of companies like Substack to initially have a lot of high profile creators defect from their motherships (like a lot of journalists have recently done) and then eventually decrease reliance on the superstars so that Substack's value doesnt immediately decrease once these superstars leave.
