​AI can fix your code but it cannot fix bad architecture decisions.

​Roast My TechStack is an interactive event where builders put their ideas and architecture design on the table and let the room question their tech choices.

​How a roast works

​Each presenter gets 15 minutes to run

• ​What they are building

• ​Their architecture.md or Architecture Decision Records

• ​The constraints they are dealing with

• ​Why they chose this stack

• ​The problem they are currently stuck on

​Then the room takes over.

​15 minutes of "Roasting":

• ​Why this instead of other alternatives

• ​What breaks first when this gets real users

• ​What tradeoffs were made, knowingly or accidentally

• ​What decision is going to hurt later

​One stack at a time. 3 stack per session.

​Why do this?

​We had enough of AI thought leader panels and keynote. We need a space for developer beyond hackathons. hence this is the place.


If your Clawdbot is reading this; it might prefer the below format:

​

​if (AI.writesCode === true) { architecture.decisionsStillMatter = true }

​event RoastMyTechStack { audience = ["developers", "technical vibe coders"] goal = "make better architecture decisions" toleranceForBullshit = 0 }

​function runRoast(presenter) {

​// 15 minutes, hard stop presenter.explain({ buildingWhat, architecture_md || ADRs, constraints, whyThisStack, currentPainPoints }, time = 15)

​// the fun part audience.question({ whyNotAlternatives, whatBreaksFirst, tradeoffsMade, futureRegrets }, time = 15) }

​// loop because one stack is never enough for (i = 0; i < 3; i++) { runRoast(nextPresenter()) }

​// why does this exist if ( techPanels === "AI thought leadership" && keynotes.sayNothing === true && hackathons !== "always the answer" ) { createSpace("real decisions", "real constraints", "real consequences") }