Papare AcademyWe ran a real coding bootcamp before we built the platform for it.
Evidence from past work, not proof of the current product
This case applies to the engagement and period it describes. It does not prove outcomes of the microcourses, training, workshops, qualification or human evaluation that betaPlan offers today.
- Registrations
- 500+
- First-cohort students
- 231
- Sprints, HTML to Next.js
- 12
- Unique learners
- 247
- Completed all 12 sprints
- 8
How it worked in practice
Run by hand, on Classroom and spreadsheets.
Before betaPlan was a product, it was a problem we had ourselves. Papare Academy was a real bootcamp: 12 sprints, from HTML and CSS to JavaScript, React and Next.js, taught live on Zoom and Google Classroom by a team of volunteer mentors.
The interest was immediate. The registration form drew more than 500 responses, and 231 students filled the very first cohort. But every sprint had its own Google Classroom, its own roster and its own pile of assignments to grade. Attendance, progress, project links and mentor notes were spread across half a dozen spreadsheets that we updated by hand, week after week.
Coordinating 231 learners that way meant asking the same questions over and over. Who is in which room, who submitted, who still needs access to the next classroom, who is quietly falling behind. The very tools that let us launch fast soon became the thing slowing us down.
The course is good, but the structure can get complicated. There are several groups, and since it was my first online course, it was easy to lose track of which room to join.
The selection funnel
Every step down is the filter working.
In a free, self-paced online cohort, attrition is expected, and we treat it as a signal. The people who stayed had shipped real, working software, sprint after sprint, to deadline and under review.
Registered
Raised their hand
Started sprint one
First live cohort
Reached the React sprints
Still shipping weekly
Completed all 12 sprints
Saw the work through to the end
Learners’ work
Real applications, built by learners who came through selection.
A working React application built during the programme. Tasks can be created, marked complete, edited and deleted, and the app’s state is handled cleanly. All identifying details have been removed.
The outcome
What it proved.
The 8 who completed all 12 sprints had shipped real, working software to deadline and under review, sprint after sprint. That is not a certificate of attendance. It is a record of what each person built, unaided.
Papare Academy shows a method from our past: sustained work, deadlines and recorded deliverables gave stronger evidence than attendance alone. Applying that lesson to another profession still takes the professional rules in force, human assessment and authorised evidence.
Overall it has been a very positive experience. It is genuinely helping me improve my coding skills.
What this past record shows.
It shows betaPlan’s experience in running sustained learning and keeping evidence of the work. It does not show that a group of professionals is ready for work today, and it does not prove current human-evaluation results.