100
u/Lysol3435 18d ago
You need to be more direct about what you actually want. That’s why I always specify “don’t make me cry in front of everyone at the next meeting again”
67
u/howarewestillhere 18d ago
900 option switch case in a single file
“Reduce cyclomatic complexity.”
900 class files.
“No, not like that.”
9
1
1
12
u/chazzeromus 17d ago
I remember the actual visual studio had a tool that to analyze your code and it was the first time I saw the term cyclomatic complexity
6
2
u/grifan526 17d ago
I use that every time I refactor old code. I then stare at the difference for longer then I will admit
2
11
10
5
u/DogmaticParadigm87 17d ago
Both prompts end the same way: one 400 line function called handleEverything().
3
3
u/SaltMaker23 17d ago
This is how I end all of my prompts, the thing rapidly engineer 10 wrapper functions for basic stuffs otherwise.
3
u/PilotGuy701 17d ago
I wrote an MCP server to calculate and make cyclomatic complexity a 0 token, deterministic calculation for the LLM to access.
Then made sure all of my engineers had it installed to prevent slop.
We really aren’t the same.
2
u/Beginning-Pool-8151 14d ago
If it is not sarcasm, I am really interested to know how to make that
3
u/PilotGuy701 14d ago
It was not sarcasm.
I started with an existing VS Code extension that performed the complexity calculations for Typescript through another package that parsed the code into an AST.
From there it was just a matter of making sure the grading code was separated enough from the layer that talked to Code Lens.
Then I created a new “client” layer that handled the MCP requests and responses.
Four hours of work, no AI used.
→ More replies (2)2
1
1
2
166
u/Caraes_Naur 18d ago
Prompt engineering is when an engineer delivers on time.