infomiho

Did a thing for myself, wanted to share the process.

My primary motivation was: what if I get locked out of my Google account. Secondary motivation: too lazy to migrate to proper self-hosted Google Drive alternative.

It works for me and I like the results I'm getting. The results often include callbacks to rules of thumb from the mentioned books - which I find easier to agree with or dismiss when I see the suggestions it made. In a way, it's a framework for me to "communicate" with the LLMs.

I think you should try finding what works for you, maybe even give my ridiculous prompt a go.

I've been successfully "vibe engineering" with Claude Code for a week now on a side quest at my job. I want the result to be of high enough quality to maybe survive in our codebase long-term, but I don't want to write it myself.

So I've added unit tests, e2e tests, formatting checks to help Claude to self-correct as much as possible. And I make him do a TON of self-review, after each feature I say something like:

> You are a master reviewer, lots of practical experience. Read Clean Code. Great at architecture. Read Effective Typescript as well. What would you comment in a PR review? Type checking MUST PASS, unit tests must PASS, formatting must PASS.

With each review, Claude catches a lot of sub-optimal choices it made which gives me more confidence in the code I get in the end.

Missed opportunity: name it Floppy Bird since it fits on a 3.5 inch floppy disk.

Every time I write a search query like "best tool for X" or "alternative to X", I use Kagi instead of Google. Because Google results for those kind of queries tend to be SEO optimized articles where the first recommended thing is the advert. Or even worse, I get some sort of spam/scam sites that get paid to shill stuff. I think got conditioned with bad Google results to not do it for those kind of queries.

For all other searches, Google seems good enough.

Off-topic but:

body { max-width: 80ch; margin: 2rem auto; font-size: 18px; line-height: 1.5; }