Is anybody else bored of talking about AI?
431–440 of 570 posts
Re: Is anybody else bored of talking about AI?
#432Re: Is anybody else bored of talking about AI?
#433Re: Is anybody else bored of talking about AI?
#434Re: Is anybody else bored of talking about AI?
#435The topic of AI triggers people in various ways - anxiety and uncertainty about the future, frustration with excessive hype, and the debate between people on each side of the fence. It will calm down once the dust starts to settle and there's some kind of consensus on how the chips have fallen. Also there is an irony that talking about being sick of talking about AI is still talking about AI.
The only thing that triggers me about it peoples inability to understand how a scam works, after falling for such scams the n-th time.
Hyperloop, ubeam, blockchain, Elon musk taking all to mars....
In these line of scams, LLMs are a wet dream...
Re: Is anybody else bored of talking about AI?
#436Earlier quoted context omitted.
When C arrived, programmers wonder how software devs would look like when they won't have assembly experience. Then the same happened with languages that managed memory. And with IDE that could refactor your code in a click and autocomplete API calls. And with Stack Overflow where people copy/pasted code they didn't understand.
I reckon there's a limit to how long this abstraction can go on before not understanding underlying mechanisms will seriously hamstring you.
But with that said, those who learn the underlying mechanisms will always be able to solve more problems than the folks who don't. When you know the lower pieces, your mental model tells you when and where the higher level pieces are likely to break. Legit superpower.
Re: Is anybody else bored of talking about AI?
#437I "tried" Claude the other day. It gave me 3 options for choosing, effectively, an API to call an AI. The first were sort of off limits, b/c my company… while I think we have a Claude Pro Max Ultra+ XL Premium S account, it's Conway's Law'd. But, oh, I can give it a vertex API key! "I can probably probably get one of those" — I thought to myself. The CLI even links you to docs, and … oh, the docs page is a 404. But the 404's prose misrepresents it as a 500.
Maybe Claude could take a bit of its own medicine before trying to peddle it on me?
We're on like our 8th? 9th? Github review bot. Absolutely none of them (Claude included) is seemingly capable of writing an actual suggestion. Instead of "your code is trash, here's a patch" I get a long-form prose explanation of what I need to change, which I must then translate into code. That's if it is correct. The most recent comment was attached to the wrong line number: "f-string that does not need to be an f-string on line 130" — this comment, mind you, the AI has put on line 50. Line 130? "else:" — no f-strings in sight.
"Phd level intelligence."
Re: Is anybody else bored of talking about AI?
#438Re: Is anybody else bored of talking about AI?
#439Earlier quoted context omitted.
I reckon there's a limit to how long this abstraction can go on before not understanding underlying mechanisms will seriously hamstring you.
I think we're a long ways from that. But with that said, those who learn the underlying mechanisms will always be able to solve more problems than the folks who don't. When you know the lower pieces, your mental model tells you when and where the higher level pieces are likely to break. Legit superpower.
I would define that as being "seriously hamstrung"
Re: Is anybody else bored of talking about AI?
#440Earlier quoted context omitted.
Spot on take. The people I’ve noticed that say things like “it’s not useful” are the ones who are doing so little they can’t see the value. This isn’t to say there’s not hype. Just that if you’re not seeing big productivity gains you need to make sure you really are an outlier and not just surplus to requirements.
I rarely come across people who flat out say "it's not useful". They exist, but IME they're the minority. Rather, I hear a lot of nuanced opinions of how the tech is useful in some scenarios, but that the net benefit is not clear. I.e. the tech has many drawbacks that make it require a lot of effort to extract actual value from. This is an opinion I personally share. In most cases, those "big productivity gains" are…
This is overly dismissive, there are many things that are possible now that weren't before because writing the code is no longer the bottleneck, like porting parts of the codebase from managed to unmanaged for teams with limited capacity. Writing code is about 1/3rd of the job. Another 1/3rd is analysis, which also benefits from AI allowing people who aren't very good at it to outperform. The final 1/3rd is-
> the effort to carefully design and implement correct solutions to real-world problems.
That's problem-solving - that part doesn't get sped up, and likely never will, reliably.