Measuring Developers Productivity... McKinsey what's the point?
HTML-код
- Опубликовано: 10 сен 2023
- 📢 Developer Productivity: A Deep Dive 📢
Recently, McKinsey stirred up the tech community with an article on developers' productivity.
www.mckinsey.com/industries/t...
Today, I dissect this topic and explore the intricate world of software engineering, going beyond just lines of code.
🖥️ In this video, you'll discover:
My perspective as a software engineer on why measuring individual productivity might miss the mark.
The intangible contributions developers make that go beyond coding: fostering team dynamics, mentorship, and more.
How focusing on individual metrics can hinder creativity and stifle innovation. Why should a developer risk trying something new if it might affect their 'productivity' score?
The potential pitfalls of a metric-driven approach. Engineers are problem-solvers by nature, and if you give them a metric, they'll find ways to 'game' it.
🌟 Team vs. Individual Metrics 🌟
Let's delve into the debate on whether we should focus on team dynamics vs. individual achievements. Software engineering, at its core, is a collective effort. So, should we then lean towards measuring team productivity instead?
🤝 The Importance of a Positive Culture 🤝
The atmosphere within an organization plays a crucial role. A positive, collaborative environment will naturally attract passionate developers and weed out those who don't align. In contrast, a toxic culture can suppress innovation and make even the best talents underperform.
❓ Question of the Day:
Do you believe in measuring developer productivity? What are your thoughts on McKinsey's article and the points raised in this video? Drop a comment below; let's engage in a meaningful discussion.
If you resonate with content surrounding platform engineering, coding, and the developer experience, don't forget to hit that subscribe button! 🔔 Your support means the world and helps us create more insightful content.
Thank you for tuning in! Stay curious and keep coding. Catch you in the next video. 👋🏼 🚀
WHO AM I:
Hey friends, welcome to my RUclips channel @outofdevops . If you're new my name is Anto, here I talk about software engineering and software engineers. Don't forget to comment like and subscribe 👍🏻.
RUclips GEAR:
🎥 My RUclips Camera Gear - kit.co/outofdevops
MY SOCIAL LINKs:
🐦 Twitter - / outofdevops
📘 Facebook - / outofdevops
📰 My blog - amasucci.com
📸 Instagram - / outofdevops
GET IN TOUCH:
If you’d like to talk, I’d love to hear from you. Tweeting @OutOfDevOps directly will be the quickest way to get a response, but if your question is very long, feel free to email me at hi@OutOfDevOps.com.
PS: Some of the links in this description are affiliate links that I get a kickback from 😜 
Наука
Making simple. Whoever wants measure a developer, don't know anything about development work. Good amount of work is in their mind until it brings the solution. If it is a simple change... maybe is double in some sense.... but things that brings value comes from developers mind/brain... Your points are good too!!
Goodhart's Law : "When a measure becomes a target, it ceases to be a good measure."
Instead of focusing on meaningless metrics companies should focus on healthy team topologies…
You can't manage what you can't measure! MUHAHAHA. Wait how did we make it before numbers? Is logic without numbers possible? Arghhh...
Numbers are just a way to represent measurements. Without numbers you can still measure. But without measuring your previous X, how do you know if you’re getting better at it or not? I may have not fully understood your comment.
@@OutOfDevOps It is this stupid mantra about managing only being possible with metrics that turns a lot of otherwise intelligent human beings in management positions into draconian game masters that want to incentivize you the creative on a micro level to do the right thing. They don't know anything real but they know that there is some correlation between output and success so the output needs to be bigger and faster. Add to that the generic management approach that thinks domain knowledge is irrelevant and you could put a cockroach in charge as it has the same objective function of maximizing some gain short term that feels right instead of the human planning, conceptualizing, remembering stuff and winning in the long run over all other animals.
I see what you mean, I have read stories about customers loyalty metrics improving by simply hiding the ‘unsubscribe’ button 🤦♂️. I think this is the problem with most definitions/mantras, they don’t capture every possibility.