grepsedawk
Re:Setup Script Should Support Git Worktrees
on Tuesday July 28, 2026 @03:11PM (#49088525)
Yeah! All the same. I love this pattern.
Re:Setup Script Should Support Git Worktrees
on Tuesday July 28, 2026 @02:54PM (#49088300)
Yeah! Worktrees were already sitting there. Agents just turned them from an occasional convenience into something I use every day.
Re:Setup Script Should Support Git Worktrees
on Tuesday July 28, 2026 @02:54PM (#49088293)
Love it! Same here. bin/ is a convention I picked up from Rails and thoughtbot over the years. I also have bin/staging and bin/prod for data fixes, deploy helpers, and querying the DB, alongside bin/test and bin/dev.
Re:Setup Script Should Support Git Worktrees
on Tuesday July 28, 2026 @02:41PM (#49088147)
Actually no, sat down and wrote it out. Did some AI proofreading but applied the suggestions by hand. Would be interested to hear what parts were painful.
Re:Process Is a Tool, Not a Virtue
on Thursday July 09, 2026 @06:01AM (#48843434)
I audit engineering teams for a living and see this constantly: a 6 person team running ceremonies lifted from whatever 400 person org the founders came from, and nobody can say what coordination problem any of it solves. Adding a process is easy, killing one is somehow a whole political project.
Questions for the Team During Onboarding
Re:Tripping on Acid
on Wednesday July 08, 2026 @06:42PM (#48838349)
Lol! I was baited into clicking this one. Cute title
Re:Cloudflare Drop
on Wednesday July 08, 2026 @06:27PM (#48838205)
This is pretty cool, thanks for sharing.
It really enables less tech savvy users. It would really enable frontpage/dreamworks-like flows for some people
Re:Decoding the obfuscated bash script on a Uniqlo t-shirt
on Wednesday July 08, 2026 @06:25PM (#48838187)
This is so sick!
How to Be a Good open-source Maintainer
Google Vibe Coding vs. Agentic Engineering White Paper
Re:
on Saturday May 09, 2026 @09:55PM (#48080241)
If you use arch but you are forced to be on a mac for any reason, this will make you hate yourself less.
Re:The Git Commands I Run Before Reading Any Code
on Thursday April 09, 2026 @04:20AM (#47700726)
Wrapping these in a TUI is on my list. Haven't built it yet.
Re:The Git Commands I Run Before Reading Any Code
on Thursday April 09, 2026 @04:17AM (#47700694)
Good catch. The word boundary syntax isn't portable across platforms. I reverted to the simpler version that works everywhere.
Re:The Git Commands I Run Before Reading Any Code
on Wednesday April 08, 2026 @09:19AM (#47689836)
Sure, normalizing by size would be more precise. But this is a quick gut check to know which files to look at first, not a metric.
Re:The Git Commands I Run Before Reading Any Code
on Wednesday April 08, 2026 @09:18AM (#47689831)
Fair point. I skip lockfiles, changelogs, and generated code. The first application file on the list is the one that matters. Should have been explicit about that in the post.
Re:The Git Commands I Run Before Reading Any Code
on Wednesday April 08, 2026 @09:07AM (#47689658)
Only two of the five depend on commit messages. Churn, authorship, and velocity work regardless. Even teams with terrible hygiene write "fix" when something breaks.
Re:The Git Commands I Run Before Reading Any Code
on Wednesday April 08, 2026 @09:06AM (#47689646)
Big projects tend to self-correct. These commands hit differently on private codebases with 3-10 contributors, where high-churn usually means one person patching the same thing repeatedly.
Re:The Git Commands I Run Before Reading Any Code
on Wednesday April 08, 2026 @08:58AM (#47689555)
Good catch, that's better
Why Your Engineering Team Is Slow (It's the Codebase, Not the People)
The Git Commands I Run Before Reading Any Code
Why Your Engineering Team Is Slow (It's the Codebase, Not the People)
Transactal Tests for Rails running outside of rails (react, detox, cypress)
Generate RSA Key Using Command OpenSSL Genrsa
Don't Use Rails Default Scope
Re:How to Protect Strained, Sore Developer Eyes
on Saturday January 04, 2020 @01:58PM (#21956637)
Very happy to hear!