grepsedawk

6 ms·

1.
by grepsedawk 2mo ago
Yeah! All the same. I love this pattern.
2.
by grepsedawk 2mo ago
Yeah! Worktrees were already sitting there. Agents just turned them from an occasional convenience into something I use every day.
3.
by grepsedawk 2mo ago
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
4.
by grepsedawk 2mo ago
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.
5.
by grepsedawk 2mo ago
Author here. Parallel worktrees showed me where Git’s isolation ends. Files stayed separate; ports, databases, cache keys, queues, and Compose resources did not. We now share compatible services and isolate names per worktree. Which shared
6.
by grepsedawk 2mo ago
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 i
7.
Process Is a Tool, Not a Virtue(blog.kevingoldsmith.com)
2 points by grepsedawk 2mo ago|1 comments
8.
Questions for the Team During Onboarding(simonwillison.net)
6 points by grepsedawk 2mo ago|1 comments
9.
by grepsedawk 2mo ago
Lol! I was baited into clicking this one. Cute title
10.
by grepsedawk 2mo ago
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
11.
by grepsedawk 2mo ago
This is so sick!
12.
How to Be a Good open-source Maintainer(piechowski.io)
9 points by grepsedawk 2mo ago|0 comments
13.
Google Vibe Coding vs. Agentic Engineering White Paper(kaggle.com)
4 points by grepsedawk 2mo ago|0 comments
14.
by grepsedawk 4mo ago
If you use arch but you are forced to be on a mac for any reason, this will make you hate yourself less.
15.
by grepsedawk 5mo ago
Wrapping these in a TUI is on my list. Haven't built it yet.
16.
by grepsedawk 5mo ago
Good catch. The word boundary syntax isn't portable across platforms. I reverted to the simpler version that works everywhere.
17.
by grepsedawk 5mo ago
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.
18.
by grepsedawk 5mo ago
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.
19.
by grepsedawk 5mo ago
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.
20.
by grepsedawk 5mo ago
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.
21.
by grepsedawk 5mo ago
Good catch, that's better
22.
Why Your Engineering Team Is Slow (It's the Codebase, Not the People)(piechowski.io)
2 points by grepsedawk 5mo ago|0 comments
23.
Git commands I run before reading any code(piechowski.io)
2338 points by grepsedawk 5mo ago|509 comments
24.
Why Your Engineering Team Is Slow (It's the Codebase, Not the People)(piechowski.io)
3 points by grepsedawk 6mo ago|1 comments
25.
Transactal Tests for Rails running outside of rails (react, detox, cypress)(github.com)
1 points by grepsedawk 5y ago|0 comments
26.
Generate RSA Key Using Command OpenSSL Genrsa(piechowski.io)
3 points by grepsedawk 7y ago|0 comments
27.
Don't Use Rails Default Scope(piechowski.io)
1 points by grepsedawk 7y ago|0 comments
28.
by grepsedawk 7y ago
Very happy to hear!
29.
How to Protect Strained, Sore Developer Eyes(piechowski.io)
4 points by grepsedawk 7y ago|2 comments
30.
How to Reduce Developer Back Pain and Tightness(piechowski.io)
1 points by grepsedawk 7y ago|0 comments

More ›