- web boss crossed 500 subscribers on YouTube
- Published seven articles on Medium
- Crossed 100 followers on Medium
- Published my third npm package and used it to solve a problem at work
- Worked with GitHub actions for the first time to setup auto-publish to npm for “4”
- Had my first partying/clubbing experience
- Started going to church a little early
- Changed church (WIP)
- Worked with friends to release the shortest course on frontend development
- Finally learnt to mind my business/Stopped giving a damn generally
- Still figuring out this work-life-balance thing
- Someone who was owing me money for close to two years finally paid back
- Worked with the team at FourthCanvas to document and handoff a codebase to a major client
- Had a viral tweet
- My team finally started doing shorter standups
- Came back on WhatsApp.
No hashtags, I made an innocent tweet and it blew up 🔥

I expected my followers to increase but it didn’t move one bit — I wish I could swear but then it clicked! these people liked the tweet not me; they don’t know who I am and do not give a damn about me — they shouldn’t.
So, what did I do? I started following the people who liked the post and they started following back. By now showing interest in the people who already liked something I put out, they now showed interest in me.
Of course, not everybody followed but I got at least a 100 followers in 24hours. Argue with my twitter analytics dashboard.

I will assume you already know what GitHub Actions and environment variables are, and you only need a quick guide to know where to put your environment variable for a GitHub action so I will get straight to it.
- On the repo, you want to create an environment variable, click on the “Settings” tab.
- On the sidebar, scroll down and look for “Secrets” (yeah you guessed right, GitHub calls environment variables secrets) then click on “Actions”
- Click on “New repository secret”. Enter the name of your secret(environment variable) and paste the value. Click “Add Secret” and you are done!