Day 1: The Ambitious Recipe Website Adventure Begins

Dec. 8, 2024, 6:40 p.m.

Hello, world! Sazzzel here, your friendly neighbourhood Junior Full Stack Developer, embarking on a heroic (and occasionally bewildering) journey to create my capstone project. And what better way to immortalise my growing pains than a daily blog? Let me take you through the chaos of Day 1. Buckle up; it’s going to be a dry, witty ride.

The Grand Plan: Recipe Website with AI and OCR

You know the saying: go big or go home? Well, I must have decided to go big *and* to the moon, because my first idea was a Recipe website. But not just any recipe website. Oh no. This one would use AI to suggest recipes based on whatever sad, wilting ingredients are lurking in your fridge. And for the cherry on top? OCR (optical character recognition) to scan and digitize your grandmother’s ancient, gravy-stained recipe cards. Ambitious? Absolutely. Plausible within my timeline? Well, hindsight’s 20/20, isn’t it?

Tools of the Trade

Thanks to Code Institute, the environment setup was mercifully pre-handled for me. No docker drama, no database debacles, just a pristine template ready for me to mess up—I mean, customize. I created my GitHub repository and confidently titled it something inspirational, like “AI-Recipe-OCR-Magic…” or maybe just “ThisBetterWork.”

Sketching My Dreams: Wireframing

Armed with caffeine and a touch too much enthusiasm, I spent the morning creating wireframes. I envisioned a sleek homepage with rotating recipe cards, a sassy AI assistant suggesting you finally use up those old lentils, and a snazzy dashboard for uploading and scanning recipe images. By lunchtime, I had several wireframes that looked like they belonged in a tech startup pitch deck. By dinner, I was wondering who was going to build all this (spoiler: me).

User Stories: AKA Writing My Wishlist

In the afternoon, I wrote my user stories. Here’s a snippet:

  • As a user, I can upload a photo of a recipe card so that I can digitize it for easy access.
  • As a user, I can search for recipes using AI-powered suggestions so that I can finally use up that bag of quinoa.
  • As a developer, I can dramatically lower my expectations so that I can finish this project on time.

Okay, maybe I didn’t write that last one, but it would have been wise.

The Naïve Optimism of Day 1

By the end of the day, my repository was buzzing with boilerplate code, wireframes, and a mountain of over-scoped ambitions. Did I think I’d be done in three weeks? Of course. Did I account for the fact that AI integration and OCR aren’t exactly weekend hobbies? Not so much. But hey, that’s a problem for Future Sazzzel. Present Sazzzel went to bed feeling like the next Silicon Valley disruptor.

Lessons Learned (Already!)

  1. Ambition is great; realism is better. If I had a pound for every feature I planned on Day 1, I could afford to hire someone else to build this for me.
  2. Document everything. There’s nothing quite like writing user stories to remind yourself that the devil is in the details.
  3. Don’t let the scope creep in. At this point, I’m practically holding the door open for it.

And there we have it, folks: Day 1 of Blogggel—I mean, the Recipe website journey. Stick around for tomorrow’s post, where I’ll probably bite off more than I can chew. Again.

Cheers,
Sazzzel



No comments yet. Be the first to comment!