Participant Feedback
Reviews from workshop participants, RL course students, and enterprise retainer clients. Edited only for length, not for tone.
Back to Home3+
Years Operating
310+
Workshop Participants
4.6
Avg Rating / 5
18
Enterprise Clients
Feedback from individual participants across the workshop and RL Fundamentals course.
Nurul Zahirah
Petaling Jaya · Data Analyst
I came to the weekend workshop having worked with spreadsheets and SQL for a few years but never touched ML. What I appreciated was how the two days were structured — you could see where you were going at each point. The leakage section surprised me; I had no idea how common that issue was in tabular work. The model card at the end felt like a genuinely useful exercise, not a box-ticking exercise.
June 2025 · Weekend Workshop
Ravi Krishnamurthy
Shah Alam · Software Engineer
Thirteen weeks is a real commitment alongside a full-time job. The pace in the RL course was consistent — five contact hours a week, plus the lab work. The reproduction study at the end was harder than I expected, mostly because the paper I chose had unclear hyperparameters. Writing up what I couldn't replicate and why ended up being the most educational part of the whole course.
July 2025 · RL Fundamentals
Siew Yan Loh
Cyberjaya · ML Researcher
The module on evaluation under stochasticity was what I specifically wanted. Most RL courses I've looked at skip past it. Here it's a full week with references supplied — not summarised claims about what benchmarks do and don't show, but the actual papers. The benchmark limitations coverage made me reconsider how I'd been reading several results in my own work.
July 2025 · RL Fundamentals
Faizul Haris
Kuala Lumpur · Product Manager
I was on the fence about the workshop because I'm not an engineer and wasn't sure I'd keep up. The sandbox environment meant I didn't spend either day troubleshooting installations. The "honest scope" description on the website was accurate — it really is one specific path, not a survey of the field. For what I needed, that was exactly right.
June 2025 · Weekend Workshop
Amirah Mustafa
Putrajaya · Government Analyst
The workshop gave me enough to evaluate ML project proposals from vendors more carefully. I'm not building models, but understanding how a baseline should be constructed and what a model card is supposed to contain changed how I read the documentation we receive. That was the outcome I was looking for.
July 2025 · Weekend Workshop
Chong Wei Ling
Penang · Data Engineer
The RL course is not light. Ten hours of lab work a week on top of five contact hours is accurate. I found the actor-critic section the hardest — the material itself is complex, and the implementation exercise for that week took me closer to fourteen hours. The instructor was reachable with specific questions, which helped. Would have appreciated slightly longer session blocks rather than spreading five hours across the week.
June 2025 · RL Fundamentals
Two accounts from organisations on the enterprise retainer programme.
The organisation had hired three ML engineers over eighteen months but had no shared engineering practice — no common evaluation framework, no documentation standards, and no internal review process for model changes going to production.
Initial curriculum scoping against their Python and SQL stack. Quarterly training blocks covering evaluation frameworks, documentation practice, and code review standards. Monthly office hours for specific technical questions. Code review clinics against their internal repositories in quarters two through four.
A written evaluation framework in use across three teams, model card templates adopted as an internal standard, and the annual capability report used as input to their 2025 hiring plan. The organisation renewed for a second year.
"The code review clinics were the most directly useful part. Having an external eye on our actual codebase surfaced issues we'd stopped noticing."
A team of twenty analysts needed to develop working familiarity with ML outputs — not to build models, but to evaluate vendor submissions and internal model proposals more precisely. Their existing technical training covered theory without hands-on practice.
A curriculum written specifically for an evaluation-oriented audience: how models are assessed, what evaluation metrics mean and what they hide, how to read a model card, and what questions to ask when a vendor presents results. Four quarterly blocks ran cohorts of up to twenty staff, rotating so different teams were covered across the year.
Internal model review process updated to include structured evaluation checklists drawn from the curriculum. The annual capability report documented coverage gaps in the firm's current review process and recommended two specific areas for continued development in year two.
"The curriculum matched what our analysts were actually being asked to do. That specificity was what made the training land."
Address
21 Jalan SS 15/4B
47500 Subang Jaya
Selangor, Malaysia
Office Hours
Mon – Fri: 09:00 – 18:00
Sat: 09:00 – 13:00
Closed Sunday & public holidays
Contact us with your background and which programme you are considering. We will give you a straight answer about fit.