sagenschneider

4 ms·

1.
by sagenschneider 18d ago
Yes, agree very capable of consuming large amounts of information I'd be interested to see what happens: - to token counts after a year of so of changes, as the specification list grows? - how it goes with concurrent changes in teams?
2.
by sagenschneider 18d ago
Yep, not looking to replace cyclomatic complexity. Looking to use it in what I've researched is a novel new way. Instead of focusing solely on the complexity of the thing you change. Include the context around what you are changing a
3.
by sagenschneider 18d ago
Yes, agree. It's a learning process. I tend to find when I build systems that at some point you need to stop analysis and just start building things to explore the problem. As you do, you prototype, refactor and possibly throw out i
4.
by sagenschneider 19d ago
Yes The research I'm actually doing is comparing: - mutative architecture (Spring) which as single method handling the request. It grows in complexity as changes are added - additive architecture (OfficeFloor) which does function injec
5.
by sagenschneider 19d ago
Keeping all the specifications and user discussion does create more context, which is useful for AI. However, I'd bring in Brooks discussion on essential and accidental complexity. In other words, there being No Silver Bullet https:&#
6.
by sagenschneider 19d ago
Yes, you are right that looking at one commit doesn't tell you much. It's looking at the nature of on going changes. A single complex file written once and never touched is likely a good cohesive file about a single problem solved
7.
by sagenschneider 19d ago
Most static code analysis looks for bugs or just too complex functions. The novelty of Change Impact is it looks at the context of the complexity. Adding complexity to something already complex should be flagged for review. I've not c
8.
by sagenschneider 19d ago
Yes, the formula does make some approximations. The problem with cohesion is understanding what is "single purpose". Nothing can determine this without interpreting the code and making a judgement call on whether it needs to be r
9.
by sagenschneider 19d ago
It uses lizard for parsing, so Python, Java, JavaScript, TypeScript, C, C#, Go, Scala, and more.
10.
by sagenschneider 19d ago
Yep, agree on annoying developers. So just to cover usability it can run in warn and block mode to address this. Though to the bigger point of your comment, yes SDLC are becoming faster. We can churn out code at a ridiculous rate. Howeve
11.
by sagenschneider 19d ago
Yep, this all actually started because of experimenting with my own open source project https://officefloor.net (giving full disclosure) I was testing the additive pipeline style of OfficeFloor against the mutative handler style
12.
by sagenschneider 19d ago
I'm not looking at building prototypes. Looking at ways to manage code bases after they've gone through hundreds if not thousands of changes.
13.
by sagenschneider 19d ago
Comes from the basic Computer Science principals of High Cohesion and Low Coupling. High cohesion means the functionality of a component are closely related and focused on performing a single well defined task. Basically single classes for
14.
by sagenschneider 19d ago
When you think about a god class or god method, it occurs over time by adding more than a single responsibility. Yes, there are generally complex algorithms but they usually are not things developers write (imported from libraries). What is
15.
by sagenschneider 19d ago
Probably because I've had Quality Gates in my pipelines for so long :)
16.
by sagenschneider 19d ago
The difference to previous CC use, is the the change impact formula looks at the complexity already in the class/file. Typical CC just looks at the function it is change and not the context of the change. The Change Impact formula inco
17.
by sagenschneider 19d ago
Yes, I've run it against a bunch of open source projects with long histories (before AI) to see if it predicts bugs. Seems file size is still a better predictor. However, for the projects where good coding was strictly adhered to and
18.
by sagenschneider 19d ago
Yes, I'm doing my own research on AI augmented pipelines https://blog.officefloor.net . I actually found most code quality tools look for bugs and complexity, but nothing much about cohesive erosion. The nice thing about
19.
by sagenschneider 19d ago
How the change impact formula works: https://blog.officefloor.net/2026/08/measuring-blast-radius-...
20.
by sagenschneider 19d ago
It is called Impact"Gate" https://github.com/marketplace/actions/impact-gate
21.
ImpactGate: A merge gate that scores the structural decay AI adds(github.com)
34 points by sagenschneider 19d ago|41 comments
22.
Layers Are the Symptom of Methods(blog.officefloor.net)
1 points by sagenschneider 3mo ago|0 comments
23.
by sagenschneider 3mo ago
Agreed. AGENTS.md and skills are the documentation level from the linked post that hands AI the context its training lacks. However, this only works if you know a better architecture exists. Most won't and they'll use the "
24.
by sagenschneider 3mo ago
And it's this output of humans that we are further training AI on. Will this progress things, or will it just keep us regurgitating 2020 code patterns?
25.
by sagenschneider 3mo ago
And how many projects are actually doing this? And if they are, how many are keeping this up to date?
26.
Will AI keep us stuck in 2020 architectures?(sagenschneider.blogspot.com)
3 points by sagenschneider 3mo ago|6 comments