As someone who spends a reasonable amount of time writing, rehearsing, and giving tech talks, I often find folks new to speaking about tech asking me: how do you do it? How do you know that you will be able to write and give an excellent tech talk? The simple
In the 15 or so years we've been on a DevOps journey as an industry, we've seen several waves of tooling and processes. When teams were wholly separated, each brought their tools to bear on the problem. Then, as organizations brought teams together, they began to standardize onto a set
If there is one thing I've learned about actually doing software work in production environments over my career, it is: debugging is hard. And once you accept that it is hard, you have no option, in my mind, except to fall back on two essential but different tools to address
You can also read my blog post on changing the default branch stream upstream in git or renaming your own default branch in GitLab. This post is a living post where I document all the different places where one may need to update the default branch when changing the name
This article was inspired by Scott Hanselman's article about the same topic. You can also read my blog post on changing the default branch stream upstream in git or changing your default branch everywhere else. Also while you're here, go follow me on Twitter So let's say you're bought in:
I've been using Git for years and always took for granted that the default branch name was master. After all, it's been that way since May 2005 long before I started using Git. At the same time, I've been very supportive of efforts to eliminate master/slave metaphors in tech.
Since I was an early adopter of Slack, I've been using Slack for almost half of my career at this point. I've always been a fan of chat as a way to collaborate with friends and colleagues. Before Slack, it was HipChat - which I brought into my first role