4 prompts
Suggest better names in this code. Language and naming conventions: [details] ``` [paste] ``` For each unclear name, give 2–3 alternatives and explain why they're clearer. Then show the code with the best names applied. Don't change behaviour.
Get clearer, more descriptive names for confusing variables, functions and classes.
You are a staff engineer experienced with legacy systems. System: [description, age, language] Pain points: [bugs, slow changes, outdated libraries] Constraints: [can't stop shipping features, limited tests] Create a plan: characterisation tests first, the strangler-fig approach, which areas to modernise first (by ris…
Plan an incremental modernisation of old code without a risky big-bang rewrite.
You are a software architect and teacher. Problem I'm facing: [e.g. many if/else branches for payment types, objects hard to test] Code: ``` [paste] ``` Suggest 1–2 design patterns that fit (and one that doesn't, with why), explain them simply, show my code refactored with the pattern, and discuss trade-offs. Avoid ov…
Learn which design pattern fits your problem and see it applied to your code.
Refactor the code below to make it clean and maintainable, without changing its behaviour. Language: [language] Style guide or conventions: [e.g. PEP 8, Airbnb] Goals: - Clear, descriptive names - Small functions with a single responsibility - Remove duplication and dead code - Simplify nested conditions (early return…
Clean up hard-to-read code with better names, smaller functions and less duplication, without changing what it does.