Technology

Engineers know when a codebase needs a fundamental overhaul. The hard part isn't identifying the problem — it's convincing a VP of Product, CTO, or CFO who has seen too many rewrites turn into multi-year sinkholes. This devil's advocate prompt plays a skeptical but fair business stakeholder and presses your proposal through the five objections every business leader will raise. By the end, you'll have a tighter argument and a structured one-page case you can actually use.

A rubber-stamp LGTM helps no one. A wall of unranked nits demoralizes junior engineers and clogs review queues. Good code review is a skill — one most engineers are never explicitly taught. This format-aware prompt adapts to your situation (senior reviewing junior, junior reviewing senior, or peer review) and helps you write comments that are specific, actionable, and calibrated to what actually needs to change — without crushing confidence or burning hours on things that don't matter.

Most engineers spend the week before a promotion cycle scrambling to remember what they shipped six months ago. The ones who get promoted built the case continuously — a narrative at the next level, evidence mapped to a rubric, and a speech their manager can give when they're not in the room. This iterative coaching prompt walks you through building that document now, when it can still change what you do, not just how you describe it.

Systematically compare and evaluate AI models (GPT-5.4, Claude Opus 4.5, Gemini 3.1, etc.) on your specific use case with structured head-to-head testing and scoring.

Create a comprehensive personal and family defense plan against AI voice cloning scams, vishing attacks, and social engineering that exploits synthetic media.