There is no demand for average anymore. I used to think shipping something decent was enough. Get it out. Iterate later. But decent doesn't cut through. Decent gets lost in the noise. inkStar either has to be the best tool a tattoo studio has ever used, or it's just another app collecting digital dust. No middle ground. That's what keeps me up at night. And also what keeps me building.

We've been building inkStar.app for almost two years now. My girlfriend runs our tattoo studio. I write the code. We both use the app every day. Today we sat down together to rewrite the homepage copy. She'd read a sentence out loud and say "that's not what we do." I'd rewrite it. She'd read it again. "Closer, but nobody talks like that." We spent hours on just the homepage. Didn't even finish it. The words started sounding like us instead of sounding like AI. Like how she'd explain it to a friend who asked what I've been building all year. We'll need a few more sessions. Honestly, I'm looking forward to them.

For months the inkStar website was functional but rough. Pages that didn't match. Copy that tried to say everything and ended up saying nothing AND on top of that, Missing pages. Friday I shipped the rework. Every page redesigned. Blog system live. Full SEO foundation in place. By Saturday, all pages were indexed thanks to RalfyIndex. Then I spent the weekend going through every competitor I could find, pulling the keywords they rank for. 400 keywords on the list now, AND checking out possible sources to build some links. The website is live. Now comes the harder part: making sure the right people actually find it. Stay tuned!

Your customer's customer should never have to install your app. If a tattoo client needs to download something just to book an appointment or sign a consent form, you already lost them. The studio runs the app. The client just shows up.

I used to think great engineers were just really smart problem solvers. Then I started building inkStar. The scheduling assistant, the forensic e-sign system, the offline-first architecture for studios with concrete walls and zero signal... None of that came from logic alone. It came from caring. From obsessing. From wanting the thing to feel right, not just work right. Turns out engineering and craft aren't that different.

If you stop moving on your product for long enough... you stop believing in it. I've felt that with inkStar. Two weeks of no commits, no updates, no nothing. And suddenly it starts feeling like a mistake instead of an unfinished bet. The code didn't change. My conviction did.

I think the current gate keeper for AI is the quality, since most AI software is just low quality slop and imo enterprise software has the biggest barrier with all the legal requirements, architecture and special needs, per industry etc. Sure AI can one shot a ToDo app... because there are more ToDo apps out there than humans on this planet... But software is NOT simple 😂especially specialized one that most companies require. Saying that AI will replace all devs is like saying a calculator makes understanding math obsolete 😂 I just don't buy it. I might be biased, but I just can't imagine a world where AI is doing 100% of the work. Whoever thinks that, must be a junior, not a dev or is trying to sell you AI.

Knowledge. Reputation. Capital. Those are the three things you're actually building when you ship in public. Not followers. Not likes. I forget that sometimes. Especially on the days when I get 19 visitors and one bot signup. But every post, every honest failure, every real number I share? That's compounding. Slowly. Quietly. For real.

Truth bomb: There's no point in learning custom tools, workflows, or languages anymore. Unless they're YOUR tools. YOUR workflow. YOUR product. I spent years mastering client-specific systems. Internal tools that only existed in one company. Workflows that died the moment I left the project. All that knowledge? Worthless now. But the time I spent building inkStar? Learning how MY product works? How MY customers think? That compounds. Every bug I fix makes me better at fixing the next one. Every feature I ship teaches me what users actually need. Stop optimizing for someone else's stack. Build your own thing. Even if it's messy. Even if it's small. Because the only knowledge that truly scales is the knowledge you OWN.

Everyone's talking about AI replacing jobs. Here's what I'm seeing instead: AI is exposing who was doing robotic work all along. If your job is following the same process every time, clicking through the same steps, filling out the same forms... yeah, that's getting automated. But building a product people actually want to use? Figuring out why your onboarding flow feels broken? Deciding which feature to ship next based on a gut feeling from watching your girlfriend use the app? That's not robotic. That's human. AI writes my boilerplate now. Generates my docs. Speeds up my CSS. But it doesn't know that tattoo artists need appointment swapping because clients run late. It doesn't feel the difference between a dashboard that works and one that feels RIGHT. Robots are replacing the robotic jobs. The rest of us? We're just getting faster.

A customer forgot their access code to fill out a consent form. Called the studio. My girlfriend texted me mid-session: "Can you reset this somehow?" Fifteen minutes later I committed a feature that lets you reset a contract's public access code from the app. That's what building your own tool feels like. The bug report comes from the next room.

What you ship is an honest reflection of who you are. Not the roadmap. Not the vision doc. Not the landing page copy. The actual product. The edge cases you handled. The ones you didn't. The onboarding you kept putting off. All of it adds up to a portrait of the builder. Kind of terrifying when you think about it.

A good demo makes someone fall in love with the product first. The rational justification comes after. I keep forgetting this. I'll spend days on the encryption layer, the rescheduling logic, the overlap detection. Features that are genuinely good. Features that matter. And then I show someone the app and lead with the technical stuff. Eyes glaze over instantly. Show them the feeling first. The architecture can wait.

Yesterday I was on a high. Shipped a feature, deployed a new project, felt like I was flying. Today I opened a blank documentation page. Then another. Then another. Fifty more after that. Each one needs screenshots, examples, edge cases explained. In two languages. Building the product is the part I love. Explaining the product is the part that sells it.

shipped inkStar's contracts v2 feature a while back felt like i built something incredible then realized: users will never see 90% of the work the encryption layer? invisible the security architecture? invisible the edge cases i handled? invisible they just see some inputs and a signature field building the right way takes 10x longer than building the visible way and nobody will ever know the difference except me. and the one time it prevents a disaster.

When you're building alone, every screen is a small emergency. You need the payment page done. You build a tile that links to the appointment. It works. You move on. Two months later you need the same thing on the contract page. You build it again. Slightly different. You move on. Six months in, you have a dozen screens that all do similar things in slightly different ways. Nothing is broken. Everything just feels... off. This week I finally stopped. Went through every page. Found all the places where I'd solved the same problem differently. One component. One style. Every page. Three days of work that added zero features. But when I opened the app after, it felt like a different product. Not because anything changed. Because everything finally agreed.

Nobody talks about the work that makes an app feel like one app instead of twelve screens stitched together. Unifying components. Making every page feel like it belongs to the same product. It's invisible. And it's everything.