Musk leads engineering teams so I assume he has a better sense about what engineers need from AI than most. I think it's a safe assumption, but I could be wrong. My point is he has no sense that an alt-right AI is offensive to most ordinary citizens. I wouldn't expect Musk to have a good sense of that.
I think the intent is to de-amplify topics that produce shallow responses (the kind that can be quickly made and piled on). I still see plenty of those rise to the top of the feed though, so it's more of a "turn down the volume" than "mute".
New technologies that require new ways of thinking are always this way. "Google-fu" was literally a hirable career skill in 2004 because nobody knew how to search to get optimal outcomes. They've done alright improving things since then - let's see how good Cursor is in 10 years.
Current state AI is a best fit for jobs that can be easily verified as correct. In my 20+ years, this is at least 75% of the work I’ve ever done. Maybe 99.999% (I have led a very boring career.)
There’s an enormous amount of value in doing this. For the harder problems you mentioned - most IC SWE are also incapable or unwilling to do the work. So maybe the current state has equivalent capabilities to 95% of coders out there? But it works faster, cheaper, and doesn’t object to tedious work like documentation. It doesn’t require labor law compliance, hiring, onboarding/offboarding, or cause interpersonal conflict.
Is this advice to help them maximize their business, or a personal whine that you want it but don’t want to pay so much?
Only the customers can tell this person if $60 is too much. If yure upset because it’s more than you would pay - say that. Otherwise you’re really just asking for a Porsche at the price of a Honda.
There are design patterns / architectures that data engineers often employ to make this less "sucky". Data modeling is magical! (Specifically talking about things like datelist and cumulative tables)
> pretty much every advancement in automation across history has sacrificed some fidelity and craftsmanship. That's the cost of automation
Can you help me think through how this looks when considering car manufacturing? Originally hand made cars were things of craftsmanship, but significantly lower quality and reliability than those produced with tiny tolerances on insane production lines. I'd take a modern car over a handmade one just about any day of the week.
In terms of risk, building a prototype and getting a quick win really de-risks a project. Smart decision makers' world is a game of risk - they have tolerance in some areas, less tolerance in others. If you can materialize a quick win from a prototype, it's significantly less risky that sight-unseen work.
Coders often don't think in terms of a broad investment portfolio, but that's how I've seen good executives phrase things. AI makes it cheaper and easier to build that prototype - I've been loving it for my own projects, because of how quickly I can deliver that first software.
I use Cursor and vibe code this stuff, it works great! I just built a flight tracker (I live in a flight path) that uses a SDR to receive ADS-B info from overhead flights and enrich it with flight info from the local airport, then display in a train station style flippy board. My wife loves knowing where the flights are going and so I display on our magic mirror
I know almost nothing about the underlying technologies, can barely code JS for the front end. But after about 10 hours of coding, I’ve got a very neat little app - it’s something that would have taken me 2 months then become abandonware after I got frustrated.
This was such a positive experience with vibe coding that it restored my love for code. Resulting quality seems pretty decent - maybe 1200 sLOC with good logging, performance, and what I would say is decent pro-am code quality. (IE above the median quality for typical commercial code, I’d bet)
Genuinely curious, what evidence leads you to this conclusion?