DonTheDeveloper retweeted
A somewhat common but strange response to the consumer request for AI disclosures on products is to suggest that if you did this, you should have to disclose all sorts of other things (how many people worked on the product, what other software you used, what hardware it was made on, etc.)
I can understand that some people don't like the idea of having AI disclosures, so they immediately try to think of arguments against it. But respectfully, this one makes no sense.
Product labeling requirements are driven by demand, either from consumers or from competitors. There is no significant cross-section of the public asking to know if a game was made on machines with AMD or Intel hardware. There is no significant cross-section of the industry demanding that their competitors list whether or not they used Adobe Premier.
Product labeling is not about giving you a complete set of information about how a product was made. It's about giving the consumer information that a significant number of them might want to know before making a purchase. Which ones of these get codified can be driven by consumer demand, competitor demand, or - most commonly - a combination of the two.
This is not weird. It's good, actually.
And it's especially good if an industry takes proactive steps to voluntarily label their products accurately, because then they avoid the inevitable alternative, which is that the consumer demand for the missing labeling produces a political movement which ends with mandatory labeling designed by a political body.
DonTheDeveloper retweeted
Maybe we should delete the 99% of stuff that is just wasteful and friction-causing, the main purpose of which seems just to be to increase attack surface.
xitter.cf/unusual_whales/status/…
I'm just starting to get used to the very basics of Godot & Blender and now I want to learn pixel art. I need to focus up, but gamedev is REALLY fun!
I lost count of the number of times I've been called a luddite by people who have no real technical skills.
Personally, I respect people who have taken years to hone their craft (and keep up with it) - regardless if they're an artist, game developer, web developer, etc.
And it's not because they know that skill, but because of who they had to become to push through the struggles of becoming good at it.
You can learn to create a good AI slop workflow in a weekend. It's not a skill.
You don't have to respect the lowest effort people in our society. I think once you accept that, the noise starts to become much less noticeable.
Just tell us when the layoffs are happening.
As I'm building out more developer courses for Scrimba, I'm starting to ask myself more often, after watching this section, what questions would a student still have?
It's such a simple question that I used to overlook in the beginning. It's drastically changed many parts of my courses.
Man, teaching is fun. On a side note, teachers in traditional education deserve to get paid a lot more in the US. There are so many teachers that I know who are REALLY good teachers (way better than me) who just give up because it barely pays the bills - what a sad way to treat people who have the responsibility of preparing the next generation.
No matter how much some choose to let their skills atrophy with an over-dependence on generative AI, you will NEVER become a good software engineer without learning to code first.
Writing code helps you more deeply understand it. Without question, all junior developers should be writing code.
Translation: "Since we're not able to back up our claims about AGI, let's just make humans dumber. That way, generative AI will LOOK like AGI to dumb humans."
DonTheDeveloper retweeted
Vibecoding is the most cucked thing imaginable.
You literally sit in a chair and watch.
No touching allowed.
















