It’s Day 11 of my wild Blogggel adventure, and what a journey it’s been! As I write this, I’ve just finished a rigorous round of user testing (read: me pressing buttons while sipping Earl Grey and shouting, “Why don’t you work?” at my laptop). Blogggel is starting to look less like a franken-code monster and more like an actual, functional blog platform. Dare I say, I’m even a bit proud.
Here’s how today’s escapade unfolded:
Step One: Poke Everything Until It Breaks
First on the agenda was user testing, which, as a lone developer, meant I was both the user and the tester. I clicked every button, filled out every form, and tried my absolute hardest to make the thing crash. I submitted blank blog posts, used emojis where they didn’t belong, and even copy-pasted the full text of War and Peace into the “Create Post” form (fun fact: Blogggel handled that beautifully). After an hour of this, I had a list of improvements longer than a queue for a free cup of tea.
The most glaring issue? My delete functionality was a bit too enthusiastic. It didn’t ask “are you sure?” It just deleted posts like an overzealous Marie Kondo. So, I added a confirmation prompt. Now, Blogggel politely asks, “Are you absolutely sure you want to delete this masterpiece?” before binning your work. Progress!
Step Two: Navigation Woes
Next, I tackled the navigation bar, which was about as intuitive as a London road map from 1805. Clicking on “Home” took you to the All Posts page, but clicking “All Posts” took you to...also the All Posts page. Why did I think having both buttons was a good idea? No idea. Probably sleep deprivation. I removed the duplicate and added a nice little hover effect to make the remaining buttons look like they belonged on purpose.
Step Three: Error Messages Need Love, Too
My error messages were woefully inadequate. For instance, if you tried to save an empty post, Blogggel just stared blankly at you as if to say, “Well, that’s on you, mate.” Hardly helpful. So, I rolled up my sleeves and gave the error handling some British charm. Now, if you forget to add a title, Blogggel cheerfully reminds you, “Every great story needs a title, dear writer!” Far less judgmental and much more civilized, wouldn’t you agree?
Step Four: Documenting the Madness
As is tradition, I rounded out the day by updating my README. Honestly, this document has become a bit like a diary, chronicling every bug, every triumph, and every near-existential crisis. Today’s updates included a new “Known Issues” section, which currently lists only one item: “Navigation bar hover effect doesn’t work in IE11. Solution: Stop using IE11.”
Lessons Learned
- Always have a cup of tea nearby. It’s amazing how much clearer code looks after a quick sip.
- Over-testing is not a thing. Try to break your app in every ridiculous way you can imagine because someone else definitely will.
- Error messages are an art form. A little personality can turn frustration into a chuckle.
Tomorrow’s plan is to dive into some CSS tweaks and maybe (just maybe) add a tiny feature. But for now, I’m signing off. Blogggel survived another day, and so did I. Cheers!
Comments (0):
No comments yet. Be the first to comment!