Dirty repository design pattern

When you're developing services, database management and query code can bloat your codebase if they aren't abstracted cleanly. The repository design pattern is a useful way to keep the codebase clean without limiting functionality.

I don't like overly sophisticated harnesses.

I have tried out several different harnesses over the years, cursor, devin, claude code, codex, gemini cli, grok bot, and more. I think simplicity is probably the right approach to using generative AI.

All blogs →