This is the second article in a series that tries to put a number on the value of Plinth's AI-native development workflow for Java. The Part 1 article showed the benchmark results across 4 scenarios:
ScenarioWhat the agent gets
scenario1A minimal README only — baseline, sparsest possible brief
scenario2A full functional-requirements package: user story, Gherkin, OpenAPI, ADRs
scenario3An OpenSp...
[Read More]
Validating hypotheses about Plinth workflow with a Benchmark Part 1
The questions behind the benchmark
During the last months, the project has evolved from a complete Skills folder for Java to provide an AI-native development workflow for Java, more or less this project lives in the Third generation (Systemp prompts -> Skills -> AI-Native development Workflow). During this time, any inquisitive user could ask for evidences about what is the real value using t...
[Read More]
Beyond Traditional Profiling: Mastering JFR for Modern Java Applications
Discovering JFR: A Journey into Modern Java Profiling Excellence
Symptom: memory usage drifts under real production load. Constraint: profiling cannot degrade latency or throughput. Solution: Java Flight Recorder (JFR) — the built‑in, low‑overhead recorder that captures CPU, memory, GC, I/O, and custom events from live systems with typically under 2% impact.
With JFR, production evidence replaces g...
[Read More]