Sign in

Technical Coach at Redgate Software.
Photo by Patrick Fore on Unsplash

One of the growing topics in technical authoring over the past few years has been Documentation as Code — a philosophy that “you should be writing documentation with the same tools as code”, rather than it being an awkward, disjoint part of your work.

Which tool to use?

As with anything, there are loads of Documentation as Code…

Photo by "My Life Through A Lens" on Unsplash

We’ve already shared what a software engineering career looks like at Redgate, but there’s far more to the modern software organisation than engineering alone.

Photo by Cookie the Pom on Unsplash

There’s no “one right way” to build software, and there’s no “one right way” to grow your career in software either. That can make it hard to know what to expect with different companies.

Photo by Jordan Opel on Unsplash

We’ve recently shared about Redgate’s new Progression Framework, and how it’s helping folks at Redgate develop their skills and careers.

Back in the mists of time

Our journey started way back in 2018.

Photo by Alex Zamora on Unsplash

Book clubs are a popular way for groups to work through a book or article together and share their insights.

How did it work?

Well, here’s what we did:

  • Signed…

Photo by JESHOOTS.COM on Unsplash

Working as a team of internal coaches isn’t easy. We do complex work with a wide range of people, across many areas and levels within the company.

Photo by Alex Holyoake on Unsplash

Back in July we shared our early experience learning from the “Four Key Metrics” presented in Accelerate.

Photo by Heather Mount on Unsplash

There’s been a lot of excitement about the book Accelerate, which summarises research from the past several years of the State of DevOps report (which Redgate sponsors).

How to track them?

We trialled manually gathering data, by recording release dates or timestamping index cards. …

Photo by Naveen Jack on Unsplash

Some of our teams at Redgate have adopted a Zero Bugs Policy.

Impact on the teams

Of our two trial teams, one was effectively taking a Zero Bugs approach already while the other was faced with a significant change in how they work.

Photo by Paweł Czerwiński on Unsplash

Some of our teams have been trying out a zero bugs policy, following a simple remit:

If a bug is reported that you feel you should fix, then you fix it right away. If not, you close it.

We wanted to share what we’ve learnt.

Did it help with issue management?

For us, yes.

Do all teams follow the same process?

Not quite.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store