https://platformengineering.org logo
#platform-culture
Title
# platform-culture
d

David Lluna

04/27/2022, 8:57 AM
Hi everyone!, I'm doing a little research on the different flavours of
Engineering Productivity
in the industry, I found a lot of different ways to call groups with similar goals ( of course with a lot of nuances as it depends on company size, maturity, etc )
Copy code
Developer Tools ( Auth0, Facebook )
Engineering Productivity ( Google, Pinterest, Gitlab )
Developer productivity ( Airbnb, Zalando )
Productivity Engineering ( Spotify, Netflix )
Engineering Effectiveness ( Twitter )
Developer Efficiency ( Datadog )
The issue with the examples above ☝️ is that those represent only a very small percentage of the industry, I'm interested on the other maybe 99% ( loving this post from Jean Yang https://future.a16z.com/software-development-building-for-99-developers/ ) How do you call
the team
doing this kind of work in your company? Do you see
Platform Engineering
as one of the branches of
Engineering Productivity
?, or do you see it as independent discipline? 🧵
👀 2
In our case, the team is called
Tools
at the moment, and emerged organically from the SRE organization, including some developers from outside the SRE org
m

Michael W

04/27/2022, 9:05 AM
In my opinion, I’m not sure it’s necessarily about the name of the team as such as understanding the dynamics of the org. I’ve seen teams called e.g. ‘DevOps Architecture’ who have a KPI for adoption % of the platform, because leadership already understands that this is the most efficient way to get things done and everything else is discouraged. I’ve also heard of companies where it is not a team but a single individual who is given the mandate to address productivity, and needs to rely on the other teams to make change. Perhaps more about what is the charter of the team/person and how are they measured?
2
b

Bruno Dias

04/27/2022, 10:03 AM
At the beginning of the year, we created the Developer Experience area. As our peers, we have our SRE and Security areas.
d

David Lluna

04/27/2022, 10:30 AM
@Michael W Agreed, I have also heard of such individuals.
h

Henning Jacobs

04/27/2022, 10:46 AM
In Zalando, "Developer Productivity" is part of the "Builder Infrastructure" organization which also contains SRE, Observability, etc.
b

Bruno Dias

04/27/2022, 10:51 AM
We call here Tech Infrastructure. Different names for similar problems. 😂 “There are only two hard things in Computer Science: cache invalidation and naming things. -- Phil Karlton”
h

Henning Jacobs

04/27/2022, 11:03 AM
Asking the other way around, regardless of naming, one could ask which department is focusing on tracking and improving Software Delivery Performance (Accelerate)?
👍 1
d

David Lluna

04/27/2022, 12:44 PM
@Henning Jacobs Interesting, I like that approach, thinking about our specific case, there are different teams tackling different contributing factors for Software Delivery Performance
s

Scott Mathson

04/27/2022, 10:05 PM
@Bruno Dias "There are only two hard things in Computer Science: cache invalidation, naming things and off by one errors." 😉
😂 1
b

Bruno Dias

04/28/2022, 1:14 AM
Here at VTEX, we articulate these (and other metrics) as Development Lifecycle Metrics. It is our focus (in DX) to track and improve them.
d

Daniel Serodio

05/02/2022, 9:54 PM
@Bruno Dias, what are your Development Lifecycle Metrics? How do you measure Platform adoption and "user happiness"?
b

Bruno Dias

05/06/2022, 11:20 AM
Hi @Daniel Serodio , we are derived from DORA metrics Lead time for changes • here we can split in other two: time to request a review, time to review • in the future we want to expand to add cycle time on top of LTC, this will consider also the time to design Change frequency Change failure rate Time to restore services Time between failures Service Level Objectives
👍 1
We are still in the begging of the adoption. But how I thinking to measure user happiness it will probably be with CSAT
CSAT will be specific for each service, tool that we deliver in the platform. How is the satisfaction of the engineer regarding the build workflow, how they feel regarding the configuration management system… and so on.
d

Daniel Serodio

05/06/2022, 4:38 PM
Got it, thanks!
n

Nina S

05/21/2022, 7:37 PM
@Bruno Dias : How big is your team and which tool do you use for tracking the metrics
b

Bruno Dias

05/21/2022, 10:12 PM
We have >200 engineers. We are testing (for some metrics) the codacy pulse. (DX team has ~13)
n

Nina S

05/22/2022, 3:59 AM
@Bruno Dias: Got it! How do you balance context switching between the DX(13engineers) and manage the flow of requests from engineers?
b

Bruno Dias

05/25/2022, 5:45 PM
Align with the rest of the organization the priorities in that timeframe. When we have a good align we can say “no, why” in a simple manner. Now we have some things align and others not. So I need to manage expectations of the org needs.
n

Nina S

05/25/2022, 11:04 PM
Same! Thanks for the response @Bruno Dias
23 Views