AI Software Engineer

• Key points are in the visual diagram above.

This capstone proves you can build the same plan→code→test→review loop used by Cursor, Devin, and internal codegen bots — not a chatbot that pastes code snippets.

A junior engineer with terminal access and a PR template — you remain the tech lead who approves the plan and merges.

Scenario

Issue: 'Add rate limiting to POST /login.' Planner identifies auth middleware and tests. Coder adds token-bucket decorator. Sandbox runs 47 tests — 1 fails. Debugger fixes off-by-one in window size. Reviewer opens PR #142 with benchmark table showing 429 responses after 10 req/min.

Solution

In Capstone Projects, apply AI Software Engineer to this scenario: Issue: 'Add rate limiting to POST /login. Identify the inputs, run the technique, validate the output, and note one thing you would monitor in production.

Do this before moving to the next module — reading alone is not enough.

Open the Code Walkthrough below and run it locally. Change one parameter related to AI Software Engineer (e.g. model, temperature, top_k, or tool name), observe the difference in output, and write 2–3 sentences explaining what changed.

Highlighted lines show where AI Software Engineer happens in the code.

1# LangGraph-style state (simplified)2class AgentState(TypedDict):  # define a data structure or component3    task: str4    plan: list[str]5    patches: list[str]6    test_log: str7    attempts: int8
9def coder_node(state):  # define a reusable function10  patch = llm.invoke(f"Task: {state['task']}\nPlan step: {state['plan'][0]}")11  result = sandbox.apply_and_test(patch)12  return {"patches": [patch], "test_log": result.log, "attempts": state["attempts"] + 1}  # return the result

• Letting the agent edit files without running tests
• Sending entire repo in every prompt instead of retrieval
• No human gate before merge to main

Quick recap — the most important points from this module.