Taichi Nakashima

書いた / グローバル展開にむけたアプリと基盤の再構築 | メルカリエンジニアリング engineering.mercari.com/blog/entry/202…

The principles of extreme fault tolerance — PlanetScale planetscale.com/blog/the-princ…

Some secret management belongs in your HTTP proxy blog.exe.dev/http-proxy-sec…

After Automation every.to/p/after-automa…

駿河屋さんとご一緒させて頂くことで、オフラインとオンラインを横断した圧倒的な商品データベースを創り上げ、AI時代の武器とすることでグローバルで勝ちにいきます！！ そんな挑戦に向けて、駿河屋さん&メルカリ 双方で積極採用中です！！ ps.nikkei.com/mercari2605/in…

Mercari DBRE の IC のジョブがオープンしました。ミッションクリティカルな DB 運用や SRE プラクティスにご興味のある方は連絡ください。 apply.workable.com/mercari/j/ACD2… この辺のことをやっているチームです。 pingcap.co.jp/case-study/mer…

a prompt I've been using a lot recently: implement <SPEC> and while you do, keep a running implementation-notes.html file (or markdown) with decisions you had to make weren't in the spec, things you had to change, tradeoffs you had to make or anything else I should know

How Claude Code works in large codebases: Best practices and where to start | Claude claude.com/blog/how-claud…

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.

Introducing Code Intelligence. Give Linear Agent controlled access to your codebase and turn repositories into shared product context your whole team can use.

end-to-end testing > unit tests, in the vibecoding era. A massive, almost entirely agent-coded refactor passed all unit and pre-merge tests but broke a critical feature. It was only caught due to my own excessive paranoia making me run end-to-end tests before the prod deploy.

The agent principal-agent problem crawshaw.io/blog/agent-pri…

Introducing /orchestrate, a skill that recursively spawns agents to tackle your most ambitious tasks with the Cursor SDK. We’ve used it to: - Autoresearch our internal skills, cutting token use by 20% while improving evals - Cut cold start times on our internal backend by 80%

When everyone has AI and the company still learns nothing robert-glaser.de/when-everyone-…

Today @EntireHQ is open sourcing our next release: Skills, teaching your agent how to use the full context the Entire CLI captures behind your code changes: prompts, transcripts, and the decisions behind every commit, alongside your git history. Instead of looking up syntax or running commands yourself, you can ask in plain language and let your agent drive the workflow. This initial release enables your agent to: (1/5) github.com/entireio/skills

A desktop made for one – Geir's Everything isene.org/2026/05/Audien…

よろしくお願いします！