Day 5: Rising from the Ashes of a Deleted Repo
After what can only be described as a small but important breakdown yesterday, I’ve emerged from the ashes of my deleted repository like a phoenix—or perhaps more like a slightly singed pigeon with a newfound sense of perspective. Gone are the dreams of AI-powered recipe brilliance. Instead, I’ve settled on something simpler, something achievable, something... Blogggel.
Why Blogggel?
First off, let’s address the name. Blogggel isn’t a typo. It’s quirky, it’s memorable, and most importantly, it has just enough extra Gs to make people wonder if I’m eccentric or just bad at spelling. Either way, it’s now the official name of my capstone project: a simple blog platform where users can perform all the essential CRUD operations without crying into their keyboards (as I might have done yesterday).
The Pivot: From Ambition to Sanity
Let’s not beat around the bush: my original project idea was ridiculous. A recipe site with AI integration and OCR functionality sounded great when I pitched it to myself over tea and biscuits. But after three days of prototypes, I realised I was in over my head. The phrase “passive scope creep” might as well be tattooed on my forehead at this point. By Day 4, I’d accidentally deleted my repo in a fit of panic (a rookie move, I know), and the sobering realisation hit: I needed to simplify.
Enter Blogggel. No fancy AI, no magic OCR. Just a clean, functional blog platform. View posts. Create posts. Edit posts. Delete posts. Simple, elegant, and most importantly, something I can actually finish within the deadline.
Starting Over: The Day 5 Journey
Today was all about starting fresh and documenting everything. I created a new repo using the Code Institute template (because apparently, I need all the help I can get when it comes to templates). This time, every step is being logged in the README like it’s a diary for future developers—or perhaps just a cautionary tale for myself.
I’ve outlined the project’s scope and listed the user stories:
- As a user, I want to view all blog posts so that I can choose one to read.
- As a user, I want to create a blog post so that I can share my brilliant (or not-so-brilliant) thoughts.
- As a user, I want to edit my blog post so that I can fix the inevitable typos.
- As a user, I want to delete my blog post so that no one knows I ever thought that badly-written haiku was a good idea.
Wireframes and Structure
With my new focus, I sketched out some very basic wireframes. Think minimalist chic, or maybe just lazy efficiency. A landing page listing all blog posts. A single post view. A form to create new posts. A page to edit existing posts. No bells, no whistles, just good old-fashioned blogging functionality.
GitPod and Heroku: My New Best Frenemies
Today also marked my first foray into GitPod for development and Heroku for deployment. GitPod, bless its heart, seems determined to turn me into a fan despite my initial scepticism. And Heroku? Well, we’ll see how that goes when deployment day arrives. Let’s just say I’m cautiously optimistic—or as optimistic as one can be after yesterday’s repository implosion.
Lessons Learned (So Far)
- KISS: Keep It Simple, Sazzzel. My ambitions were noble, but they were also the coding equivalent of trying to climb Everest in flip-flops. Blogggel’s simplicity is its charm.
- Documentation is your friend. Losing all my previous work taught me the hard way that documenting as you go isn’t just a good habit—it’s survival.
- Humour helps. If I can’t laugh at myself, who will? (Spoiler: Everyone.)
So here I am, with a fresh repo, a fresh perspective, and a project that actually feels doable. Blogggel might not change the world, but it’s already changed mine—and if that’s not worth a celebratory biscuit, I don’t know what is.
Comments (0):
No comments yet. Be the first to comment!