The hardest part wasn't building the game. It was making it PLAYABLE. ๐ฎ While building Shadow He...The hardest part wasn't building the game. It was making it PLAYABLE. ๐ฎ While building Shadow He...
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
Toughest for me was a rich text editor that swallowed the first keystroke when it took focus. No error, no crash, the text just published with the first letter missing. It stayed hidden a while precisely because nothing failed loudly. Now I read the field back before submitting....
That's a great example of a "silent" bug. Those can be much harder to catch because everything appears to be working normally until you notice the actual user experience is wrong. I really like your point about reading the field back before submission sometimes the best...
Only after, mostly. Checks everywhere and you end up with code nobody reads and warnings nobody trusts.
The one I add by default is a read-back on anything that leaves the process: form submit, API write, file upload. Confirm it landed by asking the system again, not by checking...
That's a really valuable lesson. I hadn't looked at verification from that angle before especially the difference between confirming what my code thinks happened and confirming what the actual system received.
The "source of truth" point really stands out to me. For something...
Mine wasn't a crash. It was a scraper that kept working.
I build a tool that reads live car listings and tells people whether a car is worth buying. A site changed its markup and my parser didn't error, it just started pulling the wrong number into the price field. Everything...
This maps onto design work more than people expect: the first version comes together fast, then most of the real time goes into the edge cases and states nobody sees in the demo. Shipping something that holds up under real use is the actual job.
That first keystroke vanishing is such an annoying and silent bug. Reading the field value directly before submitting rather than trusting the visible output is exactly the right instinct.
The gap between built and playable is where product engineering really lives. The best fixes are almost invisible: no broken state, no lost progress, no confusing recovery. Which bug forced the biggest architectural change during Shadow Heist?
Really nice UI direction๐ the visual style and overall presentation look great. If you ever need help with game UI/UX, interface design, or polishing the visual system, feel free to reach out. Iโd be happy to collaborate.๐
Looking to add a premium, tactile feel to your website? โจ
I just finished building this smooth, drag-and-scroll horizontal gallery and wanted to share the preview with the community! It starts as a clean image stack and smoothly expands into an interactive carousel, making it perfect for creative portfolios or service showcases.
Instead of writing complex animation logic from scratch, this is fully coded and ready to go with HTML, CSS, and JS. You can easily plug it into your site and swap the images in minutes using Claude.
Check out the video below to see how it flows!
If you want to use this exact component for your next web project, you can download the complete code package here: Gallery-scroll-animation