Engineering Manager at @Buffer husband, father of four little monkeys, and happy Latter-day Saint. If you're reading this we should be friends. 👋🏻日本語を勉強します!
So now that I'm writing less code 'by hand', I'm finally trying to properly learn `vim`, since it feels like it'll be less costly in terms of time-commitment.
I got Claude to set me up with a nice neovim setup for webdev (tree view, LSPs), but I'm still weak at vim basics.
I just did that thing where you accidentally send a message to the wrong chat, except instead of a person, I sent a message to the wrong Claude Code session. 🤦♂️
My solution; vibe-code an orchestrator script on my MacBook that builds the macOS version locally, and then uses `ssh` to remotely run the build script on my Gaming PC downstairs (for Windows) and also ssh into WSL running on that same PC (for the Linux version).
AI makes me faster, but it doesn't necessarily make me better.
With my upcoming app Hangar, i've spent a lot of time trying to polish little things to improve the overall design, and UX. It's a bit buzzwordy, but I do feel like "craft" is going to become even more important.
Coming soon: Hangar ✈️
It's a desktop app I've been building for the past few weeks. Fully cross platform with Tauri/Rust. Local-first.
Get ready to organize the chaos of your local dev/projects directory. ✨
Launching next week!
My favorite software for learning Japanese is Anki. It's a free flashcard app that has tons of useful plugins, plenty of helpful guides to help you get setup, and it works on any device!
Just burned way too many tokens trying to fix a bug. The error was cryptic, and no matter how I rephrased the problem, the LLM kept guessing wrong.
What finally worked: asked it to instrument some logging first. Ran the build, pasted the logs back in. Issue was clear immediately
The lesson: if you're going in circles, don't keep retrying the same vague error. Add some logging, get concrete data, THEN go back to the LLM. Real logs > vibes-based debugging.
#buildinpublic
Obsidian uses local files, so all your standard terminal commands work for editing/moving/searching files
what Obsidian CLI adds is everything else:
- interacting with the UI
- Obsidian's internal functions, e.g. base queries
- deterministic results like the "orphans" command
- easily one-shot a personal plugin, now that your agent can access devtools, console, screenshots, eval, etc
See the docs:
help.obsidian.md/cli