The twenty problems
Every full-stack project runs into the same two lists, and they belong to different people. Twelve cost the developer the first two weeks. Eight decide whether the client signs at all, and they are asked before anybody mentions a feature.
Each one here says what actually goes wrong, what Grit does about it, the commands, and what it does not do. They are the backbone of the talk.
What it costs the developer
D1The copy-paste startYou open the last project and start pasting.D2Wiring the monorepoA Go API beside Next.js. Or beside Expo.D3Types written four timesOne invoice. Four descriptions of it.D4The same UI for every tableCRUD hell.D5Testing performanceEvery tool needs a day before it tells you anything.D6No window into the dataCan I just look at my data?D7The undocumented APIWhat does this endpoint return?D8Import and exportCan we upload a spreadsheet?D9No data to build againstYou test on ten rows. The client has fifty thousand.D10Migrations with no way backA schema change on production, with no way back.D11The frontend nobody wantsYou are fluent in Go. Then you open the React project.D12Paying a model to write itAsking a model to write it is not free.
What the client asks
B1Can different people see different things?“Can different people see different things?”B2What happens if we get hacked?“What happens if we get hacked?”B3Does it work without internet?“Does it work without internet?”B4How will we know when it breaks?“How will we know when it breaks?”B5Is any of this backed up?“Is any of this backed up?”B6What if it gets busy?“What if it gets busy?”B7Who changed this?“Who changed this?”B8Can it take a ten megabyte photo?“Our staff photograph things on their phones.”