VS Code Launch Configuration and Debugging Habit Review
Check how a team debugs and where time is lost.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Review debugging practice without shaming habits. Launch configurations in use: [LAUNCH_CONFIGS]. How developers debug today (print statements, debugger, logs): [DEBUG_HABITS]. A recent bug that took long to find, with a short timeline: [BUG_TIMELINE]. Walk through the example timeline and identify where a debugger or better logging would have shortened the search, with minutes saved and arithmetic: 3 hours spent against an estimated 45 minutes with a breakpoint at the right place saves 2 hours 15 minutes. Review each launch configuration for missing arguments, environment variables and pre-launch steps, reproducibility on other machines, and names that tell another developer what they do. Return a table and a 45-minute training outline covering breakpoint types, watch expressions, logpoints, reading the call stack, and a practice bug, plus configurations to add. Mark feature names [VERIFY]. Keep the tone encouraging and the training outline practical, with a practice bug the team can use. Ask me for the missing launch configurations if I did not paste them, and say what you could not judge from the timeline alone.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.