The engineering intelligence platform designed by leading researchers.
Joined March 2022
- Tweets99
- Following2
- Followers773
- Likes148
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/episode…
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/adopting-e…)
Nahi Ojeil, VPE at @captivateiq, with a practice for improving cross-team collaboration:
(Full interview here - getdx.com/best-practices/cro…)
Minh Pham from @IbottaTech on the decision for investing in a dedicated developer experience team:
(full interview: getdx.com/podcast/founding-a…)
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/engineerin…
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/engineerin…
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:
“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.”
