development-methodology

Tag

Cards List
#development-methodology

Principles of Anchor Engineering

Lobsters Hottest ↗ · 2026-10-17 Cached

The author introduces 'Anchor Engineering,' a software development method that encodes human design judgement into 'anchors'—guiding constraints stored in an 'Anchor Book' alongside the code—so AI coding agents can build systems faster without losing shared understanding, quality, or team coordination.

0 favorites 0 likes
#development-methodology

@timoreilly: I'm really looking forward to my conversation with my old friend Jesse Vincent tomorrow. We'll talk about Superpowers a…

X AI KOLs Following ↗ · 2026-09-15 Cached

Tim O’Reilly will host a live conversation with Jesse Vincent to discuss the 'Superpowers' agentic development methodology, its evolution, and its impact on AI-assisted development.

0 favorites 0 likes
#development-methodology

@DanKornas: AI coding plans are easy to write. Keeping them aligned with the code is the hard part. OpenSPDD is a structured prompt…

X AI KOLs Timeline ↗ · 2026-06-23 Cached

OpenSPDD is a structured prompt-driven development methodology and cross-platform CLI that turns AI coding prompts into executable design contracts using the REASONS Canvas for scope, architecture, and safeguards.

0 favorites 0 likes
#development-methodology

@vikingmute: Great workflow, now it's also my main workflow for developing new features and new ideas: Grill - let AI fiercely question every detail until clear -> Research - separately analyze difficult areas and create a research document (optional) -> PRD - gen...

X AI KOLs Timeline ↗ · 2026-06-20 Cached

VikingMute shares their main workflow for developing new features and ideas: using AI (Grill) to drill down on details, Research to analyze difficulties, generating a PRD, breaking it into independent Issues, step-by-step implementation, and finally Review. This is a supplement to Matt Pocock's seven-stage AI development method.

0 favorites 0 likes
#development-methodology

@mattpocockuk: The more I replace plans with prototypes, the better the outputs Who'd have thought that low fidelity prototypes were b…

X AI KOLs Following ↗ · 2026-05-07 Cached

Matt Pocock argues that replacing plans with low-fidelity prototypes leads to better outcomes, countering the trend of detailed specifications in software development.

0 favorites 0 likes
← Back to home

Submit Feedback