Frank

Frank

Solo Founder of Four-Leaf.ai
#966338822 followers47 following
🔥 7 day streak
#17,213Last month
0 KP
>10,000All time
39 KP

About

I'm building Four-Leaf, the job search assistant built around you, that organizes and personalizes everything around each job application. The thing that bothered me about existing tools was everyone prepares for interviews by reading answers on a screen. Then they freeze when they have to say it to a real person. Typing "tell me about a time you led a project" and speaking it under pressure are completely different skills. So Four-Leaf does full voice mock interviews. You speak your answers, get feedback on content and delivery. Plus resume tailoring, cover letters, and salary negotiation coaching, all tied to the specific role you're applying to.

Badges

Gemologist
Gemologist
Tastemaker
Tastemaker
Gone streaking 10
Gone streaking 10
Gone streaking
Gone streaking
View all badges

Maker History

Forums

•

3d ago

Most of my Claude Code input tokens weren’t my code

I logged the raw requests from one Claude Code session on a real repo to see where the input tokens actually go. I expected the files the agent read to dominate.

Input was about 123k tokens:

  • ~74% tool definitions

  • ~21% conversation, including a 40 KB file the agent read

  • ~5% system prompt

•

22d ago

What's your "is it safe to ship?" checklist for AI-built apps?

AI can get me to a working app in a day, but "it works on my machine" and "it's safe for real users" are very different things.

The part that worries me is the boring stuff that's easy to miss when the code looks clean and everything runs: API keys sitting in the frontend, auth checks that exist on the page but not on the endpoint, database rules left wide open from the prototype stage, no rate limits on anything. The AI rarely warns you about these unless you ask, and by the time you think to ask, you've already moved on to the next feature.

Right now my pre-launch process is mostly manual and a bit random: I skim through the auth flow, search the repo for hardcoded secrets, and try to break things as a logged-out user. It catches some things, but I never feel fully confident.

I'd love to hear how others handle it:

•

26d ago

Shipping a feature got cheap. Deciding to delete one didn't.

We've got 111 one click apps in Arteza across six studios. Building them was the easy part. With an agent you can take a prompt template to a shipped, working app in an afternoon, so adding one feels free and you stop asking whether it earns its place.

The bill arrives later. A menu nobody can scan. Support load for things almost nobody opens. And every model swap underneath means retesting all of it, because 111 apps sitting on 30+ models is a test matrix, not a feature list.

The mistake wasn't building them. It was not writing the kill rule first. If I'd set a number up front, opened by this many distinct people in 30 days or it goes, removal would be a rule instead of an argument. Now every deletion is a conversation with someone who liked that one.

Vibe coding collapsed the build cost and did nothing to the maintenance cost, so the ratio is worse than it has ever been. Most of the feature bloat I see right now isn't ambition, it's just that saying no got expensive relative to saying yes.

View more