There is a common trap that we fall into as developers, and it is believing that because some code “worked” that the code was written “correctly”.
In this world, nothing can be said to be certain, except death, taxes, and migrations. Earlier in my career, I would come to a new project and inevitably a hectic migration would be underway.
A universally unique identifier (UUID) is a 128-bit format for creating IDs in code that has become popular in recent years, especially in relation to database keys.
“Dead Poet’s Society” is a classic film, and has become a recent favorite of mine. There’s a scene in particular that I enjoy, where Robin William’s character explains that it’s bad practice to use terms like “very tired” or “very sad”, instead we should use descriptive words like “exhausted” or “morose”!
I recently had a ticket opened on my team’s backlog board requesting the ability to bypass our API’s caching system.
Too often I neglect the idea of UX design in backend work. The goal of user experience design is to give users a product that’s easy to use.
I’ve noticed that bugs introduced into an existing code base are often due to poor variable naming more than one might suspect.
Functional programming is a way to writing code where programs are created strictly through functions. Functional programming has gained quite a bit of traction in recent years among the development community, mostly because of the benefits it provides.
Clean code is like clean garbage - it’s only clean if it doesn’t exist. In other words, the only clean code is no code .
Unit tests are incredibly important to us as developers because they allow us to demonstrate the correctness of the code we’ve written.