Remove DevOps Remove Document Remove Engineering Culture
article thumbnail

DevOps

The Programmer's Paradox

Not sure what happened, but my initial understanding of the role of DevOps comes from my experiences in the early 90s. I was working for a big company that had a strong vibrant engineering culture. Before we’d spent a lot of time coding, we write down what we were going to do in a document and send it out for feedback.

DevOps 45
article thumbnail

InnerSource, a practice that brings open-source principles to internal software development within organizations

Xebia

It involves well-documented projects, making it easy for anyone within the organization to discover, understand, and participate. Perhaps your focus is on breaking down traditional boundaries through DevOps practices. These packages are available through platforms like Azure DevOps Artifacts or GitHub Packages.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Engineers New to Honeycomb, What Did You First Notice About How We Do Things Here?

Honeycomb

My first DevOps role was at a startup consulting for other startups. My last company, a data analytics startup, was probably the biggest I’ve worked at (~500 people) where I split my time between “traditional DevOps” (i.e. I’ve spent most of my time at startups or smaller companies. I then moved on (burned out) to internal roles.

article thumbnail

Three practices managers can use gamification to drive enterprise change

Xebia

One example of such a task is documentation, and it is often done at the end of a project but not completed. A progress bar can be of great value when you cut up big goals into smaller, achievable goals. Within many organizations, initiatives are started but not completed due to people losing motivation to take the last steps.

article thumbnail

The Spotify Model of Scaling – Spotify Doesn’t Use It, Neither Should You

Agile Pain Relief Notes from a Tool User

Their approach grew from their people and their culture. In addition, all attempts to document a culture are simplifications that are missing details that were important. Versus a pipeline that requires waiting for the DevOps team to deploy for them. FitBit, John Deere), grow your own Agile model.

Agile 122
article thumbnail

Tips for Onboarding New Hires Remotely

LaunchDarkly

At LaunchDarkly, our IT and Ops teams have clearly documented in Confluence (a program we use like a well-oiled machine) the process changes they’ve been making in response to the all-remote work paradigm. Be sure to thank your Ops person too. Both these departments are doing a lot of extra work to ensure our remote work situations are solid.

article thumbnail

Panel Discussion: Teams, Processes, and Practices in DevOps

LaunchDarkly

Well, so what really has struck me about sort of the modern reality of DevOps and SRE life has been, I’ve gotten to know more of, has been this sort of deep shared responsibility for something that you didn’t make, that you can’t necessarily fix. At the moment our documentation is kind of in the user manual style.