Build-in-public writing from Janaka and Tiran. What we’re building with spec2web, how we approach product development, and our takes on AI, consulting, and the new SDLC — written when it happens, not after.
We started building in public before we launched. Posts from before May 2026 are from our pre-launch period — written as things happened during the build of specshop.dev and spec2web.
What AI actually changes about every stage of software development — and why the phase everyone ignores is now the most important one.
The traditional PM role is being automated — not by a pink slip, but a promotion nobody asked for. What spec-first AI development means for the coordination layer of software.
The MVP was always a workaround for expensive software. Vibe coding eliminated that excuse. Why spec-first development is the only rational model for 2026 and beyond.
How we turned a 2,500-word Sri Lankan tax spec into a landing page, interactive tax wizard, knowledge base, and Chrome extension concept in three days — ready to test with CA firms.
AI solved the build. Nobody solved the morning after. How one client conversation exposed the gap spec2web was built to fill.
How we spec’d and prototyped Punchclock — a roster, time-tracking, and biometric attendance platform built for operations managers who still rely on spreadsheets and paper timesheets.
How we built Gelukkig — an ethical reputation management platform for Dutch hospitality that catches unhappy guests before they post negative reviews, and invites every guest to leave one.
AI teams are debugging orchestration, swapping models, tuning prompts. Almost nobody is asking whether the artifact was designed to be read by a distributed system of processors.
What AI actually changes about every stage of software development — and why the phase everyone ignores is now the most important one.
I burned $90,000 on dev once. Here’s the ratio I wish I’d known: 60% distribution, 40% build. And why that gap is widening in 2026.
How we designed and shipped a spec-first CRM + field service workflow for a mid-market HVAC company in three weeks — including a browser-based field app for technicians.
14 screens. 295 staff. Zero ambiguity. How we wrote a full UX specification for an enterprise healthcare Time & Attendance platform — and turned it into an interactive prototype before writing production code.
I dismissed SAFe for a small studio in 2020. Then we added AI agents and the coordination surface exploded. Here is what changed.
AI didn’t create spec-driven development. It just made ignoring it unaffordable. How the industry caught up to what we built in 2022.
How structured artifacts living in Git are becoming the operating layer of AI-native software — and why there’s no single right way to do it yet.
No posts in this category yet. Check back soon.