I feel like there's a bit of AI psychosis in this particular post.
>"These are tools which burn vastly more tokens, but are also quickly becoming daily drivers for the work carried out by extremely well-compensated professionals."
>"Somehow this fragment turned into headlines like Uber’s COO says it’s getting harder to justify the money spent on AI tokenmaxxing, because the market for stories about AI failures remains enormous."
Yes, it's just the yearning for AI failures. It couldn't possibly be runaway costs, record revenues, and massive layoffs. It couldn't possibly be that these tools are lighting dollars on fire by people already paid significantly well and not producing any increase in "value" for it (I recognize that output is 100x but outcomes are flat by all measures).
1) Daily, there were 2-3 very active ones in my small town. Procomm Plus was what I used the most in DOS. This was also a stepping stone to IRC. It got to the point I was doing chores to pay for a second phone line for my bedroom.
2) The phone numbers were in a little ad box in the newspaper one time.
3) Most people seemed to bounce around to each BBS but there were communities within each that also seemed to stick there. I expect that was partially due to relationships that people had with the sysops.
4) It was a small East Texas town, so people were generally friendly. We were just kids, like 12 years old, having political discussions with adults. People would also trade or offer up gear they had. I remember inviting a high school guy over to my (parent's) house to install a 28.8k modem for FREE because he had upgraded to 56k. He just gave it to me for nothing. As far as I knew people just treated each other like people. I don't recall ever knowing I was being excluded from something because of my age. For a while there were monthly meetups at a local pizza place.
5) I wasn't interested in programming back then. I remember a lot of talk of hardware, mostly modems, one guy trying to convince every Amiga was the future, file sharing/warez (I downloaded Duke Nukem 3D from a BBS in 5MB zip files), chess and other games over FidoNet.
I'd choose a different word for the title of Hoard Things You Know How to Do. Hoarding is the opposite of what we want to do but I get from reading the section you mean create a collection that you can draw upon. IMO "Share" is a much better word choice.
That's what he was saying. Wall Street (the stock market) are people's "pensions" now because everyone has a 401k or equivalent so their retirement is tied to the market. Thus, these companies are betting America's collective retirement on AI...
Thanks for the response, I appreciate it. I absolutely agree with you about CS education. I went to school to learn how to learn. So, the best-case outcome is everyone has A Young Lady's Illustrated Primer available to them. At that point I suppose to really does live with the individual as to whether they want to see how much potential they really have.
None of these articles address how we'll go from novice to expert, as either self-taught or through the educational system, and all the bloggers got their proverbial "10k hours" before LLMs were a thing. IMO This isn't abstractions, the risk is wholesale outsourcing of learning. And no, I don't accept the argument that correct and LLMs errors is the same as correcting a junior devs errors because the junior dev would (presumably) learn and grow to become a senior. The technology doesn't exist for an LLM to do the same today and there's no viable path in that direction.
Can someone tell me what the current thinking is on how we'll get over that gap?
Thanks for the follow up. I can see the value in trying to look at the chained read - search - write or similar patterns to alert the user. Awareness of tool activity is definitely helpful.
Agreed. If someone could help answer the question of "how" I'd appreciate it. I'm currently skeptical but not sure I'm knowledgeable enough to prove myself right or wrong.
But, it just seems to me that some of the 'vulnerabilities' are baked in from the beginning, e.g. control and data being in the same channel AFAIK isn't solvable. How is it possible to address that at all? Sure we can do input validation, sanitization, restrict access, etc. ,etc., and a host of other things but at the end of the day isn't it still non-zero chance that something is exploited and we're just playing whack-a-mole? Not to mention I doubt everyone will define things like "private data" and "untrusted" the same. uBlock tells me when a link is on one of it's lists but I still click go ahead anyways.