Events / Selected build record

Short deadlines. Real problems. Working systems.

A selected record of hackathons and builder communities that turned learning into working prototypes. This is not yet the complete event history; new entries will be added only after their dates, teams and outcomes are checked against the original files.

How to read the archive

More than attendance badges.

Every retained entry should answer three useful questions: what needed solving, what was actually built, and what came out of the work. The full archive can later expand this same structure with verified teams, dates and media.

  1. 01 / Problem

    Start with a real brief.

    Record the user, workflow or institutional problem—not just the event name.

  2. 02 / Build

    Show working evidence.

    Connect the summary to the prototype, diagram, photographs or original reflection.

  3. 03 / Outcome

    State what changed.

    Capture the result, lesson or project that continued after the deadline.

Selected participation

Hackathons and build sprints.

Each entry focuses on the challenge, role and outcome. Supporting project pages or original records are linked where they are already available.

2025Oct 2025
HackathonSingapore
Builder · FormMind

Cursor Hackathon Singapore

Prototyped FormMind: a system for retrieving and reusing grounded answers across complex forms.

View FormMind
01
2024Late 2024
HackathonKuala Lumpur
Third place

AI Tinkerers × Bank Negara Malaysia Hackathon

Built an n8n and Supabase workflow to compare regulatory documents, assess changes and suggest internal updates; the team placed third.

Read the build record
02
20172017
HackathonIpoh, Malaysia
Second place

MaGIC Startup Weekend Ipoh

An early product-building experience that connected a real problem, a team and a working pitch under time pressure.

03

Build receipts

Original posts and working evidence.

These are Puviin’s own records from the FormMind build, the Bank Negara Malaysia regulatory-document challenge and an AI-security learning event. Photographs, diagrams and the available demo remain attached to their original context.

What carried forward

The event was useful when the method survived it.

01

Start with real work

The strongest briefs were not abstract demos: they involved regulatory change, repetitive documents and other workflows people already struggled with.

02

Make the idea testable

A working n8n flow or usable FormMind prototype made the trade-offs visible and gave teammates, judges and users something concrete to challenge.

03

Carry the useful parts forward

The deadline ends; the learning should not. FormMind continued beyond its first 24-hour build and became a larger document-automation project.

Independent coverage

The community-led learning path, reported by The Star.

Spoke about moving from mechanical engineering into AI-assisted software building, and how local communities made the learning curve practical.

Read the article Follow current event notes