I believe that writing or blogging about programming will show and prove if you really understand the topic your are talking about and is able explain it in simple terms that others would understand too.
I agree with this (but I also have a bias toward writing as a creative outlet ). I don’t think it needs to be a blog or anything public, though. Just working on day-to-day code reviews, emails, and documentation is a great way to level up writing skills.
One suggestion I would make is: Be objective about your own work. Step away for a while after you’ve written something. When you come back, re-read it with fresh eyes; put yourself in the shoes of your readers who don’t have the same mental context or lived experiences as you. Here are a few questions you can ask yourself to prompt that kind of empathy:
Is your audience just as (non)technical as you?
Have you made any assumptions about shared knowledge?
Are you using unfamiliar/arcane/esoteric terms or acronyms?
Practice is always best. After I started with Elixir I needed just 3 months to get highest trust level on Elixir forum and … my first Elixir job!
It was absolutely brilliant time … no fear for viruses, no fear for wars, even EU was not that bad …
Anyway, there is no rule which covers all cases. There is no “one right way” to do something. If it would be then we would not need AI to work for us as instead simplest algorithms could do everything.
I still wish that some algorithms (ehem … Google/YouTube) would finally use huge amounts of data they collect in a way they declare. Since my IP is from Romania I’m still getting almost always content in Romanian from which I don’t understand much.
I definitely do not recommend focusing on just one thing, but being active in community is always a big