How we teach.
Our curriculum is empirical, built from years of real workshops and client work. Learners join a team, build a real product, and grow into capable engineers by doing the work, with feedback at every step.
The learning model
Learn by building, from the first week
From the first week, learners build real software in a team and ship it together. There are no isolated tutorials. Each cohort takes one real product from first principles to a deployed application, and learns the discipline by carrying it.
We teach the disciplines professionals use, test driven development without mocks, pairing, version control, continuous delivery and real time web development, on our own open source tools, Ekolite and Ekoflow, which run on modest hardware.
How the work is checked
Engineering is a discipline of checking
Learners work on real repositories where every claim the code makes is verified before it ships. A pipeline runs the tests, the types, the linting and the documents generated from the tests, and it declines to deploy anything it cannot verify.
The same standard applies to us. Our pipeline is public, and so are the occasions it caught us: a document that had quietly gone stale, a check that found a problem and had no way to stop the build. We publish what we found and what we changed, and it becomes part of the curriculum.
Learners see the discipline practised on real work, including ours, and carry it into whatever they build next.
From first principles to a shipped product
A cohort moves through three phases, on real work the whole way.
Foundations
The tools and disciplines of professional engineering: the editor and terminal, version control, test driven development and pairing, practised on small real problems.
Build and ship
The team builds one real product for a community partner and deploys it, on Ekolite and open platforms like CiviCRM, with real users and real feedback.
Reflect and measure
A companion app turns each learner's real engineering activity into reflective metrics, so growth is visible and progress is owned by the learner.
Participatory, learner centred, grounded in real work
Our method is participatory and learner centred. Learners are active makers of their own knowledge, not passive recipients of content, and the curriculum is built around what they do rather than what they are told.
Learners pose and frame real problems, build in pairs, and reflect in structured cycles. Knowledge is constructed between people, through pairing, code review and honest peer feedback. It draws on project based, learner centred traditions, for example Freire and Dewey, delivered as concrete practice in coding dojos.
Understanding and action stay together. Engineers who understand the systems they build, technically and in context, gain the confidence and agency to shape their own communities.