How I currently use AIs for research
I thought I'd document how I'm currently using AI tools, both because it's changed a lot in the past month and also in the hope that someone can look at this, be horrified, and tell me all the things I'm doing that could be better.
I thought I'd document how I'm currently using AI tools, both because it's changed a lot in the past month and also in the hope that someone can look at this, be horrified, and tell me all the things I'm doing that could be better. For context, I work as a researcher producing technical research memos and papers. Most projects involve sustained desk research, usually calculations and data analysis in Python, turned into memos or external outputs. My previous posts on far UVC and whole brain emulation give a sense of the kind of work. It's hard to estimate the speed-up from AI exactly, but I'd
Explore this link on the map →related reading
- How I Use Claude Code | Philipp Spiessspiess.dev
- A Guide to Claude Code 2.0 and getting better at using coding agents – sankalp's blogsankalp.bearblog.dev
- When AI builds itself \ Anthropicanthropic.com
- The machines are fine. I'm worried about us.ergosphere.blog
- How we built our multi-agent research system \ Anthropicanthropic.com
- Don’t Outsource Your Thinkingteltam.github.io
- Best practices for Claude Code - Claude Code Docsanthropic.com
- How I'm using coding agents in September, 2025 — Massively Parallel Procrastinationblog.fsck.com
- Vibe physics: The AI grad student \ Anthropicanthropic.com
- Introduction to subagentsanthropic.skilljar.com
- Effective harnesses for long-running agents \ Anthropicanthropic.com
- How I Use Claude Code | Boris Taneboristane.com