# Ryan Kowalski, Engineering Lead at Clearfield Analytics — read of learns-yo, 2026-05-20

> 9 years writing TypeScript, last 3 leading a 7-engineer team at a 45-person fintech SaaS. We live in Notion specs and Linear tickets. I coach my 8-year-old's Saturday soccer and catch up on dev threads during the 40-minute drive home.

## How I got here

Someone dropped a link in the #tooling channel of a dev Slack I'm in. Message was just "huh, interesting." No pitch, no context. That's actually why I clicked — the people in that channel have decent taste and don't hype. I opened it on my phone during a coffee break, then switched to desktop because the code block looked like it needed real screen real estate.

## What I clicked first

The hero line stopped me: "Pseudocode in. TypeScript that passes review on the first try." Short. Concrete. Doesn't say "AI-powered" or "10x your productivity." I kept reading.

Then the code example. That's the right call — show, don't tell. The input is just a comment block: `// fetch user by id, throw NotFoundError if missing, log the access event`. The output uses `@/lib/db`, `@/lib/logger`, `@/errors` — aliased imports, not some generic `prisma.user.findUnique` from a tutorial. That's the actual job. That's what I'd want to see from a junior whose PR I'm reviewing.

## Where I paused

The spec table. Specifically: "Context: Up to 200k tokens of repo context per translation" and "Privacy: BYO model key, self host the indexer, no training on your code." I read that twice. If true, that's the answer to the question I was already forming. We have a compliance requirement that anything touching our codebase can't be sent to a third-party model for training. Most tools in this space hand-wave that. This page at least attempts an answer. I don't know if I believe it yet, but they knew the question to answer.

## What I distrusted

Two things, one minor, one bad.

Minor: "The code comes out clean enough to pass review on the first try." I've seen a lot of generated code. "First try" is doing a lot of work in that sentence. First try by whom? A senior engineer who knows the codebase, or someone rubber-stamping? I'd want to see a failure case, not just the happy path output.

Bad: I scrolled to "Who this is for" expecting to see something like "mid-sized TypeScript teams shipping weekly" and instead I got this:

> "Tutors with $500K+ revenue, training-program operators, certification course creators with a list"

What? I'm reading a TypeScript translation tool page. That copy belongs somewhere else entirely. It looks like someone copy-pasted from a different product listing and didn't catch it. That's a trust hit. If you can't proofread your own homepage, how careful are you being with my codebase index?

Then I noticed the Fermi math: "$-20,990 Year-1 take-home" and "1 in 9 meaningful-success odds." That's... not for me? I came here as a potential user, not a founder. Suddenly the page is pitching me on adopting a business idea for $99. I'm confused about who this is actually for.

## What would convince me

One real team's before/after. Not a synthetic example with placeholder imports. I want to see: actual spec file from a real codebase, actual output, a screenshot of the PR with the reviewer's approval and zero requested changes. Real repo names redacted is fine. I just want to know the output isn't secretly a polished demo that took 10 tries.

And a straight answer on what "indexes your codebase" actually means infrastructure-wise. Does it embed my source files and send vectors somewhere? Does it run entirely local? "Self-host the indexer" suggests local, but the page also says "embeddings stored on your infra or ours" which is ambiguous. I need that to not be ambiguous before I run this against our repo.

## What I'd ask in an email reply

1. The output in your example uses `db.users.findUnique` — that's Prisma-shaped. If my team uses a custom query builder with a completely different API, how does the indexer learn that? Does it pick it up from usage in existing files, or do I have to configure it manually?

2. "Passes review on the first try" — what's your actual pass rate in the cases where you have data? I get that you're pre-revenue, but you must have run this on real repos internally. What fell apart?

3. The page says you're "taking design partners." What does that mean concretely? Are you looking for someone to pay you, give you feedback, or hand over a repo so you can use it for evaluation? I want to know what I'm signing up for before I reply.

## Verdict: on-the-fence

The core idea is legit and the code example earns a second look. But the page is clearly split between selling a tool to engineering teams and selling a business idea to entrepreneurs, and it doesn't do either cleanly. The wrong-ICP copy in the "who this is for" section is a real red flag. I'd reply to a founder email if it was specific and didn't lead with the Fermi math.

---
*Memo by skeptic persona, generated 2026-05-20. Studio breaks own self-grading loop.*