With iNTUition’s fourth iteration happening soon and being my final year in college, I thought it would be a good idea to document how iNTUition began and share how we started Nanyang Technological University’s only 24-hour hackathon and one of Singapore’s largest student hackathons.

As a freshman at Nanyang Tech back in 2014, I remember being particularly disappointed with the lack of tech events and clubs on campus. NTU just had a handful of tech-oriented student clubs, barely any major tech events and no annual hackathon (unlike most major engineering universities).

Nonetheless, there were two student clubs that caught my attention (despite being designated Tier 3 by NTU’s club system) — NTU Open Source Society & IEEE NTU Student Branch. I applied to both and had interviews with both clubs’ executive members. By my third week at university, I had joined IEEE NTU Student Branch as a Publicity Director and had gotten rejected by NTU Open Source Society (I’m now President of the club ).

#### iNTUition.init()

I don’t exactly remember how the idea of a hackathon was brought up but during one of the club’s initial meetings in August 2014, it became fairly clear that we would organize one — NTU’s first proper 24-hour hackathon. Having never been to a hackathon myself, it was exciting to be part of a team that was organizing something so integral to hacker culture.

We didn’t have a name for the hackathon yet and I distinctly remember the brainstorming session we had as a team for the same. At some point during the discussion, we knew the name had to be tech-y (i.e. must be one word or multiple words concatenated in camel case) and it had to relate to NTU somehow. After someone Googled which words contained ‘ntu’ in them (in case you’re curious, here), we settled on iNTUition, which not only was a fantastic pun but also represented how problem-solving & coding is second nature to most hackers.

Finally, it was decided that the hackathon would be held on the weekend of 25th & 26th October, which gave us just enough time to set things up and wasn’t too close to the final examinations.

#### Error: Variable 'hackathon' already defined.

Immediately after the meeting, the team got to work. We had to write an event proposal for NTU’s Student Affairs Office (SAO), source for sponsors, get a venue and decide on prizes in a month’s time before we opened registrations. It was extremely overwhelming.

As luck would have it, it wasn’t too long before we hit our first hurdle. SAO wouldn’t let us use the term ‘hackathon’ for our event because there was already another event on campus using the same term. What?! Where? Turns out, one of the student clubs [name redacted] was holding a two-hour coding challenge and calling it a hackathon. Despite our best efforts, we couldn’t convince the management to let us use the term too and we had to rename our event to ‘iNTUition: 24-hour Coding & Pitching Competition’. Oh, bureaucracy.

#### iNTUition.setup()

On the flip side, we managed to score a venue and our first sponsor for the event — Nanyang Technopreneurship Center. The Director of NTC at the time also agreed to be part of the judging panel, which was great.

Other potential sponsors, however, were not that receptive. We cold e-mailed numerous technology companies in Singapore and overseas but to no avail. We learned pretty quickly that nobody wanted to sponsor the first of anything and realized that if we didn’t prove ourselves this time, iNTUition would go back right where it came from.

Thus, began the incessant e-mails to personal connections and after some effort, we managed to rope in IEEE (since we’re their student branch), Microsoft (through members of the Microsoft Student Partner program), GitHub (surprisingly responsive to cold e-mails) and a few other interesting sponsors like PUB (Public Utilities Board of Singapore) who gave us cartons of water bottles, BBQ Wholesale who gave us BBQ vouchers to give away and a resort in Bali that sponsored accommodation for 4.

We were still short on cash when SAO came swooping in with a \$700 grant (thanks to the extremely well-written event proposal) and we managed to have just enough money to cover the logistics, meals & prizes for the event.

A few days after our sponsorships deals closed, the posters below (my Photoshop skills aren’t the best) went up around the university and registrations started flowing in.

iNTUition 2014 Poster

#### iNTUition.run()

And so, we ran the very first iNTUition with ~70 participants. Most of the event went smoothly (thanks to our logistics team) but we ended up overshooting the time allotted to us on Sunday by a few hours, which wasn’t the best thing for a bunch of sleep-deprived college students. Nonetheless, we successfully ran NTU’s first 24-hour hackathon and actually had some pretty quality hacks come out of it! If I remember correctly, the winning hack was one that aggregated loyalty points across e-commerce platforms & physical retail stores.

iNTUition 2014's Opening Briefing

#### iNTUition.upgrade()

Since the first iNTUition in October 2014, we’ve had major improvements to branding, event quality and general tech-iness. We’ve organized iNTUition two more times, once in March 2016 (iNTUition 2016) when I was Chair of iNTUition’s organizing committee and another time in October 2016 (iNTUition v3.0) when I was President of the club. Each year, we’ve gotten more participants and sponsors, better prizes & hacks of higher quality through the hard work and dedication of the team.

The Winning Loot of iNTUition 2016

Winners & Judging Panel of iNTUition v3.0

#### while(true) { iNTUition.run() }

In conclusion, iNTUition has been a pretty important part of my university life and while I’m no longer part of the organizing committee, having ended my term as President in July 2017, I’m extremely excited to attend iNTUition 2017 as a participant and can’t wait to see how iNTUition grows over the next few years.

iNTUition 2017 Poster

Disclaimer: A lot of this happened three years ago, so forgive me if I missed out on or didn’t accurately describe certain events.