Farewell ShipIt, Hello Merge Queue!
On a previous post on my block I talked about "ShipIt" a GitHub Bot we built when I was at Intuit to improve DevEx. Here I explain how achieve the same without any bot
On a previous post on my block I talked about "ShipIt" a GitHub Bot we built when I was at Intuit to improve DevEx. Here I explain how achieve the same without any bot
Ever since I started learning how to code I have kept hearing people saying that Java is too verbose, too complicated, takes too long to do anything, and it's a pain to work with. But is that all true? Or is it just nitpicking?
We all have learned to love these interactive shell to test solutions for a specific problem, but the question is when you should use these and when you should not?
Throughout my career I've worked in many teams, with different ways of working. Some of them worked really well some others not so much. In this post I try to explain the few key factors that I think were the most important for us to deliver features and ensure that other teams can depend on us so that they can do the same.
We all know the feeling when the main branch is broken, and you need to run to fix. To be hones who broke doesn't matter but the fact is that no one can deploy does. In this article I'll share a way I use to try to avoid it and enable everyone to release something when they need to.