Hacker News: grepsedawk

New comment by grepsedawk in "Process Is a Tool, Not a Virtue"

grepsedawk — Thu, 09 Jul 2026 10:01:52 +0000

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.

Process Is a Tool, Not a Virtue

grepsedawk — Thu, 09 Jul 2026 10:01:15 +0000

Article URL: https://blog.kevingoldsmith.com/2026/03/18/process-is-a-tool-not-a-virtue/

Comments URL: https://news.ycombinator.com/item?id=48843427

Points: 2

# Comments: 1

Questions for the Team During Onboarding

grepsedawk — Thu, 09 Jul 2026 09:47:33 +0000

Article URL: https://simonwillison.net/2026/Mar/6/ally-piechowski/

Comments URL: https://news.ycombinator.com/item?id=48843353

Points: 4

# Comments: 1

New comment by grepsedawk in "Tripping on Acid"

grepsedawk — Wed, 08 Jul 2026 22:42:03 +0000

Lol! I was baited into clicking this one. Cute title

New comment by grepsedawk in "Cloudflare Drop"

grepsedawk — Wed, 08 Jul 2026 22:27:31 +0000

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

New comment by grepsedawk in "Decoding the obfuscated bash script on a Uniqlo t-shirt"

grepsedawk — Wed, 08 Jul 2026 22:25:29 +0000

This is so sick!

How to Be a Good open-source Maintainer

grepsedawk — Wed, 08 Jul 2026 22:21:08 +0000

Article URL: https://piechowski.io/post/how-to-be-a-good-open-source-maintainer/

Comments URL: https://news.ycombinator.com/item?id=48838158

Points: 8

# Comments: 0

Google Vibe Coding vs. Agentic Engineering White Paper

grepsedawk — Wed, 08 Jul 2026 22:16:22 +0000

Article URL: https://www.kaggle.com/whitepaper-the-new-SDLC-with-vibe-coding

Comments URL: https://news.ycombinator.com/item?id=48838111

Points: 4

# Comments: 0

New comment by grepsedawk in "[dead]"

grepsedawk — Sun, 10 May 2026 01:55:31 +0000

If you use arch but you are forced to be on a mac for any reason, this will make you hate yourself less.

New comment by grepsedawk in "Git commands I run before reading any code"

grepsedawk — Thu, 09 Apr 2026 08:20:59 +0000

Wrapping these in a TUI is on my list. Haven't built it yet.

New comment by grepsedawk in "Git commands I run before reading any code"

grepsedawk — Thu, 09 Apr 2026 08:17:25 +0000

Good catch. The word boundary syntax isn't portable across platforms. I reverted to the simpler version that works everywhere.

New comment by grepsedawk in "Git commands I run before reading any code"

grepsedawk — Wed, 08 Apr 2026 13:19:12 +0000

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.

New comment by grepsedawk in "Git commands I run before reading any code"

grepsedawk — Wed, 08 Apr 2026 13:18:50 +0000

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.

New comment by grepsedawk in "Git commands I run before reading any code"

grepsedawk — Wed, 08 Apr 2026 13:07:14 +0000

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.

New comment by grepsedawk in "Git commands I run before reading any code"

grepsedawk — Wed, 08 Apr 2026 13:06:21 +0000

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.