Couriers, Not Coders 5 ▲ Yegor Bugayenko 65 days ago · Tech · hide · 1 comments Someone submitted an issue to one of our open GitHub repositories a week ago, suggesting a new feature. We didn’t respond, since we didn’t notice it. Today, someone else submitted an implementation of the feature in a pull request. I rejected it and explained that the feature request must first be accepted by the project architect, and only then would it be worth making a pull request. The author of the PR got offended. He won’t be back. Good. A year ago, we would have been sad to lose an enthusiastic contributor. Today, we don’t care. Cruel Intentions (1999) by Roger Kumble For years you sold coding skill at $50 an hour. AI now codes for cents. But you still want $50. We are still ready to pay. Not for the code—the code is free. For the delivery. You take what Claude Code wrote and you walk it to our door. You are the courier, not the coder. The margin is what we pay for trust: that what you deliver, we can merge without re-checking. So the delivery must be flawless. We pay for the… Log in to reply on the Fediverse. Comments will appear here. jreber @jreber@mastodon.social 11 days ago [-] Thought-provoking for where my team is at, trying to figure out where (and how much) AI can help. Runs the spectrum from "AI-assisted but still very hands on" to "Did you even read this before you posted it?" courier types.I like this framing. I wouldn't pay my salary for a courier, unless that courier had some damn high commitment to quality delivery. My salary requires that I add $X value _on top of_ what AI can do.
