The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
🚨 A bug that looks like a frontend problem might actually be your backend.
I once spent time checking UI code, only to find the real issue was an API returning the wrong data.
When debugging, I always check the full data flow:
Frontend → API → Backend → Database
Debug the source, not just the symptom. 🔍
Have you ever found a backend bug while fixing a frontend issue?
Yes haha, i can imagine that feeling, what a way to debug
😄 Sometimes debugging feels like detective work. You start looking in one place and end up finding the real issue somewhere completely unexpected..
hmm......well said
yess appreciate 😊😊
True. I recently had this challenge, Json; API errors can be misleading.
Absolutely! 😄 JSON and API errors can definitely send you in the wrong direction. That's why I always verify the actual response, backend logs, and network requests before assuming where the bug is..
Surprisingly the bug is usually a syntax error...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
🔥 New addition to my portfolio 🔥
Previously I had an SVG mask of my logo in the center with my showreel behind it, but this had a couple of issues. So yesterday I pushed it further and I created a 3D variation, video playing inside it, glass refraction and it's even more beautiful when you click into it.
Take a look; www.grilledpixels.com
the glass refraction on the 3d mark is a cool touch. did you build the interaction with three.js?
Built Gloss Instant Booking for the #lovablechallenge.
I created a booking experience for a fictional solo automobile detailing business in Austin where the owner was losing time to back-and-forth booking messages.
Instead of:
Inquiry → questions → calendar checking → confirmation → reminder
Gloss turns it into:
Inquiry → availability → confirmed booking → automated follow-up.
Built with @Lovable.
#lovablechallenge
Really like how clearly you've framed the before vs. after workflow here. For a mobile detailing business, did you also account for travel time/location when determining availability?
Feels like that's where scheduling gets especially interesting once bookings start stacking up.
We've been building something for a while, and it's finally time to share it.
Meet Zupa, an AI tool that helps you write LinkedIn and social media posts that actually sound like you.
Most people know they should post more. The hard part is sitting down and turning a rough idea into something worth reading. Zupa takes that idea and shapes it into a post built around what makes people stop scrolling and engage.
It's made for founders, marketers, agencies, and anyone building a personal brand who doesn't have hours to spend writing.
Here's a quick look at what we've built 👇
We're opening early access now, and it's free to try. If you want a look, check out https://www.zupapost.ai/
Honest feedback is welcome too. That's how we'll make it better.
Really like the idea of using psychology to help people rewrite their posts! The UI feels thoughtful and fits the concept really well. It’s a focused tool I could see being useful in everyday writing, especially for making posts more engaging. How long did it take you to go from the initial idea to the finished website?