How a Hackathon Changed My Life – A Personal Story from the CEO of SupremeTech
21/08/2025
32
Table of Contents
Written by Binh Nguyen, CEO of SupremeTech, from his own Hackathon journey
Hi everyone,
Today I’d like to share an experience that truly shaped who I am, not just as a professional, but as a builder. This is the story of how a Hackathon transformed my mindset from being just a developer into becoming a tech builder.
Before moving into business analysis and later management, I started out as a Front-end Developer. Back in 2016, I was self-learning HTML, CSS, and React.js.
Then in 2017, I had the chance to join a Hackathon that completely changed how I approached product development. It was the turning point that made me realize the difference between being a coder and being a builder.

Step 1: Accepting the Challenge
The Hackathon was organized by the Da Nang Business Incubator in collaboration with the Embassy of Israel, with support from venture capitalists and incubators from Israel.
At that time, the prizes weren’t particularly big. But as someone new to the industry, eager to start a career and even dream of building a startup, I felt I had to join. Honestly, another reason was my competitive nature, I wanted to prove that even though I came from a non-tech background and had only been coding for a year, I could still stand shoulder-to-shoulder with others.
Step 2: Preparing, Planning and Strategy
For those unfamiliar, a Hackathon is a short, intensive coding competition where individuals or teams create a product in just a few days. You start from an idea, build it, and then present it on the last day – the demo day. The products are evaluated by the judges based on the Hackathon’s criteria.
Our theme that year was straightforward: turn a startup idea into a product in just two days.
If coding is a sport, then Hackathon is like a championship match. To build an app in such a short time, we had to prepare carefully, especially the methods to build a complete app as fast as possible. Boilerplates, bootstrap, pre-made components, even self-made code generation tools to save time… techniques that now are nothing difficult, but the goal of a Hackathon is always the same: build fast and ship immediately!
With everything ready, we headed off to the competition.
Step 3: Code, Bug, Hack and Chaos
After the opening ceremony, we chose our topic and immediately got to work.
Our topic was an app to find venues and make group reservations.
Like most projects, the first 50% of the codebase went smoothly. We managed to build it within half a day. But the problems started when we moved into the core features and tricky logic like date pickers, slot reservations, venue data, etc. Ideas kept coming, we kept coding, and bugs showed up just as much.
By 9 p.m., we were exhausted, buried in bugs, with no clear way forward, and nothing ready for the demo the next morning. So we decided to stop coding and discuss how to deliver on time. After more than an hour of debate, here’s how we planned the remaining work:
- Stop implementing backend logic and data crawlers, use front-end mockups to ensure demo flow
- Deploy on Heroku to save time on server setup and have a live product
- Spend extra time preparing slides to explain during the demo
In the end, the chaos turned into something more organized. The funny part was that I, the front-end guy, had to keep coding, while our back-end guy ended up making the slides.
Step 4: Demo – The G Hour
After polishing things up until the last minute, we got on stage to demo. This part was quite similar to a sprint review, except that we had to stand on stage and present to a big audience. For everyone at ST now, sprint reviews are done very well already, so nothing more to add here.
What surprised us was that the judges, especially the Israeli experts, didn’t pay much attention to the detailed features we had spent so much effort on. Instead, they asked “general” questions like:
- What is the technology that makes this product better than others?
- In what situations would users actually want to use this product?
Step 5: Reflection – What I Gained
We didn’t win for two main reasons:
- The software was quite complete but didn’t clearly show competitive advantages.
- Vietnamese users at that time didn’t really have the habit of booking tables/services via apps.
Although we lost and felt quite upset at that moment, looking back now, I gained so much more:
- Confidence in setting up the initial codebase and preparing projects for production
- Understanding that the value of technology lies in efficiency and competitiveness, not the number of features
- Realizing that users don’t care how much effort we put into building an app, they just want their problem solved in the best way
- Delivering code fast and continuously, without waiting
- Preparation and choosing the right topic are the two keys to winning
- With the right mindset, I could work with the best developers without losing confidence, even with less knowledge and experience
Lastly: Try It Once—It Might Change You Too
Hackathon changed me from being just a self-taught coder into a true tech builder. The mindset I gained in those two days has helped me a lot throughout my career until now. I believe many others will also learn valuable lessons from upcoming quality Hackathons.
100 million VND in prizes are waiting for you at the SupremeTech Hackathon this September 2025. Enjoy!
Related Blog