Back to blog
AIFebruary 24, 20263 min read

Projects on the agenda

Overnight my brain kept working and in the morning I wrote down a dozen projects I want to build while learning vibe coding. From hooking up an X feed, through a Supabase blog, newsletter, games, online chess, payments, to data visualizations from job boards and a CV generator. All on one site — we're building a Frankenstein.


Overnight my brain kept working and I was thinking about what else I'd like to build, to test various possibilities of vibe coding and how everything connects — integrating external tools or creating them "on my own." Woke up in the morning and wrote down a dozen or so topics. Some seem simple, some a bit more complex, but everything looks achievable. We'll see.

What I'd like to build next

  1. Hook up a feed from my X after setting up a developer account on the platform
  2. Set up a blog on Supabase with login and a text editor — figure out what that's all about
  3. A notebook (behind login) in Airtable style: what I worked on, task duration, and difficulty level
  4. Connect the blog to a newsletter that auto-sends every new post — build the automation
  5. A simple Calendly for scheduling a call with me, with automatic Google Calendar integration
  6. Some simple games: snake, minesweeper, solitaire
  7. Maybe more complex games like chess with different board skins
  8. Chess with the option to play against me online asynchronously (after registration)
  9. Integrate with some external API
  10. Add payments for purchasing something

Industry-specific ideas

  1. Data visualizations based on data from our job boards via the Snowflake API
  2. Build my own browser extension for something, e.g. scraping job listings
  3. Something for e-learning, like a mini-course generator from a YouTube link
  4. Build a job market news aggregator
  5. Build a simple CV generator

Much more complex structures

  1. Our internal TomHRM — leave management for the company
  2. A mini educational platform with courses based on provided materials

That's all that comes to mind for now. I'll keep updating this list in future versions of this file.

Expectations for the pace

If I could spend 1 day (5h) on each topic from list 1–10 (so 10 topics × 5h = 50h) and three working days on industry topics (5 topics × 15h = 75h), I'd need about 125h total. I'm not even counting the much larger projects here time-wise — that's just too big a scope.

So we're looking at roughly end of quarter, assuming an optimistic and very ambitious pace of 5h per day. If I could learn a decent amount in 130h then why not. Given that I'll probably get stuck on some topics for hours — I already got frustrated when I mistyped a command because I didn't use the right number of dashes — I suspect the problems will grow exponentially with these tasks. If I finish list 1–10 by end of quarter, I'll be satisfied. I'll chronicle everything here and add it to the notebook (point 3) regarding time tracking.

I'm curious how I'll need to build this to connect all these elements directly on one site. I want to create everything in one place, to better understand how to build somewhat more complex structures and how to do vibe coding that makes sense even for more complex topics. So we're building this Frankenstein… :)

Stay tuned!


Back to blog