6 Steps To Survive A DevOps Transformation

From measurable goals to targeting quick wins and sharing lessons learned, here are the steps that can lead to DevOps success.
DevOps is everywhere, and if you're not already in the middle of a DevOps adoption program, there's probably one coming your way. Here's how to survive, in six only moderately painful steps.

SSH Examples, Tips & Tunnels

Practical SSH examples to take your remote system admin game to the next level. Commands and tips to not only use SSH but master ways to move around the network.

Knowing a few ssh tricks will benefit any system administrator, network engineer or security professional.

Strategies for Organizing Code

This article outlines four different strategies for organizing code: by component, by toolbox, by layer, and by kind. I think these four form a kind of hierarchy with regards to which kind of cohesion they favor and in my experience they cover most of the real-world code I’ve worked with.

Dinner with friends: How tech startups test, organize, and review their code

Building software is hard. In a casual dinner with ten developers (friends) from leading startup software teams, shared a behind-the-scenes look at their processes (and frustrations): testing, deployment, and code reviews. 

The Problem with Shared Code

The Problem

To be clear, sharing code is not hard. There are many different ways to share code in general and most of them are relatively easy to implement. The hard part is doing it efficiently at scale which means:

1. Multiple code modules (that share some code)
2. Multiple team members
3. High rate of change
4. Little to no loss of individual productivity

What’s a monorepo? - Why Google Stores Billions of Lines of Code in a Single Repository

What’s a monorepo? Imagine if every time you needed to make a new source control repository, you just made a new top-level folder in your current repository instead. You’re doing monorepo! All the software written by everyone in your company stored together, versioned together.

Why every development team needs continuous delivery....

Continuous delivery helps you move faster and retain talent. Yet only 28% of dev teams do it! Find out why continuous delivery could be your competitive advantage.
28%. That is the number of teams currently practicing continuous delivery (CD) across all projects, company wide. That means a whopping 72% of software teams are likely to feel dread instead of relief when they hear the term “release”