Sure it's possible, but harder. Anything you write for public consumption that involves anything from your job should be run by your legal department to clear it first. Disclosing anything that could be considered proprietary is a fireable offense. (I know people this has happened to.)
This works only if readers take the time to critique the writing. Otherwise you could muddle along writing poorly thinking you're doing great for years.
It is very possible to blog about concepts you learn at work without sharing your "not for public" closed-source software.
A good way way become better at writing is by practice. Improving communications skills through writing will help in a developer's career.
Fair enough. Sometimes I don't want to code but oh well, it pays the bills.
Very well said Paul! 👏