What people are
learning this week.
Ranked by live guide views over the last 30 days. Ties fall back to the newest guides.
Ship a feature with a coding agent: spec, tests first, then review the diffThe loop experienced developers describe on r/ExperiencedDevs: write the spec, plan the smallest steps, have tests written from the spec, implement, then review against the spec before anything merges.
Plan in Obsidian, build with Claude Code: the PRD-to-tasks loopHow practitioners on r/hermesagent run projects: requirements and task lists in an Obsidian vault, small tasks handed to a coding agent, every diff reviewed by a human.
Make a coding agent write the failing tests first, then implementSplit the work into separate prompts: tests only, confirm they fail for the right reason, commit, then implement without touching the tests.
Keep agent PRs small: one concern per branchA developer's setup from r/ExperiencedDevs: the agent plans a feature into small chunks, writes the approved plan to the repo, and ships one stacked PR per concern.
Review AI-written pull requests against an acceptance contractA reviewer's method from r/ExperiencedDevs: a short scope contract at the top of the PR, the diff checked against it first, no extra behavior, plus Copilot code review as a first pass.
Write complex Excel formulas with Copilot, then prove they workHow r/excel users actually use Copilot for formulas: describe each field, take the draft as a starting point, test it on awkward rows, and check every reference before filling down.
Clean a messy workbook: have Copilot flag issues, then decide yourselfUse Copilot as an auditor rather than an autopilot. Ask it to flag anything that needs manual review on its own sheet, then fix the data with Excel features you control.
Automate a recurring Excel report: deterministic Python, AI only for the fuzzy partsThe pattern practitioners recommend on r/AI_Agents and r/automation: scripts for ingest, transform and validate, an OpenAI or Claude API call only for fields that need interpretation, and a hard stop when totals don't reconcile.
Write Cursor project rules that actually load when you need themPut rules in .cursor/rules as .mdc files, set alwaysApply, globs and the description on purpose, and test that the agent picks each rule up.
Combine monthly files with Power Query, using an LLM one step at a timePoint Power Query at a folder of same-shaped files, then use ChatGPT or Copilot only to write or explain individual M steps, testing each one before adding the next.
Set up Claude Code hooks for formatting, tests and protected filesAdd PostToolUse hooks that format and test after edits, a PreToolUse hook that blocks protected files, and a notification for long runs.
Let the agent check its own UI with Playwright MCPStop pasting screenshots. Add the Playwright MCP server so the agent can open your dev server, read the page structure and compare it with what you asked for.