Unlimited retakes would be an enormous amount of work for professors/TAs/teachers.
Optional homework is often a disaster. At best, students would do it right before an exam and the goal of education is not to just pass exams. They’d probably still get a lower score than if they did the homework when they were supposed to.
What I think is better is to have a due date, but just make the maximum 10% each day it is late. So after 2 days, the highest score you could receive would be 80%.
I liked that system because it gave some flexibility with deadlines while still encouraging you to turn things in on time.
Late work policies like this can be a logistical nightmare at scale. Rather than play the penalty-over-time game, have hard deadlines that are inflexible. Students don't have to engage in mental gymnastics with their scores and instructors don't need to track this stuff.
My view is this: a student can turn in an incomplete assignment. Work they completed get evaluated and graded. Anything not completed gets zero credit. Homework should be an investment in effort over time anyway. Unfortunately, procrastination is a deeply rooted problem that usually kills this.
You're right, there are tons of different workflows you can do. One of the more innocent ones, regardless of you opinions on vibe coding, is just using the LLM to understand the code base better. Even if I'm vibe coding something, I will often start by having the LLM construct documentation for the current code flows. It's a document that is useful to me as a human because it mostly just gives me code pointers and tells me what it does as part of the larger whole. It's useful for the LLM since it saves a ton on time and tokens in the long run.
I've personally started focusing a lot more on code quality and communication skills over correctness of solving some leetcode problem. If I could get the infrastructure in place for it in the interview, I would have candidates generate something via AI and watch their process for that (how do they evaluate a plan, how do they review the code, etc.).
It will also cause a lot of trouble for companies with specific data access policies (probably most large companies). My money is on this new thing getting gutted very quickly as they figure out how much this constraint cuts into their bottom line.
That's definitely the case as model distillation is one of the explicit safety carveouts they mention. Though TBF, model distillation is also a big concern for general safety as distillation could allow you to have the model without the other guardrails. It's sort of a master key to the model.
While less necessary with AI, Excel is still the king of data entry and basic data manipulation (sorting, filtering, updating, etc.). I’d say that SQLite with a GUI for visualization is a far stronger competitor than Jupyter at those sorts of things. You can do that stuff in Jupyter, but it’s easier in Excel.
Jupyter also has a janky execution model. It doesn’t track dependencies so you have to be very careful in how you separate cells from one another and just running the whole notebook every time seems kind of pointless vs just writing a pure Python script.
Yeah, I thought an application that works like Excel, but instead of "infinite" grids you get to declare finite rows/columns with types. Extending and inserting rows feels like a non-issue. This would also enable to have multiple tables on a single view. It's essentially a merge of Excel and SQL.
std::array can sometimes give you the best of both worlds for stack allocation in that you statically constrain the stack allocation size (no alloca) while guaranteeing that your buffers are large enough for your data. You can also do a lot of powerful things with constexpr that are just not possible with arrays. It is very convenient for maintaining static mappings from enums to some other values.
That is not what they should do according to microeconomics because luxury goods are Veblen goods. Decreasing price would lower demand, at least until they lowered it enough that it was no longer a Veblen good.
Basic microeconomics is just that: basic and thus an oversimplification.
This already happens a lot for used clothes with the thrift store->poor country->landfill pipeline. That third step will likely be a lot less rare with new clothes.
Optional homework is often a disaster. At best, students would do it right before an exam and the goal of education is not to just pass exams. They’d probably still get a lower score than if they did the homework when they were supposed to.
What I think is better is to have a due date, but just make the maximum 10% each day it is late. So after 2 days, the highest score you could receive would be 80%.
I liked that system because it gave some flexibility with deadlines while still encouraging you to turn things in on time.