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
Guess 216 isn't enough to crack the top 1%
Aiming for 250!!!! Lesssgo
Great progress so far! Pushing past 200+ takes serious work, and aiming for 250 is the exact mindset needed to get to that top 1%. Keep crushing it!
yes, will do. Thanks for the motivation!!!
no better option🙌
216 is still crazy good 😂 Congrats!
I'm still trying to land my first Contra project, so seeing posts like this is honestly motivating. Hopefully I'll be making posts like this soon too.
If you ever have overflow AI/backend work, I'd love to help. Portfolio:
Thank you. Keep hustling and you will eventually land a project
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
Trending
Claude
Claude has entered the design space. How are you using it?
Contra University
Learn from expert creatives how to earn more using next-gen AI tools.
Brand Design
The best brand designers are on Contra. Scroll to see what's trending in brand design. What are you building?
creativeaiflow
Creative AI workflows are evolving. What tools do you use, and what are their strengths and weaknesses?
freelancerlife
Freelancer life is wins, pivots, and everything in between. What’s yours right now?
Related posts
Your app works locally… but crashes after deployment? 😩
One of the most common mistakes I see is forgetting that local and production environments are different.
Before deploying, always check:
✅ Environment variables are correctly configured
✅ Production database credentials are set
✅ API URLs point to the right environment
✅ CORS settings allow your frontend
✅ Build errors are resolved
✅ Authentication works in production
My rule: Never assume that because it works on localhost, it's ready for production.
What’s the most frustrating deployment error you've faced? 👇
devtipsDesktop Apps DevelopmentWeb DesignWeb DevelopmentCursorNode.jsPythonnextjsfullstackwebdevelopment
10 seconds of a hero we're designing & building.
everything is choreographed; the shell scaling in, the phone settling, and a custom webgl depth reveal.
we built it custom for one reason; the same effect lives in the brand's motion videos (That we are also working on).
goal is: brand should speak the same language everywhere and look good doing it :)
very good work, nice and clean
Getting this error in Next.js? You’re not alone.
Hydration failed because the initial UI does not match what was rendered on the server.
This usually happens when your server-rendered HTML doesn't match what React renders in the browser.
Common causes:
• Using window or localStorage during server rendering
• Rendering different content based on browser-only values
• Incorrect date/time rendering
• Invalid HTML nesting
My first fix:
Move browser-only logic into useEffect, or make the component client-side when necessary.
💡 Tip: Don't just hide the error. Find out why the server and client are rendering different UI.
Have you encountered this error before? 👇
wow this is helpful tips so far here, thanks.. ❤️