I remember back in the day, that pinball physics were extremely hard to write.
The main issue was "bouncy ball" physics. At certain angles, balls should roll along the edge and continue to touch that edge. In other cases, the ball bounces of the edge. It's very hard to get both use-cases right. Anyway, you cannot seem to get it right without taking the ball spin into account.
Some things seems very simple but are actually very hard. Pinball physics is one of them. The other I know of is time, super complex!
Who cares about the theory? The fact is that the world is now worse due to LLM use.
And it's not just restricted to software. Everything I care about is getting worse.
Dribbling about how it could theoretically be better doesn't help undo the damage. "Imagine how much fun we could have playing baseball", says the man with the baseball bat, as he kneecaps you.
Most senior developers that steered juniors or interns in the past, are able to work with LLM's.
Sure, LLM's are unreliable. So are juniors.
Sure, LLM's code quality is not always great. Well, so is the juniors code.
The benefit of LLM's is that they can work super fast and have a vast amount of knowledge. The benefit of juniors is that they actually learn from their mistakes and get better over time. LLM's stay at intern/junior level, even with the correct context.
So for me, I see each LLM session as a new intern coming in. You hand them the right context, give them the correct instruction, and off they go. Then they come back, and you will have to judge how detailed you want to review what they produced. Or in other words, can you get away with some bad code? And for the next session, it's a new intern that starts from 0.
But it is also highly dependent on the project you are working on. If it's a big complex codebase, LLM's will struggle, and they can only do simple tasks (however, they can help with testing a lot!)
So the teachable thing is unfortunately experience:
- Know where quality matters, and where it doesn't
- Know what kind of mistakes could be made and should be checked for
- Know which things can be duck-taped together, because they live at the edge, and which things need a proper foundation, because the rest builts on it.
So in the end, I think it all comes down to making the right trade-offs and the right decisions (which LLM's are terrible at, by the way). And unfortunately that is gained by the slow process of experience.
I think it's very tough for junior developers right now, because they either go fast by letting the LLM's do the work, but then they learn nothing. Or they go slow by asking the LLM's what's going on, and then do learn.
A senior developer never understood the full code-base, and never reviewed every line of code. That's just impossible. And now every developer needs to be a senior developer that is able to steer these new "interns".
And just like with juniors and interns, you have to put a lot of effort into it, and it's not always clear in the end if you gained or lost time :D.
I don't claim LLM's and juniors are the same. I claim that working with LLM's and juniors are similar. If you are able to work with juniors, you are probably able to work with LLM's.
To comment on the post you linked:
I agree that people can be thought. But on the other hand, I also had juniors that reached their limit pretty fast, which can also be frustrating. The best way to "teach" LLM's is the context, but I agree it has limits and is not really teaching anything, just steering them in the right direction every time (like a checklist).
Your comment basically states that running LLM's is a gamble, but according to my experience, most of the time it delivers what I ask. Maybe in a different way that how I would do it, but I want results, and am not interested in micro-managing.
Are you working on a project that requires high quality code? Or is it your preference to work in such a codebase? For me, I was always ok with "good enough" code. And sometimes "good enough" needs to be good, and other times you can get away with some really bad code.
Even Elon Musk made the difference between the two. He's in control of Starlink, US government in control of Starshield. Ukraine claims both were affected.
How hard can it be to reason about this? Maybe ask ChatGPT, and it will says it's both.
But sure, they all lie and you are right, Ukraine only has Starlink. Not a problem for me at all, and the world can be flat too, no issue with that. Have a fun day.
All the money is in Silicon Valley, that's why they move there.
If this was a US vs EU thing, I would love to hear a US tech giant that isn't in Silicon Valley or Seattle.
Fact is, even in US, no other city was able to replicate that success. For example, there would be no point to move your startup from EU to New York for example.
Micron was founded in Boise Idaho and is still headquartered there. Cymer, which makes the EUV light source in ASML machines, was founded in San Diego, and is still there.
Lots and lots of US tech giants are not in Silicon Valley or Seattle. In fact, Texas, North Carolina, New York, Georgia, and Virginia have huge hubs of tech giants - especially the Research Triangle Park in NC.
I agree with the general premise that US tech isn't exclusively in Silicon Valley or Seattle. But those regions clearly still play an enormously outsized role in the US tech industry, to the point where it seems unlikely US tech would be as globally dominant without them.
Notably several entries on your list are companies that were founded and grew successful before moving to the locations you listed, often for tax breaks and/or to fit the politics of the company executives. Aside from Dell, all the companies you listed as being located in Texas became successful elsewhere first. Texas has proved it can lure in already successful companies more than it has demonstrated it can grow them.
Which is itself a legitimate achievement, but if the question is how you grow new successful tech companies, it's not a super useful data point especially if we're taking about different countries. There are relatively few barriers for a company that grew up and became successful in the environment of Silicon Valley to move to Austin with the promise of lower taxes, but Europe can't quite replicate that same migratory model to grown their own tech industry.
My list exactly addresses your point: "If this was a US vs EU thing, I would love to hear a US tech giant that isn't in Silicon Valley or Seattle". I have shown you at least 10 US tech giants that are not in Silicon Valley. I also did not include many others such as Network Appliance, Texas Instruments, Pfizer, Micron Technologies, Akamai, etc. Regardless of their size vs Siemens, they are huge in the industry. But, keep moving the goalposts if that makes you feel better.
And, no, we are not ignorant to the fact Europe does not have tech companies. No one said that, but you seem to have a real axe to grind against the US. I suggest you step outside and touch some grass.
BTW: I have traveled all over the EU and one thing holds true: folks there are the most arrogant and condescending people I have ever met. And your remarks proves the point once again. They are truly unapproachable. They do not smile and they refuse to acknowledge each other when grocery shopping, walking on the sidewalks, riding on the bus/train - essentially in any public space. It must be absolutely depressing to live in such a culture all the time.
Edit: I see you removed your nasty comment: "Are Americans really that ignorant that they think Europeans don't have tech companies the size of Redhat". Why?
As a Flemish person I can attest that the Dutch have outstanding engineers. So if their intelligence agency has a proper budget, they definitely have a nice pool to select from.
Flanders has not been a part of the Netherlands for almost 200 years and was only ever really part of it for 15 years (It's the Dutch speaking part of Belgium).
Why would it do anything? Unlike living things that have gone through the rigorous gate of survival-of-the-fittest over millions of years, AI only does what it was trained to do in the sheltered environment in which it has been coddled; teetering atop an impossibly complex supply chain whose only defense against entropy is humanity's greed.
This (implied) end state isn't inconsistent with my scenario. We already see the incredibly hubristic "I'm the only person who can safely handle AI!" attitude among the people working at/running the big labs.
I think after reading all the comments here, it's clear that some people develop an emotional bond with LLM's.
It reminders me of my parents, who were commenting after seeing a robot vacuum cleaner getting stuck in the same place every time "The poor thing was stuck there again, you should really do something about it! Last time the poor thing was sitting there for a day". Like it was a pet.
Or remember that video when the guys from Boston Dynamic kicked that robot dog, and there was an outrage about that?
I wonder if you and me also have a limit, where as robots get more realistic, we would be like "Don't be cruel to that thing!"
Most wifebeaters think everyone beats their wife, and those who don’t like it just need to get over it. Never played gta, and zero interest in such forms of “entertainment.” Normal people don’t play shooter games, sorry.
The main issue was "bouncy ball" physics. At certain angles, balls should roll along the edge and continue to touch that edge. In other cases, the ball bounces of the edge. It's very hard to get both use-cases right. Anyway, you cannot seem to get it right without taking the ball spin into account.
Some things seems very simple but are actually very hard. Pinball physics is one of them. The other I know of is time, super complex!
reply