Trust is not objective. It's built between parties over time by looking at actions and the results of those actions. In other words, it's entirely subjective based on what's happened between the parties involved. You haven't built that trust with AI agents, or the agents have done things to lose that trust (assuming you've tried), but others have. You can't just dismiss their experience as invalid compared to your own.
Not sure why you're being downvoted. CORS is only a browser concept. If you fire off requests from something that isn't a browser (e.g. curl or a python script or whatever) CORS won't do anything. Servers need to validate the origin of requests properly if that's a problem.
The feature that was called is usually bundled in with cors, even if it strictly speaking isn't.
Allowed origins (what was meant) just validates the Origin header to make sure the API is called from a specific domain, and declines the request if not in the list.
The only way around that is not to send the unsubscribe request via the browser or proxy through a server, because the browser will always append the origin header according to the domain the user is on. Which if configured correctly and not proxied, would end in a http forbidden.
Whereas CORS would not even send the request I believe (but haven't verified), because thats essentially a browser feature, not server.
Andrej got famous because of his educational content. He's a smart dude but his research wasn't incredibly unique amongst his cohort at Stanford. He created publicly available educational content around ML that was high quality and got hugely popular. This is what made him a huge name in ML, which he then successfully leveraged into positions of substantial authority in his post-grad career.
He is a very effective communicator and has a lot of people listening to him. And while he is definitely more knowledgeable than most people, I don't think that he is uniquely capable of seeing the future of these technologies.
While I appreciate an appeal to authority is a logical fallacy, you can't really use that to ignore everyone's experience and expertise. Sometimes people who have a huge amount of experience and knowledge on a subject do actually make a valid point, and their authority on the subject is enough to make them worth listening to.
Naming things in the context of AI, by someone who is already responsible for naming other things in the context of AI, when they have a lot of valid experience in the field of AI. It's not entirely unreasonable.
Not claiming anything to be false, just a reminder that you should question ones opinion a bit more and not claim they "know what they are talking about" because they worked with Fei-Fei Li. You are outsourcing your thinking to someone else which is lazy and a good way of getting conned.
This is exactly right. And assuming organizations use the gains to cut headcount rather than boost total productivity, a 10% reduction in white collar employment would still be an era-defining systemic shock to the economy.
AI stops coding being about the journey, and makes it about the destination. That is the polar opposite of most people's coding experience as a professional. Most developers are not about the destination, and often don't really care about the 'product', preferring to care about the code itself. They derive satisfaction from how they got to the end product instead of the end product itself.
For those developers who just want to build a thing to drive business value, or because they want a tool that they need, or because they think the end result will be fun to have, AI coding is great. It enables them to skip over (parts of) the tedious coding bit and get straight to the result bit.
If you're coding because you love coding then obviously skipping the coding bit is going to be a bad time.
For me, it has been the journey. I love being able to say "do this" and just magically have it done, then looking over the result and saying, "well not exactly like that, I actually want it to be a little more like this." I am slowly vibe-iterating over what I hope is a solid platform, and it's been a lot of fun
> For those developers who just want to build a thing to drive business value, or because they want a tool that they need, or because they think the end result will be fun to have, AI coding is great. It enables them to skip over (parts of) the tedious coding bit and get straight to the result bit.
Then they aren't programmers anymore, are they? We don't call people using no-code platforms "programmers" and we wouldn't trust them one bit to review actual code.
AI is simply the new no-code platform, except that the scope of what it can do is much larger while the reliability of what it produces is much lower.
Right not coding with AI requires a lot of skill in understanding where the AI is going wrong, so it's still coding. Someone who can't code isn't going to make a good app with AI (although a 'working' app is definitely possible.)
In the future though, sure,it'll be possible to build a decent app without ever seeing or understanding the code.
> The customer/user can't tell the difference between a good working app and a poor working app.
Come on man, this is the whole reason Duolingo was people's favourite language learning app, or people claim they like iPhones over Android phones or Photoshop over Canva. These apps and devices all work, but which one is good or better is a debate. People have preferences; some apps in a category are easier to use than others, and some apps have branding that signals status. Now, those things become more important in differentiating your app than "It does what it is supposed to do". Until now, just getting an app to do what you wanted it to do was a competitive advantage, that's becoming a smaller advantage day by day
The problem is that the styles for something can be defined in multiple places, and that makes it hard. Especially with CSS and (potentially) having specificity issues if things aren't managed well. Having them as a part of the component means that problem goes away.
reply