Blog
Wow thats a lot of F*** BUGS

A developer's journey through the seven circles of debugging hell
Building Negativo.es has been... an experience. Here's a comprehensive list of every bug that made us question our life choices, and the absolutely normal™ ways we fixed them.
The Bug Hall of Fame
1. The Invisible Blog Posts
Bug: Blog page showed "No posts yet" even though we definitely had posts.
What we thought: "The API must be broken" What it was: Hashnode's headless mode requires authentication. We were basically knocking on a locked door expecting it to open.
Fix: Created a backend proxy to sneak the API key in like a VIP pass. The posts now appear, probably wondering where we've been all this time.
2. The Plain Jane Content
Bug: Blog posts looked like they were styled by a developer who discovered HTML yesterday.
What we thought: "Tailwind is broken" What it was: The typography plugin was installed but never invited to the party (not added to the config).
Fix: Added one line to tailwind.config.ts. One. Line. Hours of debugging for one line. We're fine.
3. The 404 Host Mystery
Bug: Hashnode returned 404 for our publication host.
What we thought: "Our blog doesn't exist in this reality" What it was: We were looking for negativo.hashnode.dev like confident developers who definitely know what they're doing.
Fix: Actually verified the correct host in the Hashnode dashboard. Turns out reading documentation is occasionally useful.
4. The Empty Edges
Bug: GraphQL response had edges: [] - a desolate wasteland of nothingness.
What we thought: "Hashnode ate our posts" What it was: No Authorization header = no private publication access. Who knew APIs had trust issues?
Fix: Gave the API our credentials like a proper introduction at a networking event.
5. The Prose That Wouldn't Prose
Bug: Headings, lists, and blockquotes rendered as plain text. Very aesthetic. Very wrong.
What we thought: "CSS is a scam" What it was: The prose classes need the typography plugin to function. They were just vibing without purpose.
Fix: require("@tailwindcss/typography") - three words that ended three hours of suffering.
6. The CORS Chaos (Honorary Mention)
Bug: Browser screamed about cross-origin requests.
What we thought: "The internet is fundamentally broken" What it was: Browsers have trust issues. Edge functions don't.
Fix: Moved API calls to backend. Let the server be the adult in the room.
7. The Lists Without Style
Bug: Blog post lists used default bullets. Boring. Unbranded. Disappointing.
What we thought: "This is fine" What it was: It was not fine. Our brand deserves golden bullets.
Fix: Added custom CSS with ::before pseudo-elements. Now bullets are yellow. As they should be.
Lessons Learned
- Read the docs first - But we won't. We'll struggle first, then read them.
- Check if plugins are registered - Installing != using. Revolutionary concept.
- Backend proxies fix everything - When in doubt, add another layer.
- One line of code can solve hours of debugging - This is fine. Everything is fine.
- Typography requires typography - The most recursive lesson of all.
Final Thoughts
Building software is just repeatedly fixing bugs until you create new, more interesting ones. We've achieved enlightenment through suffering, and now our blog looks sexy.
If you're still reading this, congratulations. You've witnessed the raw, unfiltered chaos of software development. May your builds be green and your bugs be few.
— The Negativo.es team, surviving one bug at a time