fanagra32
> Context: I teach at Princeton and study social media and recommendation systems.
I'm not sure how this context was relevant. Your post was perfectly able to stand on its own feet and convince through content, not through authority. If anything, this "context" removed pondus from it by appealing to authority.
If I look around at (a) politicians and (b) people I respect for traits needed in politicians, then those sets are not fully but largely disjoint.
> Number 1 trait of a politician should be honesty and integrity in my opinion
There are other necessary traits though. Empathy. Diplomacy. The ability to compromise. Keeping an eye on the big picture. Current processes don't always select for those traits and there are tons of BS-ers and populists out there while I see people with the desirable traits outside politics and not having any desire to get involved. Putting a camera over their head 24/7 is not going to improve that.
Also, add redundancy so that if something is read out wrong then there is guaranteed to be no match. Error-correcting codes have been around for centuries (well, almost). Simplest way to do this is to add a fourth digit which acts as a checksum. Nobody needs to know this, but it will make the legal combinations very few in the space of total combinations, so if something is read out wrong you'll notice right away.
Not really.
For swapping to occur, two orders have to be sitting there at the same time with the same last 3 digits and the wrong one has to be picked. So thats one in 2x4096. Every time there is only one order sitting there, the propability drops to 0%. And once there are more orders sitting there, it increases beyond one in 2x4096.
Where the total ends up is heavily dependent on how often multiple orders are sitting there, waiting. It's hard to quantify, but qualitatively we can certainly conclude that the more busy a place and time is, the more likely this is to occur.
Take a peek over to Italian politics and you get a glimpse of what could be coming.
Or Israel.
There are lots of good things coming out of the European Commission and some really great things. Obviously there is going to come some crap to, and a few really really bad things, like this one. I agree that it's tiring to fight those, but there is no sunshine without rain.
In the totality of all politicians out there that you have an opinion about, which fraction of them do you like, in terms of thinking they are the right person for the job? Do you think this fraction would improve with that opt-in scenario implemented?
People complaining that this thing should not say "I" because that would lead users to antropomorphize it is fine, but they should also realize that calling it "AI" has a similar issue by mischaracterizing what this thing actually is. And this article does exactly that, which is pretty sad.
Essentially, GPT is that rando's webpage but with the metadata stripped away that allowed me to make judgement calls about its trustworthyness. No author, no time, no style to see if somebody is trolling.
But I have a feeling for both, which is one of the key components of the skill in our trade.
For idionmatic code, I know the degree to which I'm following how things "should" be done or are "usually" done in a given language. If I'm uncertain, I know that. GPT won't tell me this. Worse, it will confidently claim things, possibly even if presented with evidence to the contrary.
For critical flaws, I know the "dark corners" of the code. Cases which were not obvious to handle or required some trick, etc. I'll test those specifically. With GPTs code, I have no idea what the critical cases are. I can read the code and can try to guess. But it's like outsourcing writing tests to a QA department. Never donna be as effective as the original author of the code. And if I can't trust GPT to write correct code, I can't trust it to write a good test for the code. So, neither the original author of the code (GPT) nor somebody external (me) will be able to test the result properly
Maybe if you are an American. But non-Americans are puzzled when they see 10/03/08 and are told that that's October 3rd, 2008.
Sure it may take a bit more time to get going, but then you'll get it right the first time and learn something along the way. Your copilot example is just another iteration of copy-and-paste some random snippet from StackOverflow in the hope that it will work, but without having seen its context, like from when is the post and what comments, good or bad, did it get.
I'd actually be pretty afraid of a codebase that is created like that.