3 ms·

I have started writing blog posts on things I have gained technical expertise in. I have no audience so really I write for the hell of it, but I do announce it

I have started writing blog posts on things I have gained technical expertise in. I have no audience so really I write for the hell of it, but I do announce it on my LinkedIn feed (but I have less than 100 connections). There's also the fear that putting words in public opens me to criticism, if someone can think of a better way of doing things, if my mental (or worse, technical!) model is wrong. Someone may take it too far and it leaks onto my personal life. In reality I see far worse practices than mine at work every day, so I hope if someone stumbles onto my blog that they get value out of whatever they read. It's also published with hugo on GitHub pages, absolutely no ads, and I'm not selling anything - for me, the blog really is about giving back. Lastly, time. Today I knocked out a blog post on a light topic in about an hour. No revisions, just finished writing it and hit publish. I thought of the topic over the weekend and today was just put a few short examples and write about them. I'm not positive that I was detailed enough, or my explanations are good enough, etc. So time is another big factor, unless you're willing to risk publishing mistakes due to lack of polish

tudelo 8y ago
I once read the quickest way to get a legitimate answer to your question on stack overflow was to post a bad answer. I think there is something similar to say about a blog post with bad information :) If you are wrong, at least there is a chance someone will point it out.
type0 8y ago
> I have started writing blog posts on things I have gained technical expertise in. I have no audience so really I write for the hell of it I think it's good to write down the things you've learned, even if no one reads it, text becomes a valuable exercise and then you will have it much easier to explain for someone what you mean. Not only will you be able to put your coworkers at the same level of understanding of the subject: your team becomes much faster at implementing consensus based decisions.
kennxfl 8y ago
Do you mind sharing your blog?
- staz 8y ago
  HN users can leave a text description on their profile, which you can access by clicking on their username. Usually they put links or contact info in it
- hluska 8y ago
  Staz was leading you in the right direction, only in a rather cryptic way. According to the parent's profile, his/her blog is located at: https://charmeleon.github.io https://charmeleon.github.io He or she is a good writer. Enjoy!

tudelo 8y ago

I once read the quickest way to get a legitimate answer to your question on stack overflow was to post a bad answer. I think there is something similar to say about a blog post with bad information :) If you are wrong, at least there is a chance someone will point it out.

type0 8y ago

> I have started writing blog posts on things I have gained technical expertise in. I have no audience so really I write for the hell of it I think it's good to write down the things you've learned, even if no one reads it, text becomes a valuable exercise and then you will have it much easier to explain for someone what you mean. Not only will you be able to put your coworkers at the same level of understanding of the subject: your team becomes much faster at implementing consensus based decisions.

kennxfl 8y ago

Do you mind sharing your blog?

staz 8y ago
HN users can leave a text description on their profile, which you can access by clicking on their username. Usually they put links or contact info in it
hluska 8y ago
Staz was leading you in the right direction, only in a rather cryptic way. According to the parent's profile, his/her blog is located at: https://charmeleon.github.io https://charmeleon.github.io He or she is a good writer. Enjoy!