325 karma · joined September 3, 2025
The defining feature of masonry is that it supports mixed aspect ratios. That's its whole thing. If you aren't mixing landscape and portrait images, you shouldn't be using masonry layout.
And even for the people that do, just because an LLM isn't absolutely state of the art doesn't invalidate it from being useful.
I can't imagine that it wouldn't be. If a company has explicit written permission from the copyright owner granting permission to use that copyright, then they can use it.
Also, it wouldn't be a special license. If you wanted to do a "For my friends everything, for my enemies the law" thing, you'd just set it as all rights reserved and add special note encouraging people to ask for permission to use it.
Plus, copyright enforcement typically goes in the other direction. It's not about who you can sue, it's about who you can't. Licenses are just a way of specifying who you cannot sue. If you want everybody to use your project but don't want to bother with a license, you can make it all rights reserved (the legal default) and just not sue anybody. You could sue them if you wanted to (which is why nobody would ever use your code: because of the risk that you change your mind and sue them), but nobody is forcing you to.
And I think that teachers can adapt. A few weeks ago, my English professor assigned us an essay where we had to ask ChatGPT a question and analyze its response and check its sources. I could imagine something similar in a programming course. "Ask ChatGPT to write code to this spec, then iterate on its output and fix its errors" would teach students some of the skills to use LLMs for coding.
It's obviously not quite the same as programming, but my English professor assigned an essay a few weeks ago where we had to ask ChatGPT a question and then analyze its response, check its sources, and try to spot hallucinations. It was worth about 5% of our overall grade. I thought that it was a fascinating exercise in teaching responsible LLM use.
If we assume that AI will automate many/most programming jobs (which is highly debatable and I don't believe is true, but just for the sake of argument), isn't this a good outcome? If most parts of programming are automatable and only the really tricky parts need human programmers, wouldn't it be convenient if there are fewer human programmers but the ones that do exist are really skilled?
The main way that heat dissipates from space stations and satellites is through thermal radiation: https://en.wikipedia.org/wiki/Thermal_radiation.
Space stations need enormous radiator panels to dissipate the heat from the onboard computers and the body heat of a few humans. Cooling an entire data center would require utterly colossal radiator panels.
I suspect that Claude couldn't make an "import from ChatGPT" button because OpenAI would make it difficult, so they'd have to rely on user initiative and technical capability (exporting to JSON and importing from JSON is enough technical friction that the average user won't bother).
The GPT-4o controversy is a good example. People got attached to 4o's emotional and enthusiastic response style. When GPT-5--which was much more terse and practical--rolled out, people got really upset because they were treating ChatGPT as a confident and friend, and were upset when it's personality changed.
In my experience, Gemini and Claude are much more helpful and terse than ChatGPT with less conversational padding. I can imagine that the people who value that conversational padding would have a similar reaction to Gemini or Claude as they did to GPT-5.
How common is this property in geometry? I know that fractals like the Koch Snowflake also have infinite perimeter over finite area, but I don't know what else does.
However, I don't think that banning all AI-generated code is reasonable. Having an LLM generate a couple of functions or a bit of boilerplate in an otherwise manually coded PR should not invalidate it from being accepted if it's helpful.
No, I don't think it is. There's more nuance to this debate than either "we're banning all LLM code" or "all of our features are vibe coded".
A blanket ban on unreviewed LLM code is a perfectly reasonable way to mitigate mass-produced slop PRs, but it is not reasonable to ban all code generated by an LLM. Not only is it unenforceable, but it's also counterproductive for people who genuinely get value out of it. As long as the author reviews the code carefully before opening a PR and can be held responsible, there's no problem.
Whatever solution we implement in response to AI, it must avoid hurting the students who genuinely want to learn and do honest work. Treating AI detection tools as infallible oracles is a terrible idea because of the staggering number of false reports. The solution many people have proposed in this thread, short one-on-one sessions with the instructor, seems like a great way to check if students can engage with and defend the work they turned in.