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
I built JobWorth because most job descriptions read like a wishlist. Paste one in and it tells you which skills the job really needs and which lines are just padding. It also hands you a few blunt questions for the hiring manager, which is usually where the fix starts.
Vue 3 and FastAPI, Firebase underneath, Gemini doing the reading. Works with Ashby, Greenhouse and Lever. The free check doesn't need an account.
I'm taking freelance work right now. If you've got an AI feature that's stuck as a demo, that's what I like building.
Try it: https://jobworth.io
More of my stuff: https://heyeddi.com
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
I Built an AI-Powered Quiz Platform in 3 Day Using Only My Phone. The Odds Were (and are) Against Me.
Meet Aicai Quizzes by CFMoon, a quiz creation and exploration platform I built in just three days.
🔗 Try it here: https://aicai.cfmoon.net
Aicai lets you generate quizzes with AI, share them with others, and automatically grade answers using AI, especially useful for open-ended and paragraph-length responses.
But the interesting part isn't just what I built. It's how I built it, and under what circumstances.
1. Building from outside the usual startup ecosystem
I'm not based in the US or another major tech hub. That means dealing with a different set of constraints, from limited access to payment infrastructure like Stripe to fewer opportunities, no access to GoFundMe, Kickstarter, or startup funding and other resources that developers in more privileged ecosystems often take for granted.
Building software is global. Access to the infrastructure surrounding it isn't always so convenient.
2. One person, one laptop, one phone, and AI
I did this entirely on my own.
No co-founder, no team of developers, no marketing department, and no established professional network to lean on. Just my experience as a software engineer, AI tools, and the hardware I already had: an aging laptop and a smartphone.
3. I built Aicai using only my phone. Yeah, why not use my computer? With the little time I have each day, it is hard to sit down and code, so I built it on the go, while on the street, connecting to public WiFi, all while running my already strenuous life.
AI didn't replace my engineering experience. It amplified what I could do with the resources available to me, and it really made the whole thing easier.
4. Almost no runway
I had very little money left to work with. This wasn't a project backed by investment or a comfortable financial cushion.
The Lovable free trial, made possible through Contra Challenges and Lovable, gave me the opportunity to build and ship the product without spending money I couldn't afford to spend.
A big thank-you to both for making that possible.
5. Building while technically homeless
There's one more detail worth mentioning: I'm currently living in a hotel and paying for accommodation by the day.
In other words, I built and shipped a software product while dealing with housing insecurity and the uncertainty that comes with it.
It's very difficult, and I wouldn't recommend it.
Why I'm proud of Aicai
The platform was built with proper software engineering practices and attention to code quality, maintainability, and reliability. Whop, a great platform, handles payments checkout, and Lovable Cloud handles users, registrations and AI features, which I hope to get enough runway to keep it online.
Three days is a short development window, but shipping something meaningful in that time takes more than prompting an AI to generate an application. It takes knowing what to build, making architectural decisions, evaluating the output, and getting the product ready for users, all while dealing with an already difficult life.
Aicai is a small product, but it's also a demonstration of what's possible when willpower beats the odds. That's where my experience as an engineer and tinkerer mattered, I could do it under pressure, under actual constrains and difficulties, and no degree will ever teach you that, only life.
No funding round. No team. No fancy setup. No rich uncle. Just an idea, the skills to execute it, and the willingness to make something with what I had.
This is what I'm building at CFMoon: useful software, built with professional expertise and quality in mind, always.
Explore Aicai: https://aicai.cfmoon.net
🚀Starting fresh?
How about 5 hours free for a verified client → then paid projects.
Would you take that deal to land your first client?
Vote below 👇 and comment your skill if you're in
2 voted
50%
2 voted
50%
4 votes
Closed
Time is the most valuable thing you can get you can't buy it👍
I turned the checks I run on Lovable, Bolt and Replit apps into a small scanner.
Run one command in your app's folder and it lists the gaps that expose data or money, file by file: keys that end up in the browser, the Supabase service role in client code, tables without row-level security, Stripe webhooks nobody verifies, AI routes anyone can call.
It runs locally, has no dependencies, never uploads your code, and masks every key it finds. Add --ci and it fails the build when anything is red.
It is heuristics, not a guarantee. But it catches the things I look for in the first hour of an audit.
The checklist it is built on is free: https://contra.com/products/cTLDQhiJ-the-ship-check-list-what-to-check-before-real-users-pay
What is the first thing you check before a launch?
The service role key in client code is the one I would bet most no code founders have never heard of. Honest of you to call it heuristics. First thing I check before a launch is whether the site says in one line who it is for, which is a different kind of gap but costs just as much money.