geekjock

7 ms·

1.
by geekjock 3y ago
> One of the main challenges when dealing with technical debt has been the lack of a way to measure it. To help overcome that problem, CISQ/OMG led the development of an Automated Technical Debt (ATD) measurement standard, which is
2.
by geekjock 3y ago
"Lines of code is a much better proxy than reported productivity." Researchers who specialize in this field largely disagree with this. Here's a round-up: https://getdx.com/blog/measuring-developer-activi
3.
by geekjock 3y ago
See this previous paper: https://queue.acm.org/detail.cfm?id=3595878
4.
by geekjock 3y ago
"I'm a bit pessimistic that much of this research is being driven by large orgs in collaboration with researchers who aren't sufficiently independent." I'm one of the co-authors of the study. I think your sentiment
5.
by geekjock 3y ago
Makes sense - I agree with you. My mistake on assuming you were referring to metrics like the ones I listed.
6.
by geekjock 3y ago
> Developer experience encompasses how developers feel about, think about, and value their work.9 In prior research, we identified more than 25 sociotechnical factors that affect DevEx. For example, interruptions, unrealistic deadlines,
7.
by geekjock 3y ago
Agreed with this. We're working on it!
8.
by geekjock 3y ago
"Are there any plans to figure out objective ways to measure productivity" You can't measure developer productivity objectively, assuming you're referring to metrics like lines of code, number of pull requests, or veloci
9.
by geekjock 3y ago
Ever seen developers that are frustrated by technical debt and whose business leaders don't seem to care? This study is aimed to help with that.
10.
by geekjock 3y ago
"You could look at literally any objective measure to proxy actual productivity and be better off than this" It's fairly well-established in research (and in practice) that there is no objective measure of developer productiv
11.
by geekjock 3y ago
+1 If you read the introduction of the paper, you'll see that the aim of this paper is to give managers and developers concrete data to use to help get buy-in on investing in developer experience from business leaders. https:/&#x
12.
by geekjock 3y ago
I'm one of the co-authors of the study. Your critique is valid though by research standards, for this type of study, our sample is sufficient. We are planning to replicate this study on a larger scale in the future, though!
13.
Developer Productivity Metrics Used at Top Tech Comnpanies(newsletter.pragmaticengineer.com)
2 points by geekjock 3y ago|0 comments
14.
by geekjock 3y ago
Accelerate - this book has become an excuse for managers to spend outrageous money implementing metrics like lead time and deployment frequency to measure teams, whereas the book actually advises something very different.
15.
by geekjock 4y ago
Do you know of specific examples of companies that offer this?
16.
Ask HN: How do “private cloud” SaaS solutions work?
1 points by geekjock 4y ago|4 comments
17.
Why it’s difficult to measure developer productivity(abinoda.substack.com)
1 points by geekjock 4y ago|0 comments
18.
Measuring Engineering Productivity(abinoda.substack.com)
2 points by geekjock 4y ago|0 comments
19.
by geekjock 4y ago
I'm a developer and am right there with you. But if you're a decades-old corporation with 10,000 engineers, you need some set of signals to help guide improvements to tools and processes, right? This benefits developers, and there
20.
by geekjock 4y ago
"What should we measure to improve developer productivity?" is a decades-old problem for leaders with no clear solution. There finally seems to be some level of consensus that output metrics like lines of code, # of PRs, and commi
21.
Code ownership correlates with software quality(abinoda.substack.com)
7 points by geekjock 4y ago|0 comments
22.
by geekjock 4y ago
Shoot me an email at abinoda@getdx.com, would love to connect. Right now we're focused on interviewing people in internal-facing roles, but we're exploring doing a series that explores interesting vendors and solutions.
23.
by geekjock 4y ago
I'm the host of the Engineering Enablement podcast: https://getdx.com/engineering-enablement-podcast We interview developers and leaders who work on "platform" teams (e.g. devex, devprod, infrastructure) that
24.
by geekjock 4y ago
I write and share summaries of papers related to developer productivity here: https://abinoda.substack.com Two of my favorites so far are https://homepages.dcc.ufmg.br/~figueiredo/disciplinas/papers...
25.
by geekjock 4y ago
The hard truth is that using velocity to measure performance will guarantee that developers bias their estimates to ensure they make themselves look good, thereby making your "estimates" useless. Anyone who's built software k
26.
by geekjock 4y ago
"Using velocity metrics is like looking for your lost keys under the streetlamp because that's where the light is brightest." ^ 100% agree. Tracking output metrics (including LOC, # of PRs, velocity points) doesn't help
27.
by geekjock 4y ago
Check out this summary of a peer-reviewed paper titled “What Distinguishes Great Software Engineers?” https://abinoda.substack.com/p/great-engineers
28.
by geekjock 4y ago
Julian reached out to me respectfully to resolve the issue. Nice guy, no hard feelings. I understand the startup grind.
29.
by geekjock 4y ago
Article author here — thanks for raising this. My article here was published in April 2021 and repurposed from my GitHub Universe talk given in 2019: https://www.youtube.com/watch?v=cRJZldsHS3c Julian's article was pub
30.
by geekjock 5y ago
How do you handle PRs that are for release trains/branches?

More ›