A twelve-week cohort programme
You can make it work.Can you say why?
ByteHatch is for engineers whose code runs and whose explanations run out. Six people, one instructor, one session at a time. The next session opens when you have finished the one before it — and not on a schedule, because a calendar cannot tell whether you understood something.
Six seats · applications close 28 September
This is how every session opens
> [1, 2, 10].sort()What does this return?
You see one session
Not a playlist. Not a catalogue. Not next week. The sessions ahead of you exist, and you can see that they exist, and that is all you get until you arrive at them.
Your instructor releases each one by hand. Nothing unlocks on a timer, because a timer does not know whether the cohort is ready.
- 01Reading a stack trace properlyDone
- 02Why your code is slowDone
- 03Mutation, aliasing and the heapOpen
- 04Locked
- 05Locked
- 06Locked
- 07Locked
- 08Locked
One session, four moves
- Move 1
Predict
Call what the code does, and say why, before you read a word of the session.
- Move 2
Read
The written session and its recording. At your pace, on your evening.
- Move 3
Meet
One live hour, spent on the misconception your cohort actually shares.
- Move 4
Next
The following session opens once you mark this one done. Not before.
Apply if
- You ship features that work and cannot always say why they work.
- You have been writing code for a year or three and can feel the plateau.
- You want to be argued with by someone who has read your reasoning.
Do not apply if
- You want your first engineering job in six weeks.
- You want a certificate at the end of it.
- You want to watch the recordings at double speed and skip ahead.
Tell us where you are stuck. That is the whole application.
No CV, no take-home, no assessment. Write a paragraph about something you shipped that worked for reasons you could not fully explain. That paragraph tells us more than a résumé does.
Apply for cohort 02