AI has a way of exposing people. In this example, students who are there to get a degree from a prestigious institution, rather than to learn, are prone to take perceived shortcuts and proceed to come unstuck when their AI isn't there to do their work for them, such as in an exam.
It's too damn tempting to not use. You have a magical machine that, on command, will spit out the answer to your question in 10 seconds, whereas you'd need to spend hours to do the assignment the Good Old Fashioned Way. Even students who aren't just there for the prestigious degree are falling victim to this.
When you're up against a deadline - and unless you're very good at time management you're frequently up against a deadline - it's going to be an irresistible lever to pull.
In times past, cheating would mean copying an answer off the Internet or off a friend, both of which are easy to detect. More sophisticated cheaters might spend an hour rewriting the solution to make it less obvious they cheated, but at some point the cost of cheating (time + risk of getting caught) starts exceeding the cost of just doing the assignment. AI changes this - you get a customized answer that doesn't show up in a database with no extra work.
The thing is, students fail to realize just what using AI robs them of. Struggling with the assignment is the entire point. You don't learn if the assignments are too easy; you need to have some challenge to push your brain to understand the material more deeply and to build those pathways to apply the knowledge in novel ways. You become more efficient and effective over time as that knowledge settles in and you get more proficient - one of the reasons why time-bounded exams still make sense (being fast is also a proxy measure for understanding).
That's a judgemental approach to a pattern that has all the marks of addicting behavior.
Of course many people in a competitive environment will click the autosolve button if available. This is a reason to think how to redesign the system so that the approach we want is the reasonable choice, not to look with superiority at those who fall prey to the danger.
You are wrong. Some would have failed before, but not in the larger numbers. Before when they couldn’t complete an assignment they would try different things, seek a professor, or seek out friends to help explain. You could find answer keys to many assignments online, but that doesn’t feel like learning and wouldn’t even always answer your actual misunderstanding. It wasn’t perfectly tailored to your issue all the time.
Now the barrier to an answer is zero. They are basically watching a YouTube video on how to X, seeing step by step instructions feeling like they are doing it, and the moment they swing a real hammer they are whacking themselves in the crotch. It might get better after a few years, but this stuff is just now hitting mainstream for the masses. ChatGPT has only been in mainstream use for about 3 years.
With AI, they fail later (during the exams), where as without using AI previously, they'd fail early and either course-correct, or drop out early (and suffer less of the consequences).
Not sure what the solution is - there's no possibility of stopping students using AI to complete their homework/assignments etc. But let me flip the question - do they need to be stopped? Why not let them fail at the exam? As long as the exam acts as a filter, their usage of AI to "cheat" their learning is inconsequential to anyone but themselves.
> But there's one performance-related area where the Framework pulls ahead—a little—and that's sustained performance. When running a heavy workload like HPL (a FP64 HPC task, that taxes the CPU and RAM constantly for many minutes), the Framework's fans allow it to throttle less than the Neo.
People are seeing big gains in sustained performance on MacBook Neo with a simple thermal pad mod. The disadvantage is the underside of the Neo can get hot, but that's not an issue if it's sitting on a desk instead of your lap.
I was all in on Svelte and SvelteKit until I started encountering CSS weirdness caused by a bug that the Svelte developers said is "by design", namely that components' CSS isn't removed from the document after the last instance of that component is no longer rendered. This resulted in a situation in which styles became dependent on the navigation path the user takes, leading to weird an unpredictable layout issues. I couldn't stomach solving this by using Tailwind.
Then Svelte 5 came along and made Svelte more like React. At first, there were just a few simple runes, but then the runes started proliferating like crazy to solve other runes' problems. At that point, Svelte was dead to me and I went back to React/Next.
The right path for Svelte to take would have been to continue to refine Svelte 4.
Interesting, so if I'm understanding correctly, component A's style was supposed to change when component B was present, and this was implemented as styling rules in component B? Why was Tailwind necessary rather than moving these rules to component A (which I know would probably require some gnarly selectors)?
I don't want to be a "you should've double bagged it" guy, I'm just curious. Svelte is not the be all and all, if you moved on to greener pastures more power to you.
I love how I can see the HTML being streamed onto the page in real time, like the good old days of dialup when images gradually rendered from top-to-bottom.
Brings memories. How my school trashy dial-up was so unbearably slow compared to my father's work 128 ISDN.
On latter, I was able to even download several songs per visit from ftp, and later from Napster.
Strokes will never be preventable. You can mitigate them but a stroke isn't really a disease. It's a symptom.
An ischemic stroke (i.e. stroke due to a clot) caused by vascular or cardiac issues can be mitigated. A cryptogenic stroke however is idiopathic and therefore has no understood cause. These types of strokes make up 30-40% of all strokes. Unless we figure out their cause, there's no way to really prevent them.
But then there's also hemorrhagic strokes which are an entirely separate category that has causes and mitigations more or less diametrically opposed to those for ischemic strokes.
And of course those are just your broad painted categories and they are generally looked at as the start of a medical emergency but strokes happen all the time as a consequence of other medical emergencies.
Even if you could perfectly prevent strokes in generally healthy populations, those same people may still end up suffering from a stroke during a surgery or during/after a major accident or injury. No amount of preventative medication can prevent someone suffering a stroke caused by a brain bleed after a car accident. Likewise for someone with a crush injury, internal bleeding, or broken bones that end up throwing a clot which makes it into the brain.
So any advancement in halting and reversing damage from a stroke will be a massive boon for emergency medicine until the end of time. Unless of course we somehow find a way to cure/render humans immune to blunt force trauma or lacerations.
Sure you can. Just not with any technology on the horizon. But there is conceivable technology (e.g. medical nanotechnology) that could prevent strokes or stop them as they are happening.
Like detecting constriction or loss of integrity of blood vessels, and doing the corresponding intervention.
The saddest thing here is not that it requires some future nanotechnology, but is achievable at the present scientific level, yet too expensive to develop, and wouldn't see FDA permission in a decade or two anyway.
reply