It's 2025, and JIRA is still clunky
I’ve been dragged back into Jira after five years of bliss with Linear, and it’s rough.
I’ve been dragged back into Jira after five years of bliss with Linear, and it’s rough.
I often see developers merging main into their feature branches and opening pull requests (PRs) that include commits from other branches. This practice leads to “git spaghetti,” which has several consequences:
Jamie AI is a project I embarked on to build a human-like virtual assistant that I could CC on emails to take care of my admin. I originally intended very much to open source this, but I’ve decided to make it into a product.
This is a simple example of a TypeScript React function that can assist in combining many Provider components, such as those used by React Context, into a straightforward function.
Cloudflare’s UI for managing DNS records is nice, but this method can help you import larger batches of changes faster.
I’m a member of a few software teams and, very frequently, we commit code to our main branch. Common themes within my teams are not to have a develop
branch or even release cycles. Instead, we release regularly.