The document discusses the disparity in developer productivity and emphasizes the need for agile, DevOps, and continuous integration/deployment practices in software development. It highlights the importance of using data for resource allocation, team management, and improving code quality while promoting a more responsible and accountable development environment. Open source practices are underscored as essential for enhancing software engineering and reducing costs.

1. 10.20.2005
The New Developer Productivity
St Mary Axe, May 2015

2. 2
About Us

3. 3

4. 4
Disruption!

5. 5
“So 2:1 is a big dynamic range for most things in
life. Now, in software, and it used to be the case in
hardware, the difference between the average
software developer and the best is 50:1; Maybe
even 100:1”
- Steve Jobs

6. 6
Tech is Fragmenting

7. 7
Language Rankings

8. 8
The CIO is the Last To Know

9. 9
Forking as a Good

10. 10
Social Coding as Public Utility

11. 11
Agile and Continuous Deployment

12. 12
“The lumber industry sells what used to be waste
— sawdust, chips, and shredded wood — for a
pretty profit. Today you’ll find these by-products in
synthetic fireplace logs, concrete, mulch, particle
board, fuel, livestock and pet bedding, winter road
traction, weed killing and more.”
Jason Fried, 37signals

13. 13
“In contrast to most traditional survey methods,
search data are collected as a by-product of normal
activity”
- the Bank of England

14. 14
Borrow from Web Companies

15. 15
Data, Teams and Competitive Advantage

16. 16
Wrapping Up
The business is demanding that you deliver more products to market faster.
response: Agile, DevOps, and Continuous Integration/Deployment
The War for Talent hasn't even started yet - use data for resource allocation and human resources.
Software development is an art but also science – data is a bridge.
Let developers do their jobs and make infrastructure choices, but measure the results.
Watch, don’t ask.
Agile wins, precisely because it is data-driven. Developers thrive on good data.
Break big problems and projects into smaller pieces run by smaller, more responsible, teams.
(At Netflix) the Developer is responsible if they break the build.
With large, legacy code bases, data allows you to find the best likely fix(er).
Use data to reduce organisational disagreements.
Open source is central to good software development engineering practice
Higher quality apps lower support costs.