Mairu | Lambda Script @lambdascript

Day of building Lambda Script Today was a big “clean up the foundation” day. - Rebuilt our brand site from a freelancer portfolio into a proper company site - Added Japanese + English support - Moved the blog into our own site, including redirects, SEO metadata, and RSS - Reworked Paperman’s pricing around article generation, not reading - Strengthened creator controls and safety rules in Paperman - Added an automation flow that takes a PR closer to merge-ready (human approval still required) - Improved structured logging and fixed a couple of annoying form / tooling issues in our shared monorepo Also found two bugs that passed type checks but failed at runtime. A good reminder: “type-safe” does not always mean “works in production.” Lots of invisible work today, but it makes everything easier to build on tomorrow.

Good morning, everyone. Let’s hack on our projects today. 🚀

@dannypostma I totally get how you feel. I’m basically a master of hesitating before hitting release, myself… Proud of you, man, for gathering the courage and pushing through the anxiety. Salute! 🫡

A friend of mine says that whenever a new model comes out, Claude and Codex both seem to temporarily get worse for some reason. Has anyone else experienced this? I vaguely remember feeling something similar when Opus went from 5 to 5.1, and with Codex as well. 🤔

@heyalizaid Got it, thanks! Yeah, sounds like the model choice makes a big difference. I might start with a smaller plan and give it a try.

Has anyone here used Higgsfield? I’m curious what it’s like to use—especially the output quality and workflow. 🤔

Opus 5.5! youtu.be/1f13Bl1sYkw?si…

The new banner came out so good lol But the line art is cracking me up.

Mairu | Lambda Script @lambdascript

4 days ago

Lambda Script is the name of my independent studio, and I’ve decided to make “Return True.” its slogan. It echoes `return true` in programming, but it is meant to be more than that. To ask questions. To keep thinking. To make things. To try—and listen for what reality gives

0 0 0 55 0

Lambda Script is the name of my independent studio, and I’ve decided to make “Return True.” its slogan. It echoes `return true` in programming, but it is meant to be more than that. To ask questions. To keep thinking. To make things. To try—and listen for what reality gives back. I want it to remain open enough for everyone to find their own meaning in it. Return True.

Another new thing called Jev has popped up. Apparently, it’s an AI built purely for fast decision-making. By ditching the chat interface and handling JSON only, it seems like it could enable a wider range of system designs. Might be useful for things like category classification.

4/4 That investigation found more gate bugs too: grep -q in a pipe could pass after SIGPIPE partial heading matches accepted missing spec sections disposable test repos could mutate the real repo config branches without worktrees could be falsely reported as rebased Guardrails need guardrails.

3/4 The first fix was wrong. It handled normal push-hook cases, but blocked valid pushes from a branch-rebase script. After 8 review iterations, I stopped basing the decision on how the diff was obtained and based it on whether the resulting diff was actually empty. A useful distinction.

1/4 Today I rewrote the multi-agent review flow in lambda-harness. One giant reviewer became several small reviewers: auth, cache, DB, frontend, etc. The reason was simple: as one agent owned more domains, it missed more issues. Smaller ownership scopes made reviews sharper.

I feel like agent reliability keeps improving every day. Static analysis is great, but the pixel-diff visual analysis in particular is really impressive. By combining tools like agent-browser and agent-device with seed data and a worktree branching strategy in your local dev environment, you can fully automate behavioral verification. Feed those results into inline PR comments, and you can plug them straight into an auto-fix loop — the potential productivity gains are honestly hard to overstate. It really feels like we've entered an amazing era. 🙃

Day 9-10 of Paperman #buildinpublic Made a big pivot yesterday and today. → We're making YouTube creator opt-in mandatory. Paperman is evolving into a service that grows alongside creators. It'll stay true to being a "newspaper" that archives the heat and momentum of every video — powering deeper engagement with existing viewers and SEO to reach new fans. I originally built it as a simple scraping tool. I wanted readers to log in and instantly access every article from their favorite channel. But I realized that was the tool I wanted, not one creators could accept. To build something the market truly wants, trust, integrity, and quality have to come first. So creators can turn their videos — their real assets — into detailed, easy-to-read articles, and reach their audience without losing a thing.

developers.google.com/oauthplaygroun…

I had no idea such a useful site existed. As expected of Google. You can easily test Google APIs here.

@tylerhogarth Really! That sounds exciting! I really liked Prisma's DX and ecosystem, so I'll check it out right away! I'm still using Prisma 6, so migrating might be a bit tough 😅

I've liked tsup for a while and used it quite a bit, but before I knew it, tsdown became the recommended tool... I'm embarrassed that I had no idea at all 😭 It's because I tend to avoid making waves and prefer using stable versions. After all, I'm still using Prisma. I suppose I should migrate to something like Drizzle. At least in terms of performance 🙄