Participant Accounts
What People Say After Completing a Track
These are written accounts from Cold Start, Hot Work and Tempering cohorts. Not every experience is the same — they are not written to be. They represent what the tracks are actually like.
← Back to Home340+
Participants enrolled across all tracks
78%
Track completion rate
4.6/5
Average participant satisfaction
3
Years operating from Melaka
What Participants Say
Reviews from Cold Start, Hot Work and Tempering
Ahmad Fadzillah
Accounts Manager · Kuala Lumpur
I had tried two other online Python courses before Cold Start and dropped both of them around week three. The intensity table was the thing that made me try again — I could see exactly what I was committing to. Seven hours is honest. I finished the track and I can now write scripts that actually run.
Cold Start · June 2025
Noor Rasyidah
Data Analyst · Penang
Hot Work is genuinely demanding at twelve hours per week while working full-time. I want to be clear about that because I nearly quit in week nine. The code review from my tutor was what kept me going — the feedback was specific to my implementation, not generic advice. I now have four project submissions I can actually show people.
Hot Work · May 2025
Kamal Tarmizi
Operations Supervisor · Johor Bahru
I work irregular shifts and I was worried the evening schedule would not suit me. The recorded library was the answer — every session is available within a day. The cohort channel stayed active while I caught up. I completed Cold Start without missing a single exercise submission.
Cold Start · July 2025
Lim Yee Shan
Software Engineer · Selangor
The Tempering capstone gave me something I did not have before: a project I built myself from scope to deployment, with a write-up and a recorded defence I can share. My mentor was an actual working engineer. The alumni introductions after completion were specific people, not a mailing list.
Tempering · June 2025
Suriani Putri
Product Manager · Melaka
The GPU credits made a real difference. I had been hesitant to run training experiments because of cost. Having credits included meant I actually ran the experiments the architecture clinics were about, rather than just reading the slides. The four-project structure is also useful — each one builds on the previous one.
Hot Work · April 2025
Irfan Hamizan
Systems Analyst · Kuching
The technical writing workshop in Tempering was something I did not expect to find valuable. Writing about what a system does for someone who did not build it is a different skill from building the system. I used the report format immediately in my current role when documenting an internal tool.
Tempering · May 2025
Case Studies
Two Participant Journeys in Detail
Zulaikha Ariffin
HR Executive · Cold Start → Hot Work · 2024–2025
The Starting Point
Zulaikha had no coding background and worked full days in an HR role. She had watched AI tooling arrive in her organisation and wanted to understand what it was actually doing — specifically whether the outputs she was being asked to trust were reliable. She enrolled in Cold Start after reading the intensity table and deciding seven hours per week was possible on weekday evenings.
What Changed
She completed Cold Start in eight weeks. She moved directly into Hot Work the following cohort, having met the entry standard. By week twelve of Hot Work she had built a text classification model as her third assessed project. She described the code review on that project as the most useful feedback she had received on technical work.
Where She Is Now
Zulaikha uses the statistical knowledge from Cold Start daily when reviewing analytics dashboards. She has started the Tempering track. She says the most practical outcome so far has been being able to read model evaluation output and ask specific questions about it, rather than accepting summaries from colleagues who built the systems.
"The intensity table is the feature I recommend to every person I tell about Weightsmith. You know what you are agreeing to before you pay."
Reuben Ng
Backend Developer · Hot Work → Tempering · 2024–2025
The Starting Point
Reuben was a backend developer who could write Python but had no practical experience with model training. He had read documentation and watched videos but had never run a training loop on real data. He enrolled in Hot Work directly after verifying he met the entry standard through the self-assessment exercise Weightsmith provides.
What Changed
He completed all four Hot Work projects and received detailed code review on each one. He said the architecture clinics were the most valuable component — he had been making architecture choices without understanding the production tradeoffs. He enrolled in Tempering the following cohort and scoped a document classification system as his capstone project.
Where He Is Now
Reuben completed Tempering with a deployed system that classifies internal support tickets, a written technical report and a recorded defence. His employer had been planning to outsource the work. He presented the Tempering output as a scoped proposal instead. The alumni introduction connected him with an engineer working on a related problem at a different company.
"I knew backend development. I did not know how to make decisions about model architecture. Hot Work fixed the second problem. Tempering gave me something to show for it."
Reach Us
Contact Details
Phone
+60 6-957 3184Address
4 Jalan Merdeka Raya
75000 Melaka
Office Hours
Mon–Fri 10:00–18:00
Sat 10:00–13:00 MYT
Join a Cohort
Read the track details and send an enquiry
The experiences above are from people who completed tracks while working full-time. The intensity table tells you whether the commitment fits your current schedule before you pay anything.