Creează un cont pentru a te abona la acest blog și a-i urmări articolele pe pagina Lectură.
-
♠ Problem statement: why did Espanso stop expanding text while its service was running?
-
♠ Just an ordinary day with OpenAI inference via pi: Error: Codex error: Our servers are currently overloaded.
-
♠ Git AI records agent checkpoints in Git notes1, without changing commit messages or repository files.
-
♠ Previously.
-
♠ Today I learned: pi can keep its editor and footer at the bottom of the terminal with fullscreen TUI mode, similarly to Claude Code.
-
♠ Sometimes we simply do not want to activate direnv in a given project.
-
♠ Previously.
-
♠ Previously.
-
♠ Previously.
-
♠ Problem statement: create a git alias / script to diff against the default upstream branch, inspired by chromium depot_tools(7) git-upstream-diff(1): git-upstream-diff — Print a diff of the current branch, compared to its upstream.
-
♠ Problem statement: deleting an ArgoCD Application from Git (GitOps) does not guarantee it will disappear from the cluster.
-
♠ Previously.
-
♠ Problem statement: nested shell quotes made a remote PostgreSQL update harder to run than the update itself.
-
♠ Problem statement: my blog archive was useful, but did not show its posting pattern over time.
-
♠ Problem statement: given my miniflux server with hundreds of RSS feed subscriptions, add emoji country flags to each feed title, representing their country of origin and/or the country they’re associated with1.
-
♠ Problem statement: a coding agent stops when it thinks it is done, not when the thing is actually done.
-
♠ A serendipitous discovery: macOS continuity.
-
♠ Problem statement: I often type commit (only) what you changed in coding agent harnesses.
-
♠ Problem statement: Terrateam opens drift reports as GitHub issues, but terrateam plan only works on pull requests.
-
♠ It’s about time: I added a books page to this blog with a sample of my favorites. ∎ — § — Reply via email #bestof #serenity
-
♠ Yours truly, more than two months ago: As of today, it’s not clear to me whether this approach will stick.
-
♠ Previously.
-
♠ Previously.
-
♠ Previously.
-
♠ Problem statement: a Prometheus pod crash-looped on a full 128GiB volume.
-
♠ Previously.
-
♠ Previously.
-
♠ There’s no need for plan mode.
-
♠ Previously.
-
♠ Previously.
-
♠ From: removals@google.com To: me Subject: Google notice of content restriction Hello, Your review isn’t posted.
-
♠ Today I found myself with 13 open terminals, more than half of them running Pi or Claude Code, the rest with various projects and explorations split amongst work and personal affairs. 13!!
-
♠ TIL: The ThoughtWorks Technology Radar publishes an yearly1 opinionated report about the technology landscape today.
-
♠ More and more I’ve been resorting to LLMs / Gen AI to file feature requests or issues/bugs in upstream repositories.
-
♠ Problem statement: ship a simple change (or commit, or pull request: you name it), then wait for green CI, then remove its local branch and worktree (=clean up).
-
♠ Previously.
-
♠ Problem statement: wait before opening an upstream Helm chart upgrade PR, without putting a timer in the PR workflow.
-
♠ Problem statement: git pull could not autostash files added with git add -N.
-
♠ Previously.
-
♠ Previously.