[cristianMD7]

I completely agree with you on the importance of developers being able to read and understand others' code and documentation. It's an essential part of their job. However, the focus of my newsletter is a bit different. It caters to a specific audience: managers and directors, who may not need to learn programming but need to at least understand what a server is for example.

[smarkov]

What's the intended way it's supposed to be used? Are the managers and directors supposed to subscribe to it or the developers? If it's the developers, when they need to explain a concept do they just copy-paste the explanations? Forward an email? Send some kind of a link? It seems like an awkward interaction to me.

As a developer, it's always been my job to explain things to non-technical people in as few words as possible during conversations. I'm not sure how a newsletter would fit in that use case.

[cristianMD7]

This is mainly for managers and directors to get in on the action of understanding tech terms. My theory is that if I send them nicely formatted emails that are short enough to keep them interested, but packed with enough info to quickly grasp the basics of a tech term, they'll be able to understand it when they come across it again.

This isn't an instant explanation hotline for tech terms they encounter right now (for that you have Google and GPT), but more like a learning resource to get better at understanding tech jargon.