We support teams in deciding how they work, mob programming, paired programing, individual work, or a mixture of all three.

Engineering @ Pluralsight is a document that outlines how we do engineering at Pluralsight — how we work. It establishes best practices that enable us to deliver the most customer value, create and maintain healthy processes, and perhaps most importantly it shapes a system where engineers and Pluralsighters feel fulfilled and happy at work. Since the first version was created in 2018, Pluralsight has gone through many changes. We recently took the opportunity to reflect on how our practices are serving us and where we could make meaningful adjustments.

Knowledge silos impede our ability to quickly deliver value to our users.

When you find yourself in a disagreement it might be helpful to remember this old riddle: 'What's black and white and red all over?' It has lessons to teach us about how we can think, communicate and solve problems together

At Pluralsight we value creating our product collaboratively. Here are the practices that we have chosen to support that principle.

Pluralsight is different from most engineering organizations. We are structured differently, from what makes up a team to how we deploy code. Let's jump in and walk through a typical day in the life of a developer at Pluralsight.

When I joined Pluralsight, I knew going in that it was going to be a different kind of company. They were already practicing things that I'd been learning about and struggling to implement in my prior company, like TDD and continuous delivery. But I didn't realize just how different my day-to-day work would be until I found that my team was doing something called mob programming.

Perfectionism and pragmatism are often at odds. How do you strike a balance between doing the perfect thing and doing the right thing?

Code reviews are generally accepted as good thing in software development. Some of the benefits include improving quality, sharing knowledge of a system, and promoting collective code ownership. But how you perform a code review matters...