Contra - A professional network for the jobs and skills of the futureAI is showing up in more and more software tools and it’s unlocking wild possibilities for non‑de...
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
AI is showing up in more and more software tools and it’s unlocking wild possibilities for non‑devs to build things they’ve always dreamed of. But even the best no‑code AI tools aren’t magic. They generate code fast, but usually with some flaws. If you’re building with AI, here are a few things to keep an eye on.
3 Common Pitfalls for in AI‑generated software
Security
AI often writes code that looks safe but skips basic checks or exposes info it shouldn't. Review security before sharing with users.
Edge cases
Everything works on the “perfect path,” then falls apart with any variation. Make sure to test the range of real-world scenarios.
Data quality
AI can base features on false assumptions or bad data, which leads to issues later. Double-check the data your features rely on.
Photo Credit [Gratisography]
Then: 1 month, 1 template.
Now: 1 week, 15 templates.
Same designer, different workflow.
I wrote up how I built no-code.supply: fifteen website templates, each with its own brand, in HTML and React, and some in Framer too. Claude Code did most of the typing. I did the directing.
Context-switching across editors, manual boilerplate coding, and opaque agent execution often turn software development into a tedious chore.
With Mainline, we structured a high-contrast digital workspace that makes automated code editing, performance benchmarks (12.5M+ lines of code processed), and tool ecosystem integrations (GitHub, Linear, Slack) effortlessly scannable across desktop, tablet, and mobile displays. Curious how we balanced deep developer data with a modern high-tech aesthetic?
Click the Case Study link below to explore the complete design process and component breakdowns! 💻⚡️👇
An AI-built app can work perfectly while any stranger can read its customers' data. Nothing on screen shows it.
Ask whoever built it: which tables hold user data, and what stops a logged-out stranger from reading each one? A good answer is a list. "It should be fine" means nobody has checked.
Andrés, this is the check most founders never run, because nothing breaks until someone looks. Asking for the list of tables and who can read each one is a test any owner can do without writing code. Row level access belongs on the launch checklist, not the cleanup list.