Caution!

This is an old post. Information here may be out-dated, or the post may re­flect opin­ions or be­liefs I no longer share.

If you look through my blog his­tory, you will no­tice I don’t have as many posts as I could have had, con­sid­er­ing I made my first post in 2015.

I would like to share why I feel mo­ti­vated to write and share more, per­haps now more than ever be­fore.

A pub­lic jour­nal of knowl­edge

I have been free­lanc­ing for a while. I be­lieve I have gained a tremen­dous amount of knowl­edge through my pro­fes­sional as­sign­ments, side pro­jects, and con­ver­sta­tions with my peers.

Yet, I of­ten have no way of re­vis­it­ing what I learned. It cer­tainly has made me re­al­ize that there’s value in blog­ging. It can be a ref­er­ence not just for your­self, but other de­vel­op­ers as well.

At the same time, I will ac­knowl­edge that it is not al­ways pos­si­ble to pub­lish reg­u­larly. Project dead­lines can be tricky, or we may just have too much go­ing on in our lives to be able to churn out ma­te­r­ial we see fit for pub­lish­ing.

Verifiablity of skills & knowl­edge

Prospective em­ploy­ers usu­ally have a few ways of ver­i­fy­ing that you are, in fact, as good as you say you are.

The tools they re­sort to are ref­er­ences from your past em­ploy­ers or cur­rent em­ploy­ees (outside of your di­rect con­trol), in­ter­views (which de­vel­op­ers are of­ten not fond of), and your pub­licly avail­able pro­jects on a git repos­i­tory like GitHub or GitLab (which you may not al­ways have or may fea­ture play­ground code; noth­ing that works against you, but prob­a­bly not the ideal re­flec­tion of your skill.)

Keeping a tech­ni­cal blog is a sure way to show em­ploy­ers you un­der­stand some­thing well enough to be able to write about it. In fact, writ­ing about any in­ter­est­ing or orig­i­nal work helps you stand out! I also be­lieve it shows you care about the com­mu­nity enough to give back.

Participating in an open web

I have re­cently im­ple­mented IndieWeb on my site. You can see I pub­lish notes as well now, which au­to­mat­i­cally syn­di­cate to Fosstodon and Twitter.

The replies I re­ceive on my blog posts and notes to­wards the bot­tom of the page come from Fosstodon, Twitter, as well as other web­sites par­tic­i­pat­ing in this move­ment. This is an open stan­dard called webmention, and the spec­i­fi­ca­tion is avail­able for you to read on W3.

While IndieWeb is not yet fully or per­fectly in­te­grated to my site, I see a lot of value in the ideas of the move­ment. When other peo­ple, or de­vel­op­ers, share their opin­ion on your ar­ti­cles or notes, it be­comes a so­cial proof of the value of your con­tent in the com­mu­nity.

If you’d like to par­tic­i­pate, I found this to be a very help­ful start­ing point.

My ex­pla­na­tion might help some­one reach their aha” mo­ment

While it is true most top­ics and con­cepts have been ex­plained to no end, I be­lieve there is still value in what one has to say.

One’s world view is unique to them. The way they un­der­stand some­thing and ex­plain it is unique.

Sharing one’s take on a con­cept might just be what a stranger on the in­ter­net was look­ing for to make sense of things.

Final word

I am wary of the fact that not only do opin­ions change, but even tech­ni­cal or fac­tual con­tent can be­come out-of-date. Inspired by Kev’s blog post, I too have im­ple­mented a sim­i­lar no­tice on my older posts. As I al­ready have a draft no­tice dis­played on blog posts tagged #draft, much of the foun­da­tional work was al­ready avail­able for me to build on.

All things con­sid­ered, I be­lieve this is a step in the right di­rec­tion, and with the in­clu­sion of IndieWeb and a no­tice on posts as they age, I am very ex­cited for the fu­ture of my blog.