Hacker News
Why platform teams fail (and AI makes it worse)
bad_username
|next
[-]
lowbloodsugar
|next
|previous
[-]
The team is too small because no-one wants to pay for it. Every team that uses it has their own budget to do their own things. Because these teams do application development instead of platform development, they underestimate and undervalue the work involved. They are literally not competent when it comes to evaluating the cost of the platform.
d3p0
|previous
[-]
The guardrail half was harder, and it failed in a way the article doesn't cover: silently. We require every commit in a PR to be signed. It was written down and enforced by a required check. A contributor's PR still sat for six days, because on a fork the check waited for a maintainer to approve the run and told the author nothing. Nobody was blocked by policy; they were blocked by a guardrail that didn't speak.
We changed the check to comment on the PR with the exact commits, the reason and the two commands that fix it. A guardrail that fails without telling anyone is as bad as a golden path nobody can find.
bad_username
|root
|parent
[-]
Hello, Mr. Opus
andrekandre
|root
|parent
[-]
> The guardrail half was harder, and it failed in a way the article doesn't cover: silently
this too.. its like they didn't even try
d3p0
|root
|parent
[-]
It doesn't seem fair that one grey area usage of ai would put a permanent flag and kill order on anything I post, which appears to be the case for any thing other than this one message thread that created the original flag. Some amount of ai usage should be treated similar to autocorrect and autoformatting which also tends to fail almost as often as it is correct in awkward ways when you start writing in specific and personal ways.