One thing that struck me was that a lot of the same things were done in different ways. Each solution trying to be more clever and in fewer lines of code than the previous solution.
Personally, I believe that everyone should write boring code. Boring code is great as it is easy to write, change, and delete.
For the last year, I worked mostly in Go, and Go is great for writing boring code!
Most of the time there is only 1 way to do a certain thing. So, everyone is forced to write the same code. Which is great to help people understand each other’s code. …
Cloud Run is very similar to Google’s App Engine and Cloud Functions. The main difference is that with Cloud Run, you can create custom Docker images.
This means you have way more control over how your application should be built and you can go crazy with complicated custom Docker builds. The downside is that it’s a bit harder to set up compared to Google’s App Engine.
In this article, I’ll show you how to set up a custom Docker image on Cloud Run.
The first thing we need to do is create a new Google Cloud project. …
I recently had a Cypress test that was very flaky. Sometimes it would pass and sometimes it would fail.
One day, after three failed deployment pipelines thanks to this test, I decided to improve it once and for all.
The Cypress error I was getting didn’t tell me a lot. The
#results DOM element wasn’t found, but this could have been due to many things.
When I opened the test, it looked something like this:
Can you spot the problem?
Spoiler — the issue is on line four:
The search bar performs an API call to the server. However, in our CI environment, this API call was very slow. This would result in Cypress searching for the “Hand Sanitizer Pro” product while the API was still loading. …