Xebia

NOVEMBER 1, 2023

It involves well-documented projects, making it easy for anyone within the organization to discover, understand, and participate. GitHub provides a comprehensive set of documented principles and practices to assist you in getting started with community collaboration.

Open Source 162

Open Source Software Review Software Development Organization 162

CircleCI

OCTOBER 25, 2021

I’m hopeful that work to document and generalize our approaches to software and infrastructure migrations will help in future. Go through your daily notes, journal, lab notes, “brag document”, “nice things people say” file, pull requests, key documents you’ve worked on - anything that comes to mind. by a better original plan.

Engineering 104

Engineering Software Review Weak Development Team Systems Review 104

Cloudera

NOVEMBER 12, 2021

As an engineering culture we always want to provide unlimited flexibility to open up a world of opportunity. To do this, customers had to follow our documentation and many chose to hire Cloudera professional services to implement this. Yet the business user is here to just accomplish a few goals that we can help them with.

Enterprise 98

Enterprise Software UI/UX Engineering 98

Xebia

APRIL 21, 2022

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.

Enterprise 130

Enterprise Games Social Systems Review 130

CircleCI

MAY 28, 2020

When I joined CircleCI in 2018, the engineering team had been growing by 50 percent year over year, and also increasing in terms of geographical distribution. And after all this growth, we were running into challenges around evolving our engineering culture. Conversely, the management team was incredibly small.

Culture 134

Culture Engineering Performance Energy 134

Honeycomb

FEBRUARY 15, 2022

It is intended to be a living document that we can modify as we see fit, but so far it hasn’t changed too much. The charter (aka what site reliability engineers should care about). After a few drafts and some back and forth for feedback, I had a short charter that gave a general orientation of SRE work here at Honeycomb.

Software Review 133

Software Review Systems Review Engineering Culture 133

Apiumhub

MARCH 3, 2022

Getting Stuff Done Days (GSDD) is an initiative used by many top companies to improve the quality of the software development and boost a proactive, continuous improvement-based engineering culture in their organizations. There should be a document for each initiative that proposes the work ahead. No individual work.

Weak Development Team 59

Weak Development Team Software Development Software Review Software 59

Gitprime

MAY 30, 2019

These are strategies that these three tech leaders have used in their organizations to improve connectivity and reduce isolation: DOCUMENT EVERYTHING. Documentation is key,” Armandpour says. “We We work with the presumption across the board that when your water cooler conversation turns into a decision, you must document it.”.

Engineering 75

Engineering Weak Development Team Part-Time VPE Technical Advisors 75

James Shore

AUGUST 19, 2024

PDF) Culture Changes The purpose of the new career ladder is to help change the engineering culture at OpenSesame. mostly a matter of documenting what they already know. We rolled it out in July, so now’s a good time to share what we’ve learned so far. Here’s the latest version of the ladder.

Software Engineering 63

Software Engineering Technical Advisors Engineering Software 63

Honeycomb

MARCH 16, 2023

It is a living document after all! Much like last year, we still expect our charter to be a living document. We are embedded in teams and we handle training, vendor management, capacity planning, cluster updates, tooling, and so on. It was exciting for me to let other folks get their hands in it. What changed?

Systems Review 75

Systems Review Sustainability Engineering Scalability 75

The Programmer's Paradox

APRIL 13, 2023

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. We were doing very complex, low-level work. Worldwide massively distributed fault tolerance. Very cutting-edge at the time.

DevOps 45

DevOps Weak Development Team Engineering Culture Groups 45

Agile Pain Relief Notes from a Tool User

OCTOBER 23, 2023

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. So popular is this problem, it's even got its own meme: Figure 2 from: [link] You can't copy and paste someone else's approach to Agile.

SCRUM 52

SCRUM Agile Coaching Culture 52

Xebia

APRIL 23, 2024

You can find details of some of the important fields you might see in this payload in the Slash Command Documentation. Keep in mind that this data will be sent with a Content-Type header set as application/x-www-form-urlencoded. One of the fields in the payload is the user_name.

