I'm excited to launch Calccompare the all-in-one calculator platform built for e-commerce sellers, freelancers, and everyday users who are tired of spreadsheets and guesswork.
The problem:
Sellers on Amazon, Etsy, eBay, Shopify, and 50+ other platforms often don't know their real net profit until the money hits their bank account. Hidden fees, currency conversion charges, and tax rules eat into margins. Existing calculators are either single-platform, English-only, or bloated with signup walls.
I ve been using AI pretty heavily while building my latest project, and one thing surprised me: the code can look completely fine while the architecture is already going in the wrong direction.
The worst example was multi user data. Everything worked perfectly during testing because I was basically the only user. It was only when thinking through multiple users that I realized how easily AI can make assumptions like there s only one current user or forget ownership checks.
Since then, I ve started giving AI more context before asking it to code:
who can access the data
where the data comes from
what must never be changed
how errors should be handled
what happens when multiple users do the same thing
Getting a working app out of a few prompts is the easy part now. What I keep running into is the day after: the app works, but I don't really know what's inside it.
A few things that bit me after the "wow, it runs" moment:
Realizing I couldn't explain how auth or data storage was actually set up
Fixing one bug and breaking something unrelated because I never saw the structure
Coming back a week later and not recognizing my own project
So I've started doing a short "day 2 pass" before I build anything new on top: skim the structure, check where secrets and user data live, and write a few lines about what the app does and how.