- G Guild Community-driven conversation among people that share the same goals and struggles in a judgement free environment.
- A AI What the group is about, and the tool we point at the code in the room.
- T Training Topics of conversation driven by the people in the guild to help bring clarity and consistency in building your app.
- H Help Bring a live problem from your own codebase and leave with it untangled.
- E Engineering Why the code is shaped the way it is, and what that shape costs to change.
- R Roundtable Everyone's questions on one table; where a session goes depends on what the room is stuck on.
How a session runs
led live, on the applications in the room- Architecture: writing code in repeatable shapes, so the AI has a worked example to follow and its output lands more consistently.
- Organization: laying out the project on disk so the code stays organized: every file where you would look for it, and where the next one goes.
- Getting more out of AI: learning to talk in modules: one self-contained piece of a feature at a time, small enough to describe and easy to check.
- An eye on cost: what a decision saves in time, set against what it adds to the bill.
Slides
Application Building Slides
The deck from our first session, on how an application gets built: generating ideas and curating them down to the ones worth building, prototyping, then the parts an application is made of and how project organization gives each of those parts a home on disk.
Application Building SlidesWorkshop Walkthroughs
1. Pattern Organization
Where each piece of an n-tier application lives: the six sibling folders (webhost, logic, data, adapter, shared, initializer) and what each one is allowed to know about.
Pattern Organization2. Project Organization Per Project Type
The same solution folder, then how a project is laid out on disk in four more places: the Angular workspace, the React app, the iOS app, and the Android app.
Project Organization3. Stepping through a call to a server
How front-end code talks to a server: one call, followed through its whole asynchronous life cycle. The request goes out, the promise stays pending while the page carries on working, and the reply or the failure settles it. A bad status still counts as an answer, a dropped connection does not, and the same life cycle runs whether the code uses callbacks or await.
Server Call Walkthrough