

Unfortunately for me it’s a kpi so I need to figure out how to do something useful with it.
LLM is good for
- temporary scripts like to export data
- boilerplate for new code
- simple or repetitious code like unit tests
But just in time for my performance review, I spent a week ignoring my work to set and tweak rule sets. Now it can be noticeably more useful
- set context so it understands your code better. No more stupid results like switching languages, making up a new test framework, or randomly use a different mocking tool
- create actions. I’m very happy with a code refactoring ruleset I created. It successfully finds refactoring opportunities (matches cyclonatic complexity hotspots) and recommends approaches and is really good at presenting recommendations so I can understand and accept or reject. I tweaked it until it no longer suggests stupid crap, although I really haven’t been able to use much of the code it tries.
- establish workflow. Still in progress but a ruleset to understand how we use our ticketing system, conventions for commit messages , etc. if I can get it to the point of trusting it, it should automate some of the source control actions and work tracking actions


















There’s enough people who drink the koolaid.
I helped this one as guy use an LLM to migrate his test suite to java21. It did help him incorporate some new language features but I don’t see how it made up for my time sitting with him
…… yet to management he saved 20% time. They trust that number despite no actual measurement, and hold it up as efficiency we all need to find.
But certainly if a 20% efficiency gain were real, that would be well worth $100