A while ago, I told you why your commit messages suck and what to do about it . On that occasion, I talked briefly about AI, stating that I don’t think that the usage of LLMs (Large Language Models) fundamentally changes any of the points I made in the post. However, the topic of LLM-generated commit messages is relevant enough to deserve its own treatment, especially now that more and more people…
ℹ️ Info Editorial note: I originally wrote this post for the CoderPad blog. You can check out the original here, at their site . When using databases, searching for values that match a given pattern is a familiar necessity. You might want to retrieve all students whose last name starts with a given letter or update all products whose ids include a particular string. If you’re a PostgreSQL user,…
Welcome back to my journey of building git from scratch in Go, in order to learn more about both. If you don’t know what I’m talking about, go read the first post . It’s Been a While I published the first entry for this log of sorts on March 9th. What have I been up to, and why it took me so long to continue the series? The answer is what you probably already know: I’m a busy adult and don’t have…
Your commit messages suck. They are, at best, useless. At worse, they are harmful and misleading. I don’t say this to be mean. Quite the opposite, I mean this in the most charitable way possible. I’m here to help. If you know you’re the exception, you can stop reading. I’m serious, close this step and go watch some YouTube. There, I just gave you back some minutes, you’re welcome. Still here?…
I’ve recently started working on my newest project: building git in Go, from scratch. What’s the point in that?, you might be wondering. Well, it’s quite a useless project in the sense that, you know, git has existed for 20 years. (Thanks, Linus). My goal with this project is two-fold: learn the Go language strengthen my knowledge about git internals Project Scope I don’t intend to implement 100%…
Photo by Denis Oliveira on Unsplash I’m starting a series of articles in which I’ll define some concepts or terms that are common in software development, and I’m starting with Breaking Changes . After all, why start with A like a normal person? Ok, but…why write such a series? Mainly because I want to create the resources I wish I had when I was starting out. Back then, it used to drive me crazy…
ℹ️ NOTE I originally wrote this post for Nimbus. You can read the original at their site . What’s Developer Experience? Why Should You Care? In software development, we talk a lot about user experience, and rightly so. Since it’s the end user who benefits directly from the software we write, it makes sense that they’re front and center in all our efforts. But recently, another term has started to…
ℹ️ NOTE I originally wrote this post for Cloudbees. You can read the original at their site . Repositories in Git work in a fundamentally different way from most other tools. One of the most glaring examples of said differences is branching. In most other VCS tools, branching is this elaborate ceremony. They make a huge deal out of it, and developers just give up, preferring workflows that don’t…
It’s weird how our memory works, right? I can’t quite remember what I had for dinner two nights ago, or the reason why I failed to attend the gym some days last week. But I do remember vividly a specific bug that I fixed in my first programming job after graduating from college. There was this method that wasn’t working properly, and its signature was something like this: void ProcessOrder ( int…
Photo by Francisco De Legarreta C. on Unsplash ℹ️ Info Thanks to my friend André Gonçalves da Silva for reading and reviewing earlier drafts of this post If you work in software development, you’ve certainly heard phrases like “Never stop learning,” “You have to stay updated,” “Our field changes very quickly,” and so on. Of course, all these phrases are right, to some degree. But going around…