Usually when people write tech blogs, the blog functions a bit like an online portfolio. Technologies/code snippets contained within the posts serve as evidence of the authors’ expertise in the eyes of potential employers/vendors/clients.
If we follow this train of thought then the posts, by their nature, might have to be quite moderated and uncontrovesial for fear of alienating the audience. An unfortunate side effect of this moderation could be that useful (and honest) opinions about certain technologies or trends could be self-censored by the authors. ☠️
wlog.blog was started with the intention of being an outlet for collecting my own thoughts from working as a data engineer; thoughts which I hope could prove useful to the readers. To keep these thoughts unbiased and uncensored, I aim to remain anonymous.
Posts that I personally write will be attributed to
@the.editor.
safe space for others to share thoughts as well
wlog.blog could theoretically also be used by others in the industry to share opinions freely; whether anonymously or not. After all, not all opinions are controversial and warrant anonymity.
In the interest of open-ness, I should explain the “architecture” of the site slightly:
infrastructurelives in its ownprivaterepopostslive in this ❤️ public repo under a newwlogblogGitHub account whichinfra repopulls in as agit submodule
PRs merged in the posts repo will automatically be pulled in by infra repo’s dependabot for deployment.
how?
If you are interested in getting a post published here, here’s a detailed contributing guide; hopefully as a fellow data engineer, you are already well familiar with PullRequests.
- if you want to remain anonymous, use
@an.engineeras theauthorattribute and PR from an anonymous or throwaway GitHub account.- if you want to publish publically, PR from your own GitHub account and
- use your GitHub
@handle as theauthorattribute.- use
author_external_urlattribute to link to your profile (GitHub or otherwise)
Hope to see you on GitHub!