Tune in to the latest @seradio episode for an interview with @abinoda:

They cover the importance of developer experience, how to measure it holistically, and how both engineers and senior leaders play a part in improving it.

se-radio.net/2022/08/episod…

How Snyk’s @cfhirschorn sees their Developer Experience team evolving:

4. Developers can be grouped into six categories based on their “ideal workdays”.

Identifying these groups can help us understand the wide range of definitions of productivity, and how managers can better support their teams.

Mojtaba Hosseini (Director of Eng at Zapier) with a better way to approach adopting engineering metrics:

(full conversation: getdx.com/podcast/adopti…)

Nahi Ojeil, VPE at @captivateiq, with a practice for improving cross-team collaboration:

(Full interview here - getdx.com/best-practices…)

Minh Pham from @IbottaTech on the decision for investing in a dedicated developer experience team:

(full interview: getdx.com/podcast/foundi…)

Companies invest in Sales Ops, Marketing Ops — why has their investment in Engineering Operations been delayed?

On the latest Engineering Enablement episode, Ryan Atkins from @asana shared his take:

Full interview → getdx.com/podcast/engine…

Sometimes developer experience teams have to determine whether a problem is something they can actually help with, or if it's something that exists at the local team level.

One tactic from @Lethain: embed DevEx/Infra team members in engineering.

At The Financial Times, Engineering Enablement isn't just focused on standardizing tooling — they look for ways to encourage best practices and increase developer engagement too.

Hear more from @VictoriaJMS on the latest Engineering Enablement episode: getdx.com/podcast/engine…

We've teamed up with @getclockwise to host a fireside chat this Friday — we'll learn from a leading researcher about:
1. Which disruptions are most damaging,
2. Power dynamics in interruptions,
3. How stress and interruptions are correlated, and more.

➡️lu.ma/interruptions

Step 2: Create templates for codebase-specific documentation.

“Engineers work in lots of different ways, but we need to standardize around a few things, like writing commit messages, the effective use of version control and git, and handling pull requests.”

Step 1: Define a logical structure.

Kaitlyn chose headings like Infrastructure, Testing, People, and Codebase — the places where people may intuitively look when trying to find information.

When’s the right time to hire an Eng Effectiveness team? The TLDR: Whenever it would be useful to start standardizing tooling, best practices, or metrics across teams.

@peterseibel with today’s idea for engineering teams:

Two areas to consider when improving internal documentation: the authoring experience and discovery experience.

Authoring & maintaining docs should be as low-friction as possible. Documentation should also have some navigation structure and be easily searchable.

— @ktheory

“We’ve taken the 5 categories of the SPACE framework and matched them to specific metrics across the SDLC. On one axis is all the phases of the SDLC; on the other axis are the SPACE framework categories. And in each cell in the intersection of the tool, we've put in metrics.”

A product mindset can help engineers be successful on an internal-facing team like Developer Experience.

@cirpo with today’s idea for enabling engineering teams:

“After the initial investment we made in improving our developer experience, we put in anti-slip measures. Coming out of that quarter became the new baseline, and we wanted to make sure we could only grow from there.”

@LizSaling with today’s idea for engineering teams:

“If you’re taking [developer] documentation seriously, put it on the scorecard. Look for good writers. Put it in the career ladders too. It’s a competency that individuals need to develop if they’re to move to the next level.”

@prla with today’s idea for engineering teams: