He may well be right, but 'more work' is rarely the answer. The key is doing 'the right work'.
In my experience of AI so far, it's really easy to just 'do more', but there's also very little value in the things people are doing. They don't make you more revenue or improve the product in a meaningful way, or even make the product better to work on. Price's Law[1] or the Pareto Principle[2], or whatever similar axiom you like, suggest that most people aren't actually contributing all that much.
If you apply AI to 'more work' you just end up with the same distribution of good to bad things - and it's highly likely that will lead to more outages, maintenance, and people burning out from the downsides. You have to make sure that the work is actually useful. That's hard, and something AI is terrible at.
> The company has used the amount of code shipped as a major indicator of engineering output.
> That metric is controversial.
An important point that’s buried quite a bit down the article. Grindr seems to be measuring AI success not on features shipped or business value created, but on number of lines of code generated which seems a fairly flaky justification for such a large AI spend personally.
Charles Simonyi Has that story about how a PM began publicly calling out engineering productivity by having them report weekly lines of code, and Simony one week put a negative number in for his line count. The PM stopped doing that afterward.
IMO
I’m getting a lot of small stuff done that I wouldn’t have touched previously. It’s a little bit nicer for users but I would say the difference is marginal
Software developers are famous for lamenting the high time preferences of business forcing them to make poor engineering decisions. The dynamic is common.
Therefore one should not expect higher quality out of many businesses using AI, but you should certainly expect such businesses to highly value AI. The arguments in favor of quality didn't seem to work before, I don't think they will now.
Article is light on details but the premise is something I’ve seen playing out for series A and B companies. Head-counts that were growing as some pretty stable function of revenue growth having a sharp trend change starting about 6-9 months ago.
This article itself is AI slop, of course this is not surprising coming from a website called "ai-updates.net" which I get the impression that might be entirely vibe coded too.
I feel that maybe in the future HN will have to implement a "low quality AI" flag or something(if it has aleady I'm not aware).
I bloody hate the linkedin speak that is used in this article. I am sort of glad that a lot of AI articles use such language, since I was repulsed by it before AI was a proper thing, I don't have to update my filters :))
Oh, another situation where a CEO makes an assertion that quantity is a more important metric than quality? I suppose the high level humor in this is considering the nature of the app itself. Not part of the target market but still rather side eye concerned this could end poorly for the users if the CEO isn’t very concerned with, em, protection.
He may well be right, but 'more work' is rarely the answer. The key is doing 'the right work'.
In my experience of AI so far, it's really easy to just 'do more', but there's also very little value in the things people are doing. They don't make you more revenue or improve the product in a meaningful way, or even make the product better to work on. Price's Law[1] or the Pareto Principle[2], or whatever similar axiom you like, suggest that most people aren't actually contributing all that much.
If you apply AI to 'more work' you just end up with the same distribution of good to bad things - and it's highly likely that will lead to more outages, maintenance, and people burning out from the downsides. You have to make sure that the work is actually useful. That's hard, and something AI is terrible at.
[1] https://en.wikipedia.org/wiki/Price%27s_law [2] https://en.wikipedia.org/wiki/Pareto_principle
> The company has used the amount of code shipped as a major indicator of engineering output. > That metric is controversial.
An important point that’s buried quite a bit down the article. Grindr seems to be measuring AI success not on features shipped or business value created, but on number of lines of code generated which seems a fairly flaky justification for such a large AI spend personally.
Once had a coworker adding lots of safeguards to his code - that i knew would never trip - as he was measured by LOC in his prior workplace.
If you use a wrong metric you get wrong results.
Charles Simonyi Has that story about how a PM began publicly calling out engineering productivity by having them report weekly lines of code, and Simony one week put a negative number in for his line count. The PM stopped doing that afterward.
I’ve never worked anywhere where there isn’t at least 3 times more work to do than there is time and developers to do it.
But when you do that extra 200% of work, would that give you a better output from a business point of view?
Of course not - and, in fact, ruthless prioritisation almost always makes for a better product.
IMO I’m getting a lot of small stuff done that I wouldn’t have touched previously. It’s a little bit nicer for users but I would say the difference is marginal
Software developers are famous for lamenting the high time preferences of business forcing them to make poor engineering decisions. The dynamic is common.
Therefore one should not expect higher quality out of many businesses using AI, but you should certainly expect such businesses to highly value AI. The arguments in favor of quality didn't seem to work before, I don't think they will now.
No way Grindr needs 200 engineers.
Article is light on details but the premise is something I’ve seen playing out for series A and B companies. Head-counts that were growing as some pretty stable function of revenue growth having a sharp trend change starting about 6-9 months ago.
This article itself is AI slop, of course this is not surprising coming from a website called "ai-updates.net" which I get the impression that might be entirely vibe coded too.
I feel that maybe in the future HN will have to implement a "low quality AI" flag or something(if it has aleady I'm not aware).
You can already flag threads
I bloody hate the linkedin speak that is used in this article. I am sort of glad that a lot of AI articles use such language, since I was repulsed by it before AI was a proper thing, I don't have to update my filters :))
this article is just 2 sentences turned into multi page slop using ai lol
Oh, another situation where a CEO makes an assertion that quantity is a more important metric than quality? I suppose the high level humor in this is considering the nature of the app itself. Not part of the target market but still rather side eye concerned this could end poorly for the users if the CEO isn’t very concerned with, em, protection.