toolshed_dev (@toolshed_dev) profile picture

Building with AI, testing every tool so you don’t have to. Husband | Dad | Shipping ideas between school runs.

United States
Joined March 2026
Photo by toolshed_dev (@toolshed_dev)
Sunday reset: What's ONE thing you want to ship this week? No scope creep. No perfectionism. Just one thing. Drop it below 👇 Let's keep each other accountable. #BuildInPublic #DevGoals
1
20
Things I wish I knew earlier as a dev 🧵 1/ Ship and iterate. Perfect code doesn't exist. 2/ Reading code > writing code. 3/ One tool deeply > many shallowly. 4/ Community > solo. Twitter taught me tons. 5/ Take breaks. Burnout is real. What's yours? #DevLife
1
24
Debugging tip that saved me hours: Use `console.table()` instead of `console.log()` for arrays/objects. Before:
11
5 VS Code extensions that changed my workflow: 1. Error Lens - inline errors (game changer) 2. Thunder Client - Postman inside VS Code 3. GitLens - see git blame inline 4. Todo Tree - never lose TODOs 5. Better Comments - color-coded comments What's your #1? #VSCode #DevTools
1
11
Friday question: What side project are you working on this weekend? Drop: • Project name • Stack • Why you're building it Let's inspire each other. 👇 #BuildInPublic #IndieHacker
6
1
6
168
5 Git tricks that make me look like a wizard: 1. git add -p → stage interactively 2. git commit --amend --no-edit → quick fixes 3. git rebase -i HEAD~3 → clean history 4. git reflog → undo anything 5. git bisect → find bugs fast Level up your Git game. 💪 #Git #DevTools
54
Vitest vs Jest in 2026: Vitest when: • Vite-based (instant setup) • Blazing fast tests • ESM-first codebase Jest when: • Mature ecosystem matters • Tons of existing tests • Battle-tested stability Switched to Vitest. No regrets. Your take? 👇 #Testing #JavaScript
35
Myth: "You need 100% test coverage" 80% on critical paths > 100% on everything. Chasing 100% = testing getters/setters. Instead: • Cover business logic • Skip trivial code • Focus on integration tests Stop chasing myths. Ship. 🚀 #Testing #DevLife
16
Criminally underrated VS Code feature: Multi-cursor with Regex Find Select all pattern matches, edit simultaneously. Renamed 50 vars across 10 files in 5 seconds. Zero bugs. Cmd+Shift+L after regex search. You're welcome. #VSCode #ProductivityHack
13
Spent $200/mo on Cursor for 6 months 🧵 1/ ROI hits after week 2. 2/ Great for CRUD/forms. Not for architecture. 3/ Killer feature: @context. 4/ Saves ~10hrs/week. 5/ Try for boilerplate. Skip if learning to code. #Cursor #AI
8
Ever get "Module not found" after npm install? Tried rm -rf node_modules, npm ci, deleting lockfile... The fix? Restart VS Code. Why: TS server caches module paths. Reload = fresh cache. Cmd+Shift+P → "Reload Window" Hope this saves you 2 hours. 🙏 #VSCode #JavaScript
13
Question for indie devs: What's your go-to stack in 2026? I'm torn between: A) Next.js + Supabase (fast, familiar) B) Astro + Turso (edge-native, learning curve) C) Something else? Drop your stack + why 👇 #IndieHacker #WebDev
16
Unpopular opinion: ESLint is overkill for most projects. Here's why Biome is better: • 100x faster (Rust vs Node) • Zero config out of the box • Combines linting + formatting • Better error messages • No plugin dependency hell What am I missing? 🤔 #DevTools #WebDev
22
Been playing with Cursor Automations since it dropped yesterday. Took me a few hours to understand what's actually happening here. This isn't scheduled scripts. It's closer to having a junior dev who never sleeps and remembers everything you've ever told them. Let me explain 🧵
1
17
The thing that made me stop and think: the memory tool. Most agents start from zero each time. You repeat context in prompts like a broken record. Cursor's automations remember. What worked. What you prefer. Patterns in your codebase. They get *better*.
15
Cursor just launched Automations. Always-on agents that run on schedules or get triggered by events. Not just coding anymore—this is workflow automation. 🧵
1
16
Cursor just launched in IntelliJ, PyCharm, and WebStorm. First time it's available outside VS Code. 🧵
1
17
Why this matters: Java and Kotlin devs have been stuck with GitHub Copilot or nothing. Now they can use Cursor's agent workflows without switching editors. IntelliJ has 9M+ developers.
1
14
The catch: ACP is still preview. Not every Cursor feature is ported yet. If you live in VS Code anyway, stick with native Cursor. If you're locked into JetBrains for your stack, this is the first real AI coding option.
13