nephrenka

4 ms·

1.
Practices I Abandoned with Agents: An Ode to Test-Driven Development(adamtornhill.substack.com)
2 points by nephrenka 7d ago|0 comments
2.
by nephrenka 23d ago
> This is insanity, and at the same time, the strongest and best argument to fire all these useless humans. Well, there's still the human in the loop, uncertainty and risk drive the reviews. From the article: "I never read all
3.
An opinionated (and mainly correct) guide to naming(adamtornhill.substack.com)
4 points by nephrenka 3mo ago|0 comments
4.
Why Merge Conflicts Became the New Agentic Bottleneck(adamtornhill.substack.com)
3 points by nephrenka 4mo ago|0 comments
5.
Compressed Cognition: The Cost of Faster Coding(adamtornhill.substack.com)
5 points by nephrenka 4mo ago|0 comments
6.
Coding Is Dead ( But It Still Smells Funny)(adamtornhill.substack.com)
2 points by nephrenka 5mo ago|0 comments
7.
by nephrenka 1y ago
Fascinating! I spent the past two days at a software conference in the Barbican. (The SDD conf). The place is truly beautiful in a brutalistic way. Had lunch in the greenhouse.
8.
by nephrenka 3y ago
Agree -- maintainable code was always important, but even more so in the age of AI. Unless we introduce proper guardrails via reliable code quality metrics, all these AI assistants will serve more as legacy code generators than genuine help
9.
by nephrenka 3y ago
> our research significance is currently limited in that it does not directly measure what code was AI-authored There is actual AI benchmarking data in the Refactoring vs Refuctoring paper: https://codescene.com/hubfs&#x2
10.
by nephrenka 3y ago
> 8. Your Code as a Crime Scene (Finding problems in the code using code history) There's a brand new 2nd edition on its way: https://pragprog.com/titles/atcrime2/your-code-as-a-crime-sc...
11.
by nephrenka 3y ago
There are two books which I keep coming back to learn from: * Structure and Interpretation of Computer Programs: SICP changed the way I view programming. It's an excellent intro to the mindset of solving problems with code and how to i
12.
by nephrenka 5y ago
I'm not John, but I'm one of the authors of the research paper. Indeed, one goal with this work is to complement DORA’s delivery metrics with similar correlations between code quality and its business impact. Hopefully, this work
13.
by nephrenka 5y ago
This is indeed something that the academic research paper (see https://arxiv.org/abs/2203.04374 ) identifies as Future Work. There could be a code familiarity component that explains the large risks and variations. From
14.
by nephrenka 5y ago
Yes, this empowers development teams to have data-driven tech debt conversations with management. I wish that I had this type of data myself back in the day. Would have been so much easier to push back on wishful deadlines.
15.
by nephrenka 5y ago
Yes, cyclomatic complexity might be a popular metric but it was never a good one. At least not for its original purpose. That said, I occasionally find cyclomatic complexity useful: cyclomatic complexity is a pretty good estimate on the num
16.
by nephrenka 5y ago
I started to code 35 years ago on a Commodore 64. The beauty of those machines was that you literally had to write code to even load a game (LOAD, RUN, etc.). As such, the barriers to start exploring programming on your own were low: the de
17.
by nephrenka 5y ago
That's a great visual presentation, but not really an innovation. The CodeScene tool has that built in together with a set of deep analyses on top (see https://codescene.com/ ). There are several public conference talks
18.
by nephrenka 6y ago
Fully agree! That's why I recommend to monitor the code health trends continuously -- the earlier we can catch any potential issues, the better: https://codescene.io/projects/167/jobs/55946/results&#
19.
by nephrenka 6y ago
Yes, there's an on-prem version of CodeScene that can be run on private servers. The latest release is described here: https://codescene.com/blog/architectural-analyses-simplified... To analyse Perforce, you setup
20.
by nephrenka 7y ago
CodeScene isn't built on the open source tool. CodeScene's engine is implemented from scratch in order to deal with large-scale codebases. The basic metrics are the same, but CodeScene adds plenty of information and pattern detect
21.
by nephrenka 8y ago
Cool - thanks! While the measures a simple in theory, there are some practical challenges; git repositories tend to be messy. So part of the practical challenge is to clean the input data (e.g. filter out auto-generated content, checked in
22.
by nephrenka 8y ago
A large codebase under active development presents a moving target; Even if you knew how something worked last week, that code might have changed twice since then. Detailed knowledge in the solution domain gets outdated fast. To address thi
23.
Top 5 Contemporary Software Engineering Books(medium.com)
15 points by nephrenka 8y ago|0 comments
24.
Manipulate Functions with the J Language(adamtornhill.com)
112 points by nephrenka 9y ago|31 comments
25.
Analyzing Patterns in the Evolution of Linux(empear.com)
4 points by nephrenka 10y ago|0 comments
26.
The Signs of Trouble: On Patterns, Humbleness and Lisp(adampetersen.se)
2 points by nephrenka 14y ago|0 comments