If you can code it, someone will find a way to exploit it ( accidentally or intentionally). Anytime development efforts are involved, it’s important to minimize security risks and bugs. This is also true with GitHub Actions, which allows you to script advanced automation solutions. Because of this, it’s important to understand where injection can occur and how to avoid it.

Git has some interesting behaviors built into it. For example, it makes it easy to squash a set of commits into a single commit. This creates a very simple history. But what happens if that history that you’re eliminating has a tag applied to it? Does that tag get eliminated? Does it point to the newly squashed commit? Today’s article explores what to expect in that situation … and why.

In the last post, we explored the expensive nature of technical debt and bad development practices. Today, we look at how to create financial models that help you to understand your actual costs.

Bad development practices create debt. The interest on that debt can literally make or break a company, and nobody is immune. With Internet Explorer becoming the latest casualty, it’s a good time to explore the problem.

Databricks is a powerful tool for processing data. This is big data, so how do we thing about implementing DevOps practices for these environments?