Hello friends, it's been a while since I published anything on this blog, it's been so long since I last posted anything that it is a little embarrassing. I have gone off the grid because I was just a little occupied from a few personal projects in the past few months. With that said, the Xmas break was a perfect time to recharge my batteries.

I recently started working on some side hustle projects. To keep things organised, I created a new git account with a different email. When I tried to push to the git repository within the new git account, I got the following error.

Roam is still in active development right now, which means some common features in other note-taking app is not quite as easy to use here. One of these features is the ability to share a single page of note with friends or family. In this blog post, I'll show you how to do this properly.

I use Google Calendar, both personally and professionally. I have a shared calendar with a friend to keep track of different events and activities. I have always found it hard to navigate Google Calendar in the browser, I love the look and feel of the web app, though I find myself always looking for the right buttons, etc. I knew about the brilliant shortcuts that made Gmail fun to use and decided to see if Google Calendar offered something similar. Luckily, they do, and they are straightforward to remember.

With all the new toys coming out each day, libraries, frameworks and even architectures. Have we forgotten the fundamentals of software development? Every developer wants to write good code, but how often do we do what we say? Maybe, every so often we all need to take a step back and rethink our approaches to software development. If nothing else, we should find challenges and excitement in what we do, if only to make sure the passion that drove us to this career path doesn't die out.

TypeScript 4.0 just came out, and people probably want to be upgrading to it soon. Here's a quick summary of what's new based on official release notes. This is only meant to be a quick summary, so I have left out edge cases and detailed examples. If you have time, I'd recommended giving the official release note a proper read. But for those who want to get a high-level gist of what changed, this might be useful.

Gatsby is great for generating static sites, but sometimes we need to run some client-side only JavaScript as well. The question is how might we go about that? Well, that's what I'll be covering in this blog post. Actually, I've already written about something similar in a recent post Render client-side only component in Next.js. The approach is very similar, but I'll be walking through an example in this blog that is more specific to Gatsby.

This is the last part of this blog series on Cypress errors. There were some additional notes I made which didn't go into the previous posts. This blog post is less specific and more about general advice and some obscure errors I saw along the way.

Apart from the Cypress chromium crashes I explained in Part 1 of this blog series, I also experienced some assertion timeout errors due to element cannot be found. In this part, we will talk about ways you could fix it.

After recently working on an existing project that adopted Cypress, I was both amazed at how pleasant the local developer experience was and how badly it runs on the CI pipeline. No joke, at one point I actually missed Selenium. To debug the issue, I must have run the pipeline over 100 if not 200 times and read many many Github issue threads. Finally, I was able to problem resolved and noted down a few things along the way which may help someone else in the same shoes. I am pretty confident these solutions will fix your problems, if not leave an angry comment and let me know that I failed 😂