Different type of creator, different type of bugs. I'd assume a human giving me a way to delete merged branches has probably had the same issue, solved the same problem and understands unspecified context around the problem (e.g protect local data). They probably run it themselves so bugs are most likely to occur in edge cases around none standard use as it works for them.

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)

A utility meant for viewing data? I don't think you understand what a text editor is.

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.

I’m not sure I understand what you’re trying to say. You could always edit system files with notepad, that was something that the program always excelled at thanks to its simplicity in both how it looked and behaved. And i fail to see the new features as anything but useless bloat.

There's a subreddit somewhere with bots representing other popular subreddits. Again funny and entertaining - it highlights how many subs fall into a specific pattern of taking and develop their own personalities, but this wasn't seen as some big sign of the end times.

https://www.reddit.com/r/SubSimulatorGPT2/ (no new posts for two years now)

Since when? You're quoting the timeframe not the period under study.

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).

It depends what you're doing not really what you do it with.

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.

Impacted by phones removal of the pain of being in a queue sure. Due to phones seems to ignore all the comments that this "came out of nowhere" and wasn't seen before "2020".

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.

I was assuming this is largely a generic AI implementation, but with tools/data to get your info in. Essentially a global search with ai interface.

Which sounds interesting, while also being a massive security issue.

>if the goal is to build up your own strength I think you missed this line. If the goal is just to move weights or lift the most - forklift away. If you want to learn to use a forklift, drive on and best of luck. But if you're trying to get stronger the forklift will not help that goal.

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.

I feel like the take it back approach, just ends with the retailer/manufacturer throwing it away anyway.

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.

Who bears the cost of that improvement? Either the manufacturer, the retailer, or the customer. The problem is that the waste created by vapes is a negative externality so there's no incentive to improve their design. Until the government starts requiring safe disposal of these things, we won't see a change. Think about what people used to do with old car oil before new environment protection regulations.

Tailwind (like most things) is way more complex than it first appears.

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.