Change might be inevitable, but I'm not sure your list shows or proves that.
724 karma · joined March 28, 2022
Change might be inevitable, but I'm not sure your list shows or proves that.
I left over a year ago when all of them just became dominated by the same nft and crypto posts everywhere. Couldn't scroll my timeline without seeing fake BBC news articles promising "David Attenboroughs best crypto investment " whatever account I was in. I'm not sure cleaning up a mess they made themselves is really "actively innovating", but I'd agree the country thing would have been interesting back when I used it
Of course if you record created/updated timestamps on both, insert both records in the same order, accidently record the user code in the response data, take backups in between responses, have identifying questions or just don't have that many people responding it's easy/not hard to reverse engineer.
But it's quite possible to do right, I did it quite effectively almost by mistake years ago. Sent a customer survey out with generated codes as identifiers recorded with answers. Before sending reminder emails a script grabbed the codes, marked the customer as responded and wiped the code (so I could just get future responses where code was not null to mark next people off). Although I had timestamps the script meant customers were updated in blocks, there really wasn't any data to link them.
I know because the Boss was not happy he couldn't find out which customer had said what, and I had to point out all the communication (with customers and me) called it an anonymous survey, so why would I have saved them?
So it is possible, just not easy even if you intend it, and it's often not intentional...
I don't trust anonymous surveys either now...
The early release channel is sensible, but if you're a bad actor who's compromised a package you're not going to early release are you, you get it straight out there.
I struggle to remember even relatively simple maths like working out "what percentage of X is Y" so if I write a formula like that I'll put in some simple values like 12 and 6 or 10,000 and 2,456 just to confirm I haven't got the values backwards or something. I've been shown sheets where someone put a formula in that they don't understand, checked it with numbers they can't easily eyeball and just assumed it was right as it's roughly in their ball park / they had no idea what the end result should be.
Then again I've also seen sheets where a 10% discount column always had a larger number than the standard price so even obviously wrong things aren't always checked.
This does make more sense to some of the big claims "95% of our code is ai generated" though. By the logic here a lot of my code would be considered generated for years. ide auto complete on variables, functions, closing brackets, class names etc. Lines changes by linters and formatters to add so much as a comma are not mine anymore. Add in refactoring and my use of ide templates and framework generators to make common files and increasingly small amounts would be considered my written code.
To my designers eye it was the first thing I saw, to him it was nothing.
I still think it's bad and a sign of a change in apple focus/style, but it's clearly not an issue at all for a lot of people.
Said colleague did get cross when he struggled to resize a window though. Turns out inconsistent corners means inconsistent handles. And that is a real problem.
As you get larger you see what you're seeing - not everyone is in on the meetings, knowledge in one person's head isn't shared and people don't know who to ask.
I worked on a simple barcode database setup years ago. Originally it was just a spreadsheet one person 'owned'. Then I made it into a webapp that I and original owner could both add items to - enforcing unique entries and validating checksums (plus an API I could querry). More process, but still a lot was in our heads. When a 3rd person started using it, they added something in lower-case (we always wrote refs in caps) and a variety of case sensitive bugs were found. I had to fix the DB manually and started adding hints and validation.
The more people you have using something the more problems you will have and the less feasible it is to walk everyone through the system in person!
Documentation, make process, make efforts to share knowledge. No way around it.
Which is the issue with almost all studies and statistics, what it means depends entirely on what you're measuring.
I can program very very fast if I only consider the happy path, hard code everything and don't bother with things like writing tests defining types or worrying about performance under expected scale. It's all much faster right up until the point it isn't - and then it's much slower. Ai isn't quite so obviously bad, but it can still hide short term gains into long term problems which is what studies tend to focus on as the short term doesn't usually require a study to observe.
I think Ai is similar to outsourcing staff to cheeper counties, replacing ingredients with cheaper alternatives and other MBA style ideas. It's almost always instantly beneficial, but the long term issues are harder to predict, and can have far more varied outcomes dependent on weird specifics of the business.
(interestingly asking it to make him some friends it gave me more 'original' ideas, but asking it to give him a brother and I can hear the big N's lawyers writing a letter already...)
(Not sure if that's really an apt description though, but then I was out as soon as I read they're neutering one of the usb-c speeds.)
Scoping the Ai to only use the things you'd use seems far wiser than trying to reduce your codebase so it can look at the whole thing when 90% of it is irrelevant.
I'd suspect many places would still respond positively though, especially in the more creative worlds. Almost every creative was that kid once.
Ais are giving you what they get from common patterns, parsing documentation etc. Depending what you're asking this might be an entirely novel combination of commands never run before. And depending on the model/prompt it might solve in a way any human would balk at (push main to origin, delete .git, re-clone from origin. Merged local branches are gone!)
It's like the ai art issues - people struggle with relative proportions and tones and making it look real. Ai has no issues with tones, but will add extra fingers or arms etc that humans rarely struggle with. You have to look for different things, and Ai bugs are definitely more dangerous than (most) human bugs.
(Depends a little, it's pretty easy to tell if a human knows what they're talking about. There's for sure humans who could write super destructive code, but other elements usually make you suspicious and worried about the code before that)
I'd agree that recent features feel a bit unnecessary, but it does need to edit and write files - including system ones (going through however that is authorised). You could sandbox a lot of apps with limited impact, but it would make a text editor really useless. Least privilege principles work best when you don't need many privileges.
It's also not a study of just engineers, it's people across engineering, product, design, research, and operations. For a lot of none-code tasks Ai needs pasted context as it's not usually in a repo like code is.
(And their comments about intensifying engineering workload also aren't really changed by ai copy/paste vs context).
I can do some crud apps where it's just data input to data store to output with little shaping needed. Or I can do apps where there's lots of filters, actions and logic to happen based on what's inputted that require some thought to ensure actually solve the problem it's proposed for.
"Shaping the clay" isn't about the clay, it's about the shaping. If you have to make a ball of clay and also have to make a bridge of Lego a 175kg human can stand on, you'll learn more about Lego and building it than you will about clay.
Get someone to give you a Lego instruction sheet and you'll learn far less, because you're not shaping anymore.
It seems most likely that with pubs not so active over the pandemic, then operating with more socially distanced rules, new pub users just never learnt the "only used in pubs queueing system".
Which is a weird blindspot for the article, where they reference a normal queue as something from "border control", rather than then thing you do everywhere but the pub. Without the introduction to the system they just use the system they use everywhere else. And don't worry it takes longer because it's a convenient time to check your phone.
Which sounds interesting, while also being a massive security issue.
Like many educational tests the outcome is not the point - doing the work to get there is. If you're asked to code fizz buzz it's not because the teacher needs you to solve fizz buzz for them, it's because you will learn things while you make it. Ai, copying stack overflow, using someone's code from last year, it all solves the problem while missing the purpose of the exercise. You're not learning - and presumably that is your goal.
Looking at this device it feels like it shouldn't be hard to have a reusable base with battery and electronics, and a disposable capsule that attaches on top but is replaceable.
Sure the main thing was originally 'just' mapping `.p-4` to `padding: 1rem`. But it's also about grepping the code to see if `p-4` is used so it only builds needed classes. It also needs to work with things like their responsive and state classes so `md:p-4` or `hover:p-4` add the padding only on medium or larger screens, or when hovered etc.
All of which increased to support more and more css features and arbitrary values so `not-supports-[display:grid]:p-[5px]` generates the required code to check if grid is supported and add 5px padding or whatever other values you put in the [].
You can question if that's really a sensible idea, but it is undeniably a pretty complex challenge. Not sure it compares to blender, I imagine that has a lot more maths involved - put probably less edge cases and weird displays odd in X browser bugs.