SShortSingh.
Back to feed

Day 3: I stopped hand-rolling mock JSON and unblocked three teams

0
·2 views

Every frontend team has the same folder. src/mocks/, fixtures/, stubs/ — a pile of JSON files someone wrote during the last backend delay, lovingly shaped to make the demo look good. They have exactly two properties in common: they do not match the real API, and deleting them feels dangerous. Day 3 of the the series is about replacing that folder with a mock server generated from the OpenAPI spec we wrote on Day 2. The distinction that matters: a mock should answer the contract, not whatever shape made the component render.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Using Third-Party Models as Subagents Alongside Claude in Claude Code

Too few tokens, too many spare quotas I do most of my development on a Claude Code subscription. Right now Claude Fable 5.1 and Opus 5.5 work extremely well, and I would simply call them the state of the art. The only problem is that I keep running out of tokens. At the same time, I have quota for other models lying around. I got some free quota for Xiaomi's MiMo a while ago, cheap deals for other Chinese models show up from time to time, and a friend handed me a GLM subscription they no longer use.

0
ProgrammingDEV Community ·

Three AI judges, one dirty sink

This is a submission for the Hacktoberfest Weekend Challenge: Build for a Friend I built this for my flatmates. The arguments in our flat are never about anything big. Dishes sitting in the sink. Someone's milk or snacks disappearing. Whose turn it is to clean, how late is too late to be loud, and a guest who stays one night longer than anyone agreed to.

0
ProgrammingDEV Community ·

How to turn an OpenAPI spec into an MCP server (2026 step-by-step)

Every team evaluating Model Context Protocol (MCP) servers reaches the same question: do we hand-maintain a second description of our API for agents, or do we generate it from the contract we already have? If you keep an OpenAPI document, the second answer is the sane one. An OpenAPI spec is almost literally a tool catalog already — each operation has a name, inputs, outputs, and a transport. Converting it to MCP is a mapping problem, not a modeling problem. This walkthrough covers what the mapping actually is, where generic converters fail on real specs, and how to verify the result with a re

0
ProgrammingDEV Community ·

Building Dice Atelier: a 3D dice roller with 20 themed tables, built by two AIs and one director

Two days ago our little free-tools site had a perfectly good dice roller. Then it got an upgrade with delusions of grandeur. Dice Atelier is a 3D dice roller for D&D night: twenty themed tables — an astral observatory, a clockwork library, a neon ronin bar — each with dice styled to match. Mixed pools, dice notation (try 4d6+2), advantage and disadvantage, up to 100 dice at once. It's free, no sign-up: https://penguinwearingahat.com/tools/dice-atelier/ No human wrote the app.