DevEX - reference for building teams, processes, and platforms
The entire experience that software engineers have at work is known as Developer Experience (DevEX).
DevEx includes every facet of a developer's engagement with the technology from the time they begin coding until the modifications are deployed. Standing up and maintaining an environment that facilitates developers' work by giving them the tools and resources they require to rapidly develop, test, and deliver software is the goal of DevEx. This covers everything, from the onboarding procedure to the development process's speed and dependability, the capability to request dev/test environments with a push of a button, feedback loops, collaboration opportunities, and the workflows they adhere to in order to maximise productivity and efficiency.
Unblocking The Main Thread Solving ANRs and Frozen Frames
DevEX - reference for building teams, processes, and platforms
1. DevEX - Reference for Building
Teams, Processes and Platforms
17 April @API Days
Singapore
@sergiu_bodiu | github.com/sergiubodiu | in/sergiubodiu
sergiubodiu.github.io/sergiubodiu/
6. My Journey
My Journey so far Passionate IT
craftsmanship #blitzscaling,
avid student of life, autodidact,
#cloudnative evangelist.
6
DevOps Community
18. DevEX - Reference for Building Teams, Processes and Platforms
A favela squatters occupy vacant land at the edge and construct shanties of salvaged or stolen materials.
27. https://dannorth.net/mckinsey-review/
To cut to the chase, I see two main planks to your thesis …, and which are both
erroneous:
1. Software development is a reducible activity, and can be
measured with reductionist tools.
2. Software development is primarily about coding, and
anything other than typing code into a computer terminal is
waste which we should seek to eliminate.
When Facebook acquired WhatsApp for its 500 million active users,
WhatsApp had 13 engineers.
The relational database SQLite runs in pretty much every compute device on the
planet: phones, tablets, browsers, servers, laptops. It has millions of automated tests
and only three core developers.
28. https://xkcd.com/688/
Story from Facebook about McKinsey recommendation.
“The McKinsey surveys provided valuable feedback about
the current state of developer sentiment.” - Kent Beck
29. Then folks decided that they wanted to make the survey results more legible so they
could track trends over time. They computed an overall score from the survey.
Very reasonable thing to do. That was good for another year. A 4.5 became a 4. What
happened? Then those scores started cropping up in performance reviews, just as a
"and they are doing such a good job that their score is 4.5".
That was good for another year. Then those scores became goals. Now things
started getting unhinged. Directors put pressure on managers for better scores.
Managers started negotiating with individual contributors for better survey scores.
“Give me a 5 & I’ll make sure you get an ‘exceeds expectations’.”
Directors started cutting managers & teams with poor scores, whether those cuts
made organizational sense or not.
https://newsletter.pragmaticengineer.com/p/measuring-developer-productivity https://tidyfirst.substack.com/p/measuring-developer-productivity