Viewing profile — nephrenka
nephrenka
HN member- Joined
- Thu, Oct 11, 2012, 8:59 AM UTC
- HN karma
- 63
- Public activity
- 24 items
- HN profile
- View on Hacker News ↗
About nephrenka
No profile information was provided.
Recent public activity
- story
- story
- story
- story
-
comment
Comment #43975482
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.
-
comment
Comment #39522303
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…
-
comment
Comment #39206022
> 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 Refuctori…
-
comment
Comment #38238736
> 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-cr…
-
comment
Comment #38238723
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…
-
comment
Comment #30711383
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 qual…
-
comment
Comment #30711304
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 explai…
-
comment
Comment #30711241
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 muc…
-
comment
Comment #30428009
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…
-
comment
Comment #30414204
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…
-
comment
Comment #28085809
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/ ). Th…
-
comment
Comment #25196204
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/j…
-
comment
Comment #25196171
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.…
-
comment
Comment #21031159
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 CodeS…
-
comment
Comment #19270699
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 inp…
-
comment
Comment #19270063
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 knowled…
- story
- story
- story
- story