Lambda 130

Lambda AWS Authentication Construction 130

Strategic Tech

MAY 3, 2021

An extract of a user journey showing key/high-level milestones Q: Is there a risk to using existing documentation, e.g A: There is always the risk that existing documentation is not up to date or reflects the perspective of a single person. This is what we want to end up with anyway for subsequent steps.

Software Review 52

Software Review Architecture Systems Review Technical Review 52

The Programmer's Paradox

DECEMBER 19, 2011

I landed deep in the heart of a reasonable engineering culture. But if one focuses on documentation that’s useful, rather than on the documentation a management consultant would want, then it’s not so bad either. Early on I moved away from the cowboys. They were driving me nuts. There is sometimes paperwork.

Engineering 40

Engineering Software Software Development Pharmaceuticals 40

Honeycomb

APRIL 26, 2022

Any significant shift in an organization’s software engineering culture has the potential to feel tectonic, and observability (o11y for short)—or more specifically, Observability Driven Development —is no different. the less likely an issue will crop up based on untracked instrumentation. Investigation best practices.

Weak Development Team 52

Weak Development Team Software Review Systems Review Real Estate 52

LaunchDarkly

MARCH 26, 2020

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.

Systems Review 66

Systems Review Software Review Virtualization Meeting 66

Honeycomb

AUGUST 2, 2022

There’s also a wonderful culture of documenting everything in living documents, so it’s easier to find things if I have questions. E : I think my favorite thing about Honeycomb so far has been how open and transparent things are, and how feedback is encouraged, welcomed, and acted on at every stage.

Engineering 52

Engineering Technical Review Software Review Culture 52

Hacker Earth Developers Blog

JUNE 26, 2020

And for me, the big part of the success of growth was actually a step above the pure engineering architecture. It’s firstly rooted in the engineering culture because the first Netflix employees are great people. How do you document that? How do you structure it? And in some cases like even how do you deploy it?

Internet 154

Internet Engineering Architecture Network 154

Altexsoft

MARCH 3, 2023

In the meantime, a developer can work with a QA engineer to identify and fix the bugs or issues that pop up during testing. The technical writer creates technical documentation that describes the product’s functionality, usage, and so on. Get to know more about the Spotify engineering culture.

Examples 52

Examples UI/UX Development Technical Review 52

James Shore

JANUARY 10, 2025

This is a matter of changing organizational culture, and organizational culture isnt easy to change. Our engineering managers are at the forefront of that effort. This is the document that describes what you need to do in order to be promoted. Before I joined, work was assigned to individual engineers.

Engineering 141

Engineering Software Review Weak Development Team Agile 141

LaunchDarkly

JANUARY 14, 2020

At the moment our documentation is kind of in the user manual style. I will say that is something, we have now a customer success team that is focused on things like that, but also that we’re building out more best practice guides.

Weak Development Team 10

Weak Development Team DevOps Testing Agile 10

LeanEssays

JULY 14, 2019

Each focus area was connected to one or more strategic initiatives, and each strategic initiative had a few problems below it, typically with an A3 document attached. They create an engaging engineering culture. We talked to members of several teams and found them uniformly delighted at their new way of working. This is lean.

Software Review 91

Software Review Software Engineering Weak Development Team Continuous Delivery 91

Abhishek Tiwari

SEPTEMBER 15, 2024

Documenting decisions Keeping a record of why certain technical decisions were made can provide crucial context for future development, ideally through Architecture Decision Records (ADRs) or Request for Comments (RFCs). When creating these documents, focus on answering questions like: What was the problem we were trying to solve?

Engineering 59

Engineering Software Review Technical Review Weak Development Team 59

Honeycomb

JULY 14, 2023

ICs may only come into contact with the outputs of this work in the form of an annual presentation or a summary document. Of course, there is engineering work that only fits into extended, quiet blocks of time and requires deep focus, but there was so much other stuff too.

Part-Time VPE 98

Part-Time VPE Engineering Weak Development Team Energy 98