Prompt Reviews, Shared Sessions, and Why Your Team Should Talk About How They Use AI
Peter Steinberger, the creator of OpenClaw, said something on a podcast recently that stuck with me: he reviews prompts more carefully than code. He asks contributors to attach their prompts to pull requests. He finds more signal in the prompt than in the diff.
I manage an SRE team at Billie. We use Claude Code and Gemini CLI daily. And I’ve noticed a pattern: everyone’s figured out their own way of working with AI, but nobody talks about it. One person has a brilliant technique for debugging Terraform. Another figured out how to use browser snapshots for visual regression. But these tricks stay locked in individual heads.
Obsidian CLI: Why Your AI Agent Just Got 70,000× Cheaper to Run
Obsidian 1.12 shipped a CLI. Buried in a changelog full of CSS tweaks and file explorer fixes, this is the feature I care about most.
I have about 400 notes in my Obsidian vault, synced via Syncthing to a Linux box where AI agents run against it daily. Claude Code, OpenClaw, custom scripts. They search for context, check what links where, pull facts out of my daily notes. And until this week, all of that happened through grep and reading files one at a time.
Closing the Feedback Loop Changes Everything
I refactored some components in our internal admin panel last week. The code looked fine. Tests passed. I shipped it.
Then someone opened it on a phone. Half the layout was broken.
This is the oldest story in frontend development. You change something, it looks fine on your screen, and it’s broken somewhere else. The feedback loop between “I changed the code” and “I can see what happened” has a gap in it.
Google Cloud Finally Gets Native OpenTelemetry Ingestion
I got an email from Google this morning about a new OTLP endpoint. Buried in the usual “no action required” corporate-speak was something I’ve been waiting for: telemetry.googleapis.com — a single endpoint that accepts native OpenTelemetry Protocol for logs, traces, and metrics.
It goes live March 23, 2026.
The old way was annoying
If you wanted to send OTel data to GCP before, you needed GCP-specific exporters. Your pipeline looked like this:
How I Use AI to Automate Daily Planning with Obsidian
I’ve tried GTD, bullet journals, Notion, Roam, and probably a dozen apps I’ve already forgotten. They all failed for me. Not because they’re bad tools, but because I’d always find excuses not to open them.
Obsidian stuck. It’s local-first, plain markdown, fast. But even with Obsidian, I kept abandoning my daily notes. The friction of “open app → find today’s file → remember the format → actually write something” was enough to break the habit.
Less Distraction, More Focus
In case you think the environment full of distraction and context switching introduces such negative effects as reduction of ability to stay focused on a single task for long enough, you’re not alone. No time for long reads, shorter interactions, anxiety and fear of missing out. Yeah, it’s real.
I’d like to share results of my current ongoing experiment highly inspired by this video, which I definitely recommend for watching
RunDeck Set Admin Password
RunDeck is an excellent tool from PagerDuty to automate certain tasks.
Suprisingly, resetting default admin user password in a docker container isn’t easy.
Default username is admin and the password is admin. Apparently, this is not the securest password, and needs to be changed.
To update it in the container, you have create a file
/home/rundeck/server/config/realm.properties with the contents
admin:YourNewPassword,user,admin
though, if you want to be more secure (I assume that you’d want).
Upgrading Rails to 8.1 and fixing incompatible gems
You probably faced similar error.
Could not find compatible versions
Because every version of paranoia depends on activerecord >= 6, < 8.1
and rails >= 8.1.0 depends on activerecord = 8.1.0,
every version of paranoia is incompatible with rails >= 8.1.0.
So, because Gemfile depends on rails ~> 8.1
and Gemfile depends on paranoia = 3.0.1,
version solving has failed.
This means your gem paranoia wants activerecord with version less than 8.1, but you tested and know it should work.
Rails Suppressor Pattern
While grokking through Rails source code, one pattern caught my eye, namely Suppressor.
Here is the full listing, and as you could spot, it’s quite concise.
But, I spent some time trying to figure out how it works in the context of ActiveRecord. How does it suppress callbacks and notifications?
Honestly, it took me a while to figure out. Give yourselve several minutes to read through the code. It’s really there!
Chrome Command Palette in Dev Tools
I was today years old when I learned about Cmd + Shift + p command palette in Google Chrome.

Why you might need it?
To enable dark mode emulation!
