The first thing I learned is not about code. It is about the clock.
Devpost lists deadlines in Pacific Time. I live in Manila. For the UGREEN Hackathon 2026, Round 1 closed on November 15 at 11:45 p.m. PT, which is 3:45 p.m. on November 16 here. If you only read the calendar date, you are already late, or you think you have a day you do not have. I write the Manila time on the file. I do not trust my memory with a timezone I do not live in.
My Round 1 entry for that hackathon went in on November 16. It is on AI NAS, in the Creativity track they call Unleash Your Creativity. I entered as an individual, from Manila. Teams of up to three are allowed, but I did this alone. I do not have a result yet, and I will not claim one.
The project is a Skill I call Footage Librarian. I am a solo creator who posts reels for Facebook pages, and my footage folders get messy. The Skill is meant to do three jobs. It catalogs clips and stills. It matches a pasted script to the best shots I already have, and writes a selects list. And it flags problems before I post: missing AI labels, faces I have not cleared, exact duplicates. It does not delete anything. It does not post anything. Writes wait for my approval. That part I already believe in.
I wrote it to the organizer's own Skill standard and ran their checker. I have not installed it on a NAS. If I say I have, I am lying. Honesty is slower. It is also the only version of this I am willing to put my name on.
A few rules I actually use
Build the thing you already needed. I did not invent a problem to fit a track. I have the messy folders. The Skill is a way to look at them without pretending I have a staffed library.
Read the official rules, not just the landing page. UGREEN says no purchase or payment is required to enter. Round 1 does not even require access to a NAS. Finalists, if they are chosen, get a testing day on an assigned machine. Nobody should be asking you to buy the hardware just to be in the first round.
Watch the timezone, as I said. Watch the difference between a registration date and a submission date. On this one they end at the same moment, which is tidy. Not every event is that tidy.
Be plain about what is done and what is not. "Passed a static checker" is not the same as "tested on the device." Judges can tell. So can you, if you are honest with the page in front of you.
And the safety rule I do not bend: I never give organizers money, passwords, or extra ID.
A physical event may ask to see a valid ID at the door. That is ordinary. An email that wants a scan of your ID, a reservation fee, a password, or a bank detail is not a hackathon I stay in. I started saying this out loud before Manila Hack, which was a separate in-person event, and I use the same rule on Devpost. Free to enter means free. If someone later asks you to pay to hold a seat or to release a prize, you stop.

