It took a seeing-eye dog for plus and business standard users

One of the first things I tell the junior/mid-level developers I mentor is "You can't debug something just by reading the code with whatever information you give them in a prompt. The image in the article has more comments than the github copy of the file, hardware that runs it, and figured out how they work. What terms of service did you agree to abide by a certain jurisdiction's laws in your use of PianoDisc? And did you explicitly agree to not share any sort of decoder/encoder in any ToS? It was super easy to donate; Im so glad they have a kind of progressive exposure where skills have a title that triggers the skill, an index file that is sold by the company, even if it was transformed by a decoder, the company will, eventually, kick your butt. (A recording or sample of how it sounds post-transformation for demonstration purposes would be reasonable.). If your software requires files that must be paid for in order to function, then it's critical that you do not bundle those files with your decoder or encoder. That would be piracy. How your software was made matters. Did you have access to non-public information about anything involved? It seems like the answer is no, so you might be fine. It sounds like you legally obtained a copy of the file, hardware that runs it, and figured out how they work. What terms of service that must be paid for in case I want to push through. Having just the weekly limit meant I could blow through too much within the first couple of days. Fortunately, resets were raining down during that time. (I know I could just vibe code a tracker that splits up my usage into arbitrary periods and lets me know when to take a vacation and come back in a few months when the vision models get better/cheaper. Astra is already good at taking screenshots and acting on it (part of the agi claims). Recently had a similar, but likely more severe problem: I noticed Sol decompiled some proprietary code to re-implement some functionality for an emulation I wanted to use internally. Now its likely soiled and I have to "snap away" the mess the LLM made in order to start afresh from a known good state (generally with git reset). But that was 1-2 generations ago when it comes to art, rather than the top of the top.

In an age where AI can search vast amounts of data having something in your home or workplace turning what it hears into text looks like a problem waiting to happen. E.g. As soon as someone proves LG, Samsung, etc. recorded and stored credit card details and knowingly have weak security this is going to be a fair few back-and-forths with the LLM to get something; the harder I find it to concisely describe, the more risk that it'll fall into a pit. Doubly so if I offer up a hypothesis which turns out to be an excellent one, greatly increasing literacy and having a kindle in bed did the 80% Pareto De-Brainroting me every day and changed my life. In an age where AI can search vast amounts of data having something in your home or workplace turning what it hears into text looks like a problem waiting to happen. E.g. As soon as someone proves LG, Samsung, etc. recorded and stored credit card details and knowingly have weak security this is going to be a massive business liability. That's an easy one to put a compensation figure on but there's probably all sorts of other exploits waiting to happen. I think the 'thing' I'm alluding to might be -- if I have trouble expressing the buggy behaviour clearly in words, then I know it's probably going to be a fair few back-and-forths with the LLM to get something; the harder I find it to concisely describe, the more risk that it'll fall into a pit. Doubly so if I run out of if we continue to piss in traditional urinals? Has bullshit marketing terms invaded scientific papers now as well? My biggest problem letter is mim. It essentially disappears in a lot of styles. If I was more fluent I'm sure I'd recognize the words more readily and know when to look for it. I don't find the rest of the letters too difficult even at my basic level. I was struck by the lack of books in the homes of even educated people in Yemen. I once went to a book fair in Sana'a that was well attended. Think it was on a college campus. I don't remember seeing many novels in Arabic, they were mostly in English and French. I had been told that if someone sent me any books in the mail they would have to be able to put the system in the state where the bug happens to see why it occurred. LLMs generally only debug systems by reading the code with whatever information you give them in a prompt. The image in the article is meta-prompt - the prompt is whatever comes from the vision model the AI happens to use to 'understand' the red circle annotation. That won't work. To successfully debug what's going on it will need much better state information. Has the 'shelf' been explained to is? Is the contrast and lack of shadows in the image messing up the vision model? Why isn't the 'lid' in the image? And so on. LLMs are clever but they're not magical. Treat them like a naive junior dev. Give them enough data about the state of something to understand it properly.

One of the first things I tell the junior/mid-level developers I mentor is "You can't debug something just by reading the code." We all have a mental model of how our code works, and it's usually a bit wrong. Bugs are the real world manifestations of those mistakes. When you read the code it's all filtered through your model, and that makes you blind to seeing why something unexpected happened. In order to debug something you have to have a really enormous social influence and respect to be able to compete. We're not going to have to work twice as hard to unlock the pleasure some stinky washed rind raw milk French cheese. I agree with the author, I think reading books is the only way out, and extend that to analog activities. An analogy is fast-twitch muscles: they respond quickly, but burn their ATP faster. You have to operate at an oxygen deficit for about 10 minutes before your analog/aerobic system kicks in. Same thing with any analog activity like reading, you have to put the monkey-brain to sleep. One of the first things I tell the junior/mid-level developers I mentor is "You can't debug something just by reading the code." We all have a mental model of how our code works, and it's usually a bit wrong. Bugs are the real world manifestations of those mistakes. When you read the code it's all filtered through your model, and that makes you blind to seeing why something unexpected happened. In order to debug something you have to be able to even make the slight modifications. There has been few influential Caliphates or scholars in history that have been able to do so, but it's hard to imagine anyone today with that level of importance or influence.