The outrage is a tool and there's always competition for power. "Caesar's wife must be above suspicion", because suspicion, whether it's based on genuine outrage or not, is a liability that will be explored.
That concern has merit though, because living cost has become a problem and middle class is responding by having less children, so while we are in peak population, the population is growing older, which is an indication of future population decline.
I read all of these comments and was feeling absolutely outraged. The more I read about the actual case, the less I felt that way. He wasn't just some random guy screwed for handling a landing page and customer support, he did that and:
- Operated rom-bank.com, which provided downloadable libraries of >10k ROMs for the users
- Handled additional product marketing sites, distributor reviews, and advertising.
- Received ~$320,000 in direct payments and website ad revenue, which he fully knew came from this company selling pirating hardware/software as he operated the above to enable them to do so
- Probably more, I lost interest in trying to find actual details over repetition of minor pieces of it
This operation made 10s of millions, he made hundreds of thousands and clearly knew what was going on for many years. I'm not saying I'm happy with the punishments handed to him, but I also don't buy the claims he was just some dude that got fucked out of left field because Nintendo was pure evil (emphasis on the pure). I still feel like they could throw the dude a bone at this point though, but maybe the popular 5 minute take is already so set in people's minds that Nintendo just sees bringing the topic up in people's minds again as a massive liability for backlash. Or maybe they just don't care and wanted more. Either way, he's no martyr for those who just want fair use of what they buy and it doesn't make me hate Nintendo.
320k for the period of time he worked for the group amounts to a meager 44k a year, it's a low salary.
Also piracy doesn't work like that, it's a speculation on damage but no real damage is done. It's not like people stopped buying games and consoles because they could emulate. Quite the contrary, emulation works almost as advertising. Those that stay on emulation wouldn't purchase the console and games anyway, and those that would is always exaggerated in these kinds of plea.
In https://www.theguardian.com/games/2024/feb/01/the-man-who-ow... Bowser says that fighting the charges would cost a lot of time and money and pleading guilty is simpler to deal with, so I would take information from the plea deal with a pinch of salt.
Nvidia losing 50% of its value from its peak means it’s still a $3 trillion company. What if it loses 90%? Then it’s the size of Intel which we generally agree is an important part of the industry.
This seems correct because of the proportions, but a company that's valued at say 600 million isn't the same as a company coming from being valued at 6 trillion and landing on 10% of its value, because of the direction of the valuation. While the former is at 600 million ascending, the later is in a descending trend, which affects trust and momentum.
I could never really bridge the gap between spoken language and execution on a guitar. I approach improvising and playing by intervals and shapes. For me I need to have direct access to the guitar that doesn't pass through language, as if the guitar was my mouth and I'd execute a chord or a melody as if it were a word or a sentence, without thinking about syntax.
This makes it hard to compose and study music, since I take a long time to transpose and navigate the harmonic field, but it's a tradeoff that I need to do, my brain doesn't work otherwise.
> I'd execute a chord or a melody as if it were a word or a sentence, without thinking about syntax
This is exactly the same for me. The guitar fretboard is essentially synesthesia for me when I hear music. I hear a melody and part of my brain feels the shape of the fingerings as I go. It’s been like this for maybe 30 years or so (I started guitar at a really young age.)
I have no idea if this is common for guitar players though (I assume so? If you’re the sort of player that can play solos, you probably already “audiate” sounds via fingering) but it means I can basically always immediately play a song after hearing it once, even if it’s just the basic melody. I also have what I’d call “weak” perfect pitch (I can easily conjure an E in my head and then figure out from there what note I’m hearing via well-trained relative pitch) so often I can get the exact notes right the first time.
One of the reasons why I play a whole lot of jazz standards on different instruments is because it builds that feeling of just "knowing" (if I can hear the notes in my head) what I should play. I find "youtube jam tracks" wholly unhelpful, but I spend a whole lot of time playing to backing tracks for stuff like "All of Me" or "Sweet Sue" and playing the melody in different positions/ registers. I have been finding that a lot better for my playing than doing scales (though I still work scales on instruments where I in a learning phase).
But that feeling of "just knowing" is common among a lot of instruments and players.
I know that if I play some fingering on the clarinet, or jut grab a chord on the pedal steel, or whatever it's going to do what I intend without thinking about naming what I intend to do, just like i don't think about spelling, punctation, or letter position when I type (even though I often need to edit LOL).
So I agree- if I am playing bass with folks I will often just start playing without thinking too much about what notes I am playing beyond trying to decide on the general tonic key of the song.
I've been having success playing as you describe, "ear to hand", and then once I have something I like, hand-writing it in tablature so I can lock in the notes.
Before this, I was _mostly_ remembering the "safe" notes, but the occasional stumbles break the flow badly, and the tabs have helped. Surprisingly, since I started doing this, its helped me memorize the scale and make fewer mistakes, generally.
I ran into that from the opposite side when I attempted to learn the guitar, coming from a background in classical piano and woodwinds: my whole conceptual architecture for intervals and harmonies was based on a linear arrangement of notes, and I could not get my head around the way a guitar wants you to sort of feel the shapes and positions of chords instead. Odd and disorienting experience.
"do you know what's going on" is shallow because I don't know what's going on when I use python. Do you? I mean exactly how the interpreter works, what each optimization is doing and such. I'd guess not in most cases and still it's perfectly acceptable to use technologies that abstract complexity away to a point where the code solution space and how it actually manifests in the hardware are two completely different disciplines.
So I'd expand and say that the line should be drawn at knowing how the architecture works, but also we need a pinch of good faith, because it's not very hard to know when you cross the line of overreaching for AI, and it's usually when you hit a point where your prompts start to look like "previous implementation didn't work, try again" or "that's not what I had in mind" or "bug is still there try fixing again"
I do know the broad strokes of how a Python interpreter works. I’ve written compilers and interpreters before.
But that’s not the important part: I can trust that the people who wrote the Python interpreter understand it, and I have reasonable confidence in their ability to make good judgments within the scope of what it does.
In short, they’re experts. They’ve earned a high degree of trust. I would not worry at all about their use of AI to develop Python, if that’s what they’re doing.
But someone who doesn’t understand how a Python interpreter works cannot meaningfully expect me to trust their vibecoded weekend project that reimplements Python.
But people happily trust unknown packages in NPM. It's a matter of culture and consensus. If this vibecoded weekend project was a Google internal SWE's with 16 agents running complex architected tasks, people would look at it differently, so AI usage isn't a good proxy for quality, but you can feel when there's care in a project.
> But people happily trust unknown packages in NPM.
I mean... I don't, and I don't think anybody should.
> It's a matter of culture and consensus.
Yeah, but I do think trust, confidence, personal reliability are key factors here. Slop wasn't invented by AIs. We used to call them "script kiddies" - people who only knew how to copy and paste.
> but you can feel when there's care in a project.
I couldn't agree more! This is such an important point.
This is a question I'm also grappling with. I undergrad I took C++ classes but my Computer Engineering / Electrical Engineering friends were taking C or assembly classes and there seemed to be a slight undertone that more abstracted languages were "lesser" because you didn't understand things at the machine level. I believe people feel that AI is different from "just another abstraction layer" because of the nondeterministic nature?
It's certainly because AI can make specific technical and aesthetical choices that the user wouldn't normally do, so it's a contextual reproduction of someone else's work being appropriated by the agent.
The problem is that although we do this all the time, sometimes licenses require credits when code is reproduced, which is quite hard given the nature of LLMs and their compressed knowledge.
I think we are trying to squeeze AI into a social structure of credit and reputation that's outdated and doesn't really support how technology is now developed with AI.
Here's how I look at it: I think the question you and OP need to ask is: "What is the work product?" That's what you need to understand.
When you write Python, the work product your name is on is the Python code. You don't necessarily need to understand what the python interpreter is doing under the hood--it's a nice bonus if you do, but you're not a lesser developer if you don't understand it.
When you write C++, your work product is the C++ code. You don't necessarily need to understand assembly or machine language, but it's a nice bonus. You're committing the C++ code to source control with your name on it, so that's what you are claiming to understand.
When you use an LLM to generate code, your work product is not the prompts--it's still the code (that the tool generates). So your responsibility to understand the work product you're signing your name to is to understand the code it produces. That's ultimately what you're responsible for.
Where did you get this 'signing your name to the code' ? If your version control clearly attributes code to an agent, there is no paper trail going back to you claiming fitness for a particular purpose. I am discussing with management how do we understand projects that employ agentic approach and it is not clear at all what the source will be that developer will claim to understand. What is clear is that it cannot be all of the code.
I'm talking figuratively signing your name. Most of us are not actually signing a physical piece of paper saying we understand our code, but when we do a commit or write a PR, we are essentially declaring "I understand and am responsible for the nature of my work." As a professional who takes his work (employment and even hobbies) seriously, I don't think this part is optional.
Any human working on a project needs to be responsible for his own output. We can't just throw our hands up and say "Don't look at me, the agent did it!" just like a construction worker who cuts through a water main can't say "Don't look at me, the excavator machine did it!"
I am not arguing about 'his own output'. If a person wants to assert the copyright over something then it's theirs to be responsible for. If a project wants to gain speed and/or save costs by letting an agent generate some part of the project, then no one needs a human in that part of the loop. Because a human will only slow it down. I think this is the direction where the agentic development is heading.
These kinds of things are still important these days. In my previous employment we had to create security guardrails for content distribution resources in AWS (API gateways, s3 buckets, instances and cloudfront distros) for a standalone CDN. For cloudfront you'd be right to question why put a CDN behind a CDN and the answer is technical debt, so we had to deal with it.
The problem is that cloudfront functions are very limited in code size and execution cycles, and the list of cidr blocks from the external CDN was so long it meant we couldn't do a simple comparison, so we did something similar, representing all cidr blocks and the incoming source IP to a binary representation and used binary search to see if the source IP matched any cidr block range. It's also very hard to estimate correctly if the resulting function would in fact fit the compute budget, because AWS isn't very clear about what a cf function cycle is in practice, so we tested it extensively, with real and synthetic cases to simulate worse conditions.
Sure, if you’re willing to trample on civil rights & use extraordinary social pressure to deride previously mundane activities as equivalent to murder!
I'm surely not and still I think it's overestimated, just like the climate crisis is downplayed, like the health effects of tobbaco, lead and asbestos were hidden, because it hurts quarterly reports to focus effort and thus money on things other than making more money.
reply