FE has a lot of boilerplate only if you’re starting from scratch every single time. That’s why we had template systems and why we invented view libraries. Once you’ve defined your libraries, you just copy-paste stuff.
It seems like they should be able to “overweight” newer training data. But the risk is the newer training data is going to skew more towards AI slop than older training data.
No to the first question, and maybe with a lot of money for the second question.
In the 20 years I've been in the industry, boiler plate has dropped dramatically in the backend.
Right now, front end has tons of boiler plate. It's one of the reasons AI hassle such a wow factor for FE, trivial tasks require a lot of code.
But even that is much better than it was 10 years ago.
That was a long way of saying I disagree with your no.
FE has a lot of boilerplate only if you’re starting from scratch every single time. That’s why we had template systems and why we invented view libraries. Once you’ve defined your libraries, you just copy-paste stuff.
It seems like they should be able to “overweight” newer training data. But the risk is the newer training data is going to skew more towards AI slop than older training data.
There won't ever be newer training data.
The OG data came from sites like Stackoverflow. These sites will stop existing once LLMs become better and easier to use. Game over.
Every time claude code runs tests or builds after a change, it's collecting training data.
5 replies →
I mean if people continue checking open source code into GitHub using those new features then they should be able to learn them just fine.
This is only true if there continues to be tremendous amounts of money/hardware/power available to perform the training, in perpetuity.