My Current AI Dev Workflow | Peter Steinberger
steipete.me · 599 words · saved by 1 readers
Went fully back to Ghostty, VS Code on the side, and Claude Code as my main driver. Here's what actually works after months of experimentation.
TL;DR: Ghostty + Claude Code + minimal tooling = maximum productivity. Less is more. It’s time for an update on my workflow, which keeps evolving. After going all-in on VS Code, I went fully back to Ghostty for my main setup, with VS Code on the side to look up code and Cursor/GPT-5 for reviews (sometimes also the CLI). I tried Zed, just can’t deal with a terminal that looks like this. Still extremely happy with my Dell UltraSharp U4025QW - 3840x1620 makes 4 Claude instances + Chrome all visible without moving windows. VS Code’s terminal is too unstable, had plenty freezes when pasting…
saved by
related reading
- Shipping at Inference-Speed | Peter Steinbergersteipete.me
- How I Use Claude Code | Philipp Spiessspiess.dev
- How I use Claude Code on large projectslocalcan.com
- Using AI as a Design Engineerjakub.kr
- A Guide to Claude Code 2.0 and getting better at using coding agents – sankalp's blogsankalp.bearblog.dev
- Best practices for Claude Code - Claude Code Docsanthropic.com
- Claude Code is My Computer | Peter Steinbergersteipete.me
- How I'm using coding agents in September, 2025 — Massively Parallel Procrastinationblog.fsck.com
- What I learned building an opinionated and minimal coding agentmariozechner.at
- My Tech Stackjason.ml
- How much I'm paying for AI productivity software (and the future of AI use)jacquesthibodeau.com
- Where Are the Good AI Products?varunshenoy.substack.com