Threat modelling for indie devs
STRIDE, attack trees and where most teams over-engineer.
A workshop, a Discord, a syllabus and a network — wired together so curious learners become shipping engineers in months, not years.
Every contribution flows directly into Pakistan's next generation of engineers — scholarships, regional meetups, and the servers we run so nobody is locked out.
Every Rs. you send is publicly logged in our quarterly transparency report.
Manual transfer via JazzCash / Easypaisa / Bank — no card details stored.
Three ways in. Pick whichever fits the conversation — no forms, no funnels, no sales team.
The Discord gave me a place to ask the questions I was too embarrassed to ask at work. Six months later I shipped my first prod feature.
Career clinic mocks got my offer up by 22%. The reviewers were brutal in the best way.
I came for the AI track and stayed for the cybersec community.
Office hours pulled me out of two dead ends in the same week. Real engineers, no fluff.
The Discord gave me a place to ask the questions I was too embarrassed to ask at work. Six months later I shipped my first prod feature.
Career clinic mocks got my offer up by 22%. The reviewers were brutal in the best way.
I came for the AI track and stayed for the cybersec community.
Office hours pulled me out of two dead ends in the same week. Real engineers, no fluff.
I walked in not knowing how to push a branch. A year later I am leading our infra team.
No one made me feel slow for asking. That alone changed everything about how I learn.
Office hours and the threat-modelling track saved me three sprints of dead ends.
I shipped my first OSS PR off a Saturday hack. The reviewers were kind and merciless.
I walked in not knowing how to push a branch. A year later I am leading our infra team.
No one made me feel slow for asking. That alone changed everything about how I learn.
Office hours and the threat-modelling track saved me three sprints of dead ends.
I shipped my first OSS PR off a Saturday hack. The reviewers were kind and merciless.
Three rooms open this month. No replays, no sponsors, just engineers and the work.
STRIDE, attack trees and where most teams over-engineer.
Tools, traces and evals. Ship a working agent in two hours.
Mock reviews, salary calibration and a promo doc that lands.
Swipe a card any direction — left, right, up, down — to flip to the next.
Going from "TS as a syntax tax" to using the type system to design correct software. Generics, variance, branded types, exhaustiveness.
OWASP top-ten in production. Real attacks, real fixes, real CVEs — including the kind your linter never finds.
A practitioner-led path from "I trained a regression" to a working agent loop. Six modules, three shipped artefacts, no math gatekeeping.
We started Codemo because three communities — Code Motion, Code Motivation and Code Movement — kept solving the same problem in three slightly different rooms. So we tore down the walls.
The mission is simple. Talent has no limits and money should never be the gatekeeper to a career in technology. If you can show up and do the work, we will meet you halfway with the channels, the tutorials and the people who have already walked the path.
This page is just the doorway. The community lives behind it.