This argument seems to assume that developers work on open-source software. I'd wager that most developers work on closed-source software and so can't blog about it publicly.
This argument also seems to assume that all developers are good writers. Based on many blog posts on this site, they're not; or the writing itself is OK, but the formatting is terrible and becomes too much of a distraction.
Lastly, not all developers want to blog. It's often difficult just to get many developers to write comments and documentation!
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.
educating about proxies - a technology enabling public data collection in large volumes, providing businesses with valuable insights into markets and their competitors
Software engineering engineer at a national public broadcaster. Best practices / developer experience / agile / diversity and inclusion / psychological safety
Writing good blogs takes a lot of time, which is fine if you like writing and are fairly good at it. Blogging can also be a good idea if you want to improve your writing skills. But you shouldn’t blog only because you feel you have to; bad blogs can even harm your chances of getting hired!
Fortunately, there are plenty of other things besides writing that one can do to “build a brand” (which in my experience isn’t actually that important).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This argument seems to assume that developers work on open-source software. I'd wager that most developers work on closed-source software and so can't blog about it publicly.
This argument also seems to assume that all developers are good writers. Based on many blog posts on this site, they're not; or the writing itself is OK, but the formatting is terrible and becomes too much of a distraction.
Lastly, not all developers want to blog. It's often difficult just to get many developers to write comments and documentation!
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! 👏
Thanks for bringing this up, exactly what I had in mind (about NDA and stuff).
Yeah, not everyone should blog.
Writing good blogs takes a lot of time, which is fine if you like writing and are fairly good at it. Blogging can also be a good idea if you want to improve your writing skills. But you shouldn’t blog only because you feel you have to; bad blogs can even harm your chances of getting hired!
Fortunately, there are plenty of other things besides writing that one can do to “build a brand” (which in my experience isn’t actually that important).