[ pane 00 / benefits ]
What is different about studying here
Most AI courses teach you to use the tools. Synapsia courses teach you to understand them — which takes longer and produces something more durable.
< Back to HomeSix things that shape how the courses work
Instructors have spent years writing implementations from scratch, not just calling library functions. The Foundations course was designed by someone who built their first transformer in 2019, working through the original paper component by component.
- Practical engineering background, not academic generalisation
- Course material built from direct experience with the failure modes
- Active practitioners, not course creators who stepped away from the work
Every concept is introduced through working code, read before it is run. The repository is the primary teaching material — the slides, where they exist, are secondary.
- No black-box libraries before you understand what they wrap
- Implementations grow incrementally across the course
- Matrix shapes explained before any call to a framework
Exercise submissions and artefacts receive written responses that address the specific work submitted. Students can re-read that feedback weeks later, when a related issue comes up in a new context.
- Specific to what you submitted, not a generic rubric
- Reviewers read the code, not the description of the code
- Five artefacts reviewed line by line in the Practitioner Programme
Enrolment starts with a message, not a purchase. For the Practitioner Programme, a technical conversation precedes any commitment — either side can decline to proceed.
- You are not buying something before you know it is right for you
- Self-check exercises published for every programme
- Honest about fit, not focused on maximising sign-ups
Fees are stated in Malaysian Ringgit, without upsell tiers or add-on costs. What is listed is what you pay.
- Foundations: RM 1,290
- Deployment short course: RM 870
- Full Practitioner Programme: RM 4,650
Every repository, artefact and capstone project belongs to the student. Synapsia retains no rights over what you build during a programme.
- Repository transferred to your account at course end
- Compute credit allowance included in Practitioner Programme
- No licence restrictions on the code you wrote
→ next pane: [ 02 ] detail
The thinking behind each benefit
→ next pane: [ 03 ] comparison
How the approach differs
| Feature | Typical AI courses | Synapsia |
|---|---|---|
| Teaching method | Watch video, copy code, run notebook | ✓ Write from scratch, read before running |
| Feedback on work | Auto-graded quiz or no feedback | ✓ Written feedback on each submission |
| Prerequisite honesty | "Suitable for beginners" (often misleading) | ✓ Self-check exercise published before enrolment |
| Workload stated | Vague ("go at your own pace") | ✓ Hours per week and total weeks listed plainly |
| Session format | Pre-recorded, no live interaction | ✓ Live sessions with recordings available |
| Outcome claims | Job-ready, salary increase, career change | ✓ Syllabus and workload described; no employment claims |
| Repository ownership | Platform retains access or IP | ✓ Repository transferred to student at course end |
| Fee transparency | Upsells, add-ons, tiered access | ✓ Fixed fee covers all listed inclusions |
| Cohort size | Hundreds to thousands per cohort | ✓ Small cohorts, direct instructor access |
→ next pane: [ 04 ] differentiators
Three things that are harder to find elsewhere
// what each course explicitly does not cover
Every Synapsia course publishes a "scope: excluded" section alongside the syllabus. This tells you what the course deliberately leaves out and why. Students who want to know before they start whether a particular topic is covered get a clear answer, not a vague "advanced topics are covered."
// designed to be honestly failed
The self-check exercise for each programme is not a formality. It is written so that a developer who is not ready will work through it and notice where they get stuck. That is useful information to have before paying a fee and committing to six weeks of evenings.
// hours per week, stated as a chart
The Practitioner Programme syllabus includes a monospace bar chart of hours per week, broken down by activity type. This is not the most polished visual design, but it is the most honest one. You can look at it and decide whether those hours are available in your schedule before you start.
→ next pane: [ 05 ] milestones
Where the school is now
12
cohorts completed since 2023
180+
developers through at least one programme
260+
artefacts reviewed line by line
34
capstone projects reviewed and defended
Featured in MDEC's 2024 directory of technical upskilling providers for Malaysia's digital sector workforce.
Selected for HRDC's list of approved training providers, making fees claimable under the HRD Corp levy for eligible Malaysian employers.
Invited to present the Foundations course structure at PyCon APAC 2024 as a case study in technical AI education.
// aggregate from end-of-course surveys, June–July 2025
[ prompt ]
See if one of the programmes is a reasonable fit
Send us a message telling us where you are technically and which course interests you. We will respond with a straight answer.