Skip to content

foundersandcoders/aie-workshop-friction-driven-development

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Friction-Driven Development

Building Personalised AI Toolchains

TL;DR

Teach developers to build tools that actually match how they work

This three-hour intensive transforms AI coding assistants from glorified autocomplete into personalised workflow automation by:

  • teaching systematic friction analysis
  • strategic tool construction
  • the economic trade-offs that separate sustainable solutions from expensive theatre

Participants leave with working custom tools they built themselves and the confidence to keep iterating. The developers who can shape AI to their needs will outpace those still fighting their tools.


What's This About?

Most developers suffer through workflow friction that compounds daily: the three-click task that should be one, the command they Google every week, the context-switching that murders their flow state. This workshop teaches you to stop suffering and start building. You'll learn to systematically identify your specific pain points, evaluate the true cost of both the friction and the solution, and construct custom AI-powered tools that work the way your brain actually works—not how someone else's best practice assumes it should.

Over three hours, you'll move from theory to implementation fast. You'll start by auditing your own workflow to pinpoint exactly where you're losing time and sanity. Then you'll dive into the Claude Code ecosystem—slash commands, skills, agents, and MCP servers—learning not just how they work but when to use each one and what they actually cost in tokens and money. The second half is pure building: first creating your own tool targeting your biggest friction point, then collaborating with others to build something useful for the group while learning from their completely different approaches to the same problems.

You'll leave with four concrete outputs: a documented map of your workflow friction points, a working custom tool you built yourself, a personal strategy for managing AI context budgets, and a collaboratively-built tool you helped architect. More importantly, you'll have the confidence and technical foundation to keep building as new friction emerges, and a peer network of people doing the same. No more accepting workflow pain as inevitable—you'll have the skills to fix it.


About

Teach developers to build tools that actually match how they work.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published