What People Say About Learning Here
These are accounts from people who've worked through our programmes. We've kept them honest — including the ones that mention what was harder than expected.
← Back to HomeFrom Learners Across the Programmes
Ratings range from 4 to 5 stars. Not every experience is the same, and we think that's worth showing.
"I'd tried two other coding courses before this and stopped both times around week three. The difference here was the tasks — there's something to do immediately after each lesson, which stopped me from just passively watching. It took me about eight weeks and I finished with an actual working project, which I didn't expect."
"The revision rounds were what I wasn't expecting and turned out to be the most useful part. After my first forecasting model submission, the feedback pointed out two things I hadn't considered. The second version was noticeably better and I could actually explain why. Four stars because I wish the community was a bit more active — it gets quiet sometimes."
"I was building a small demand-forecasting tool for my family's supply chain. Working through it with a mentor who had real industry context changed the direction of the project in a way I wouldn't have managed on my own. The sessions were monthly, which suited my schedule. Took about five months total. Worth it."
"I work full time and needed something I could pick up and put down without losing the thread. The module structure made that easy — each lesson is short enough that I could do one in an evening. I worked through the foundation course in about six weeks going at my own pace."
"The real datasets made a real difference. I'd done tutorials before that used perfectly clean CSV files — everything just worked. Here the data had gaps and anomalies, and dealing with that was part of the assignment. That's closer to what you actually encounter. Feedback was specific and useful, not just encouraging."
"Good experience overall. My mentor kept things realistic and pushed back when my project scope was getting too ambitious — which was the right call. I'd have spent months on something that didn't work. The redirect saved time in the end. Four stars because the onboarding at the start could be a little clearer."
Three Learner Journeys in More Detail
A logistics administrator in Bangkok wanted to understand how AI tools worked behind the scenes — not to become a developer, but to be able to work with developers more usefully. No coding background at all.
Enrolled in the Foundation Course and worked through it over ten weeks, about three evenings per week. The pace was self-selected, and several lessons were revisited more than once. The tasks helped identify which concepts needed more time.
Finished with a working classification model and, separately, better context for conversations with the data team at work. Not a developer, but no longer relying on others to explain what AI models are actually doing.
"I wanted to understand what people were talking about in meetings. I understand it now, and I can ask better questions."
A junior data analyst in Chiang Mai who knew Python basics but had never built a forecasting model. Wanted to move from cleaning spreadsheets to working with predictive models.
Joined the Time Series track and worked through it over twelve weeks. The first model submission came back with detailed feedback on feature selection. The second version addressed those points. A third round followed before the final submission.
Completed a full end-to-end forecasting project with three documented iteration rounds. The project is now part of the analyst's portfolio, and the methodology is being used informally in their current role.
"The feedback after the first submission was more useful than anything I'd received in two years at work."
A small business owner in Hat Yai wanted to build a simple tool to predict weekly stock needs for a retail shop. Had some spreadsheet experience but limited coding background.
The mentorship programme began with three sessions on defining the project clearly — what data was available, what "good enough" looked like, and what the tool actually needed to do. Development followed over four months, with monthly sessions and revisions between each one.
A working Python-based forecasting tool the business owner maintains themselves. Reduced weekly over-ordering by roughly 15% in the first month of use, though that figure depends on other factors and the owner was careful to note this in our follow-up.
"My mentor was honest when the first version wasn't doing what I wanted. We looked at why and changed the approach. That was the right call."
Questions About Any Programme?
65 Phetkasem Road
Hat Yai, Songkhla 90110
Mon–Fri: 9:00–18:00 ICT
Sat: 10:00–14:00
Ready to Start Building?
Contact us and we'll help you find the right programme for where you are now. No commitment required to ask a question.
Contact Us