Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • this article is just 2 sentences turned into multi page slop using ai lol
    by kbar13
  • Only takes 300 data centres worth of compute.
    by grebc
  • And what do Grindr engineers think of that?
    by ChiperSoft
  • 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).

    by lp4v4n
  • 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 :))
    by xarwex
  • You can already flag threads
    by icantevenhold
  • When AI start to do the activity of 200 Grindr users I'll get more concerned.
    by surgical_fire
  • 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.
    by fhub
  • No way Grindr needs 200 engineers.
    by cryo32
  • Especially considering the quality of the app and how long bugs last.
    by cosmotic
  • AI can also do the work of 500 Grindr CEOs.
    by glimshe
  • 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.
    by shric
  • But when you do that extra 200% of work, would that give you a better output from a business point of view?
    by amelius
  • 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.

    by mw888
  • Yep. If your bosses don't care about the quality of the product then there's no reason for you to care either. Make the AI vibe code slop and ship it. That is what the people signing your paychecks actually want you to do.
    by jormp_
  • > 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.

    by baloki
  • If you use a wrong metric you get wrong results.
    by lousken
  • 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.
    by Krei-se
  • 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

    by onion2k