← Back to context

Comment by sph

25 days ago

Elsewhere I called it akin to Bannon's "flood the zone" marketing strategy.

HN is lousy with new accounts (created in the past year) that are overwhelmingly excited for the so-called AI revolution.

9 comments

sph

Reply
hparadiz  25 days ago

Just woke up from half my nights sleep to see what HN is talking about at 1 am pst on a Friday.

Oh look more useless arguing.

People who do things care about the doing more than how the sausage was made.

I do not care how software gets built. Only that it works. Results is the only thing that matters and I hope everyone in this thread internalizes that fact.

  • noodletheworld  25 days ago

    > People who do things care about the doing more than how the sausage was made.

    Then do it. Be successful. Be wonderful. Show us all the great results.

    If you only care about results, then go do the things.

    Why are you complaining? Whats wrong with differing views?

    When people cannot accept other people critiquing AI; that is literally AI psychosis.

    Heres a trick: what is AI bad at? Stop and ask yourself what it really sucks at.

    Nothing come to mind?

    You're living AI psychosis.

    If you can't accept that anything it does is wrong or bad, that you are only successful when you use AI you are, flat out, gas lighting yourself.

    Now go read the comments by recent new accounts about AI.

    Yeah.

    Either there are a lot of bots, or a lot of really really troubled people out there right now.

    • hparadiz  25 days ago

      Your diatribe is irrelevant.

      This account is my real name. I have nothing to hide. The metrics speak for themselves.

      We just had a week with 7 major zero days announced for pretty much every major OS and architecture. Reality doesn't care about your opinion.

      3 replies →

  • fauigerzigerk  25 days ago

    >I do not care how software gets built. Only that it works.

    I mean, I agree on a very high level of abstraction. But my problem is that I need to understand how software gets built so that I can have confidence in my ability to maintain and evolve the project.

    I need to understand whether a feature is easy to add or requires a wholesale rewrite of the entire codebase, which comes with risks. I need to understand how new features affect existing users.

    I also need to understand the economics of the process and the economics of my industry. That means I have to care to some degree about how software gets made, not just whether some specific program works at the present moment.

    If you give me a choice between an implementation that is 100 LOC I can understand and an implementation that is a million LOC that I can never understand, I'm going to chose the former, even if both implementations pass all tests.