> Ok but this entire idea is very new. Its not an honest criticism to say no one has tried the new idea when they are actively doing it.
Not really new. Back in the day companies used to outsource their stuff to the lowest bidder agencies in proverbial Elbonia, never looked at the code, and then panickedly hired another agency when the things visibly were not what was ordered. Case studies are abound on TheDailyWTF for the last two decades.
Doing the same with agents will give you the same disastrous results for comparably the same money, just faster. Oh and you can't sue them, really.
Fair point on the Elbonia comparison. But we can't sue the SQLite maintainers either, and yet we trust them with basically everything. The reason is that open source developed its own trust mechanisms over decades. We don't have anything close to that with LLMs today. What those mechanisms might look like is an open question that is getting more important as AI generated code becomes more common.
> But we can't sue the SQLite maintainers either, and yet we trust them with basically everything.
But you don’t pay them any money and don’t enter into contractual relationship with them either. Thus you can’t sue them. Well, you can try, of course, but.
You could sue an Elbonian company, though, for contract breach. LLMs are like usual Elbonian quality with two middlemen but quicker, and you only have yourself to blame when they inevitably produce a disaster.
You surely mean the latency in its embedded terminal and not the code editor, right? I use VSCode’s remote SSH specifically so that code editing doesn’t suck. It really does not.
> I ran into a kernel panic specific to my macbook's hardware. How do I compile a new kernel with some extra debug printlns and boot it to figure out the panic?
1. You can find panic logs in Console.app. macOS writes them into NVRAM and stows away into files on its next boot. That will give you the process and kernel extension that was the culprit, and a stack trace.
2. sudo nvram boot-args="debug=0x122" or something like this will increase log output from the kernel. Those debug prints are probably there already. You can even attach a debugger running from somewhere else, presumably over Thunderbolt on newer machines.
It's more like people are corporations' gut bacteria that are always in dire health because the organism loves junk food of all kinds so much and sometimes is doing drugs too.
it does when the goal is not reading per se but consuming books that are available in audio format as well as printed. and increasingly with better TTS tools any text can be converted into audio.
I read hours most every day for decades but audiobooks never worked for me. After ten minutes, I notice my mind has drifted elsewhere and I didn’t listen to anything that was said. Funny how it takes me lots of effort to concentrate on listening but seemingly no effort to read (or watch movies). I hope my eyesight stays with me for a long time.
that happens to me if i have lots on my mind or if the story is not very engaging. the reading style can also be factor (sleepy voice :-)
i believe part of the issue is that our eyes are our primary source of input. we can control what we see by the direction where we look, or we can close our eyes. we can not control hearing in the same way, and therefore we instead learn to focus or not focus on specific sounds. but that happens much more subconsciously than how we control our eyes, therefore it can happen even if we don't intent to. (ok, when you are deep in thought you can also gaze into nothingness without closing your eyes, but that's less common)
App Store's UX has always been a show of excrement, and its search is wonky as hell. I can't imagine myself use that to discover apps, after having been shoved tons of dreck results up my behind the last time I've tried it.
I'd rather ask for app recommendations on 4chan or Reddit than browse App Store.
reply