About
Se wo were fi na wosankofa a yenkyi.
"It is not wrong to go back for that which you have forgotten.", the Akan proverb behind the Sankofa symbol, and behind everything this platform is.
Why Sankofa
The Sankofa bird flies forward while looking back, carrying an egg, the future, in its beak. It teaches that progress does not require abandoning where you come from. Here, your history, your language, your neighborhood, and your people are not obstacles to a tech career. They are the curriculum.
"Sankofa" is an Akan word from the people of Ghana, and it translates literally as "go back and fetch it." The principle is that returning to your origins for wisdom is not taboo, and that once retrieved, that wisdom is used to move forward.
The name and the symbols
The visual identity of this site is built from original renditions of Adinkra symbols, which the Akan have used for centuries. In the early 2000s the theoretical physicist Sylvester James Gates identified a class of graphs describing the algebraic structure of supersymmetry and named them "adinkras" for their resemblance to those Ghanaian symbols. Those graphs are error-correcting codes, part of the same mathematical family that underlies modern computing. Naming this school Sankofa Code acknowledges that lineage, reaching back into the visual traditions of the Akan and carrying them forward into the tools we build now.
Why this platform exists
Universal access to education is a non-negotiable requirement of a just society, and that applies to software engineering as much as to anything else. A $15,000 bootcamp is a locked door for most of the communities we serve, and that price puts a career in tech out of reach for a large part of the global population. In America the effect is not evenly distributed. Systemic economic underfunding blocks Black youth, Black adults entering the workforce, and Black mid-career professionals from moving into technology at every stage. The desire is there across generations. The capital is not, and that is a consequence of an economic system that treats knowledge as a commodity, not a statement about aptitude.
Sankofa Code opens that door permanently: 14 courses and 172 modules across 4 stages, then capstone project briefs, with a live code editor, practice tests, real projects, 11 reference guides, and certificates. Free of charge, forever, with no ads, no upsells, and no pop-ups. A supportive digital library and classroom, not a sales funnel.
The problem is generational as well as economic. "Each one teach one" has been a practical necessity in communities underserved by formal institutions for as long as there have been institutions. Once one person acquires a skill, they can transfer it to the next, and that horizontal transmission bypasses the credentialed gatekeepers and sustains itself. This platform is built to be handed down that way.
Built for Black learners, specifically
Every example is culturally grounded on purpose. You'll compute revenue for a Black-owned bookstore, analyze data about writers and musicians who changed the world, and create variables for your ancestral village. Representation isn't decoration here, research and lived experience both say learners go further when they can see themselves in the material.
How the course teaches
People learn to code through active execution. Passive consumption of video lectures and reading about syntax will not produce a programmer, and the goal is to move past following a tutorial to the point where you can go from an idea to a working program with no scaffolding.
Every concept moves through the same layers before it is yours: concept, explanation, worked example, predict and run, practice, assessment, then a piece of the project you keep. You meet each idea several times in different forms until it is genuinely yours. The editor runs in every lesson from minute one, against the real thing: real JavaScript, real Python, real SQLite, the real TypeScript compiler, real React. You learn to code by coding.
What the curriculum covers
It starts with structure and logic: HTML and CSS, then programming taught in Python and JavaScript side by side, the command line, and Git. Then real engineering: React, Django, APIs and public datasets, SQL, and TypeScript. Then the practices that separate somebody who can build a thing from somebody a team can hire: PostgreSQL and data modeling, testing and test-driven development, authentication and security, and how work is actually planned, reviewed and shipped. It ends with a full stack application that is yours.
Graded on what you built, not how you wrote it
Work is checked by running it. Your page is inspected as it renders, your query against a real database engine, your component by clicking it, your types by the actual compiler. There is more than one correct answer to almost every task, and hidden checks run against data you cannot see, so an answer typed in rather than worked out does not pass. When something fails, the feedback names the requirement rather than showing a diff.
For homes and classrooms
Sankofa Code serves self-directed learners and structured classrooms alike. Teachers create cohorts, assign modules, track mastery, and add private notes for their classes. Everything runs in the browser, no installs, and the reference cheat sheet prints for students without consistent device access. Community organizations, after-school programs, and independent groups can use every part of this platform free of charge and without asking permission.
In more languages
English is not universally accessible across the diaspora, and a language barrier keeps people out of this work as effectively as a tuition bill does. Swahili, Amharic, Arabic, French, Spanish, and Brazilian Portuguese are the first six, starting with the foundational levels. Learning to write code is hard enough without doing it in a second language, and a student who reads an explanation in their own language spends that effort on the concept instead of the translation.
More languages will follow, and that part depends on the community. If your language isn't on the list and you want it there, reach out. I need native speakers who understand software to check that the technical terms survive translation, and anyone willing to do that work can help open the curriculum to a community I can't reach on my own.
Who built this
My name is Saipher Zureti. I've been writing code for several years, almost entirely self-taught, and I've built multiple applications and websites by working through the cycle every engineer works through: something breaks and I diagnose it, I write bad code and I fix it, I hit a concept I don't understand and I read and keep trying until I can use it in something I'm building. When I looked at existing bootcamps, both to consider enrolling and to see what was being offered to my community, I kept arriving at the same reaction. If I were teaching this, I would structure it differently.
I'm also an artist, and that shapes how I approach programming. I sketch interfaces and structural diagrams before writing anything, because the creative impulse in art and the creative impulse in software are the same one. What drew me to code was autonomy, the ability to turn what I could visualize into a working product without paying a developer to do it for me. That autonomy matters most for Black creators and entrepreneurs who have the ideas and the talent but not the capital to hire out the technical work. If the only barrier between us and our own products is a body of knowledge, the answer is to spread that knowledge as widely as possible.
This started as a master cheat sheet for JavaScript and Python syntax, then Git, GitHub, HTML and CSS. A cheat sheet is a memory aid, not a course, and building the guided progression, the exercises, and the assessments is what turned that reference material into this. I did not build it to generate revenue. I built it to close a gap that should not exist, and because writing a course forces a kind of articulation that private practice does not, which keeps me accountable to the depth of my own knowledge. This is the beginning of a much larger project, and I plan to keep adding to it for as long as I am able.
Contact
Questions, corrections, an accessibility barrier you ran into, or something in a lesson that is plainly wrong. Every message gets a personal reply, because there is one person here.
Found a mistake in a lesson? Say which course, module and lesson, and what you expected instead. Content errors are treated as bugs and fixed quickly.
Hit an accessibility barrier? Tell us what got in your way. Those go to the front of the queue, and the accessibility page states what already works and what does not.
Want to translate it? Say which language you speak and what you build with. Technical background matters more than fluency alone.
Teaching with it? Partnership and cohort questions are answered on the For Schools page.