How will open-source and open-weight models continue to thrive after financial incentives die off? Surely open models will suffer from outdated knowledge cutoffs if noone will pay for model training?
Well said! The lines from this movie are written in a way that make it easy for people to relate to this vague notion that 'experience' is different from 'learning'. But quantitatively speaking it's less clear what the difference really is. After all isn't experience simply another type of learning?
Everyone knows there is bias. The problem this article highlights is that by delegating screening and human judgment to a few AI vendors those vendors will bias all employers in the same way.
If both systems have a good clock. Then the synchronization messages only need to contain the time delta to correct the time (phase?) drift to achieve full synchronization.
Although in this particular case, I tend to agree with Igor as he was employed as a system administrator not a software developer so it's unlikely that there were any real contractual constraints imposed on him in relation to copyright or invention transfer.
Absolutely! The backlog is enormous though, and much of mathematics requires a great deal of work to understand it to the depth required before a novel application becomes apparent.
The problem with exams is that everyone has a bad experience with a poorly written one. Well-written exams will have questions that test students at different levels of understanding across the whole curriculum.
So a student who only understands the basics should be able to answer most of the easy questions and students who have a deeper understanding can answer the harder ones.
Well-written exams should feel pretty fair and leave students feeling like the result they got is proportional to the effort they put into studying the material (or at least how well they personally felt they understood the material).
I feel like there is a lot of nuance around this topic that is getting lost in the noise.
The direct and indirect financial impact of technical decisions are indeed hard to measure. But some technical decisions definitely have greater financial impact than others. Even if it's hard to precisely quantify the financial costs/benefits of every decision. It is possible to order them relatively. X is likely to make more money than Y. So we do X first and Y later.
There is a significant amount of chance involved in whether a product/feature will even make money at all. So even good plans with measurably positive expected value could end up losing money.
Just because it's impossible to be 100% certain of the outcome of any decision. Doesn't mean we should throw the baby out with the bathwater.
I don't think there is a bias in the field towards a youth narrative. I think there is a bias in the media.
Nobody I've ever met would expect a breakthrough from a 20 something year old no matter how much of a genius they are. Communicating a breakthrough requires time, effort, and credibility to begin with, which nobody has at that age.
Your 30's are when you can start to really do great things. And then depending on the field you can kind of just keep going as long as you have the energy for it. But lots of people begin to wear out into their 40's (for lots of different reasons).
In terms of great breakthroughs. If you haven't had your great idea by 40. It's probably increasingly unlikely that you'll have one later in life (but not impossible). Not everyone needs to have a paradigm changing idea to have a successful career though.
I don't think they're suggesting we reduce the amount of faculty. They're suggesting that you ask all the faculty to share less space, increasing the efficiency of the real estate holdings. Also by reducing the number of schools, you reduce the amount of expensive ancillaries.
Technically it's the same. But behaviorally it's not. When pulling in more dependencies is so easy, it's very hard to slow down and ask the question do we need all of this?
Mucking around with cmake adds enough friction that everyone can take a beat for thoughtful decision-making.
There's a softer component to healthcare which is that people can overreact to medical results. If a doctor administers a scan, finds a handful of likely benign things but wants to administer another scan later on down the line, I'm probably much more likely to look for a second opinion that tells me to cut them out (even if it may not be medically necessary) than trust my doctor that "it's probably fine".
It's probably more accurate to use a software analogy about performance metrics. We measure random request spikes now and again that strain the system. It's probably fine, but later on down the line, something could change that results in an outage during one of these spikes. Do we proactively fix the problem even if no change is expected? Or do we wait till there is definitely a problem before taking action?
Did power tools not cause layoffs? That seems like a dubious claim to me. Building a house today takes far fewer people than 100 years ago. Seems unlikely that all the extra labor found other things to do in construction.
Maybe. I'm not sure its that different though? If one person can do the work of two because of power tools, then why keep both? Same with AI. How people feel about it doesn't seem relevant.
Maybe the right example is the role of tractors in agriculture. Prior to tractors you had lots of people do the work, or maybe animals. But tractors and engines eliminate a whole class of labor. You could still till a field by hand or with a horse if you want, but it's probably not commercially viable.
They should have known better. It was their job to sell the box. Instead they wasted a tonne of their clients money on a proof-of-concept for something that was never going to work. Using the word 'impossible' was probably also a big error. If it can perform computations, nothing is impossible, but some things are certainly not recommended.
I think this is partly an education problem, and partly an industry culture problem. Lots of young developers are incentivized to 'contribute' to open-source as a way to demonstrate that they can actually write software. So open-source becomes a way of signalling competence when at a broader scale it's just extracting wealth from the vulnerable.
Open-source seems to be fragmented into three groups now. Large enterprise open-source like Kubernetes or OpenStack where the license seems more like a legal agreement amongst vendors to not sue each other. Legacy open-source projects that are getting by on brand recognition and sheer willpower. And a whole bunch of noise from people who are looking to leverage open-source into a job of some sort.
As people get more comfortable with AI. I think what everyone is noticing is that AI is terrible at solving problems that don't have large amounts of readily available training data. So, basically if there isn't already an open-source solution available online, it can't do it.
If what you're doing is proprietary, or even a little bit novel. There is a really good chance that AI will screw it up. After all, how can it possibly know how to solve a problem it has never seen before?