AWS Builder Center
First Commit, Day Four: Submitted, and Straight Into an Exam

First Commit, Day Four: Submitted, and Straight Into an Exam

Four days ago I had a blinking cursor and no idea. Tonight there's a live URL. The honest story of the last day, from 10am to 11pm on five coffees.

I build, write, create and explore
“I said begin before you feel ready. Turns out you have to ship that way too.”
It’s done. A few minutes ago I submitted Fuko. Four days ago I sat here with a blinking cursor and no idea what I was building. Tonight there’s a live URL that actually does something. I’m going to sit in that for a second before I talk myself out of being proud of it.
The day itself was a straight line. Up at 9, at university by 10, and then heads down from 10am to 11pm. I recorded the demo video somewhere in the middle, which is its own special stress when you have exactly one take of energy left in you. I broke the day up with a bit of badminton whenever my brain started smoking, ran the whole thing on about five coffees, and somehow, genuinely, had fun.
Here’s what Fuko became. It shows you an opportunity only when it actually matches you, and every result tells you why. Two streams: Contribute for remote skill-based work, Near you for in-person events. The rule I refused to break is that opportunity type is a preference, not a relevance signal, so nothing shows up on a hunch. The matching runs on whole tokens, so cli never pretends to be client. It pulls each GitHub repo’s real languages so a reason like “matched on TypeScript” reflects the actual stack, not a word guessed from a title. And when nothing qualifies, it says so instead of padding the feed to look busy. Built for clarity, like I promised.
The AWS part I learned in real time. I studied the pieces I needed as I hit them and actually used them: DynamoDB for the data, Lambda for the matching, EventBridge to keep it syncing, SAM so the whole backend is one file I can redeploy, Amplify to host it. Learning a cloud stack while building on top of it is a particular kind of humbling. Twenty-five commits, a Funky theme that’s still a little feral, and a roadmap far longer than what shipped. But it’s live, it works, and it does the one thing I set out to do.
And now, the least glamorous part. I submit this and immediately open my Automata Theory notes, because that exam is tomorrow morning. I’m writing this from the floor of a friend’s PG, because mine is a triple-sharing room on another campus, congested, and closed on Sundays. So this is where the hackathon ends for me. A borrowed floor, coffee number five gone cold, an exam waiting.
Four days ago I wrote that the idea comes because you begin. It did. I didn’t feel ready, I didn’t have the clean setup, and I built the thing anyway, between exams and SIH and a commute and a floor to sleep on. Win or not, I have a live product and four honest posts I did not have on Thursday.
If you’re waiting for the tidy version of your life to start building, it isn’t coming. Build from the floor if that’s what you’ve got.
ps: five coffees, one video take, badminton saved my brain at least twice today. ps: now, I have to studyAutomata Theory. wish me luck again, I’ll need it more than the submission did.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article