The analogy is that each layer is a slice of Emmental cheese. You end up with a bad event, only if all the holes in the slices align.
5,985 karma · joined July 22, 2009
https://www.chemeo.com https://www.ceondo.com
The analogy is that each layer is a slice of Emmental cheese. You end up with a bad event, only if all the holes in the slices align.
I spend a couple of hours per week teaching software architecture to a junior in my team, because he has not the experience to not only ask correctly but also assess the quality of the answer from the LLM.
So sorry but no, the platforms are addictive and not all the kids can resist against an armada of statisticians ensuring the systems stay addictive only through honest conversations.
By the way, this would mean you could solve all the addiction issues if it would be working...
[0]: For me this is really an important part of working with Claude, the model improves with the time but stay consistent, its "personality" or whatever you want to call it, has been really stable over the past versions, this allows a very smooth transition from version N to N+1.
[0]: https://www.energy.gov/femp/hail-damage-mitigation-solar-pho...
We also have a lot of fun playing board games, simple stuff from design, card games, here, the game play is the fun factor. Yes, better hardware may bring more realistic, more x or y, but my feeling is that the real driver, long term, is the quality of the game play. Like the quality of the story telling in a good movie.
I have a team of 10 engineers, the quality of the code they produce together with the LLM of the day correlates even more with the experience.
My impression over the past 6 months - before we had no "official" access to LLM, is that they increase the gap between junior and experienced developers.
Note that this is my limited impression from a team of 10 engineers. This matches with Simon's feeling in a good way for you!
I am at the end of the third decade, soon entering the 4th. I find it easier with the time. This is because with the experience, I can directly zero on the fundamentals of the new technology popping up and quickly see if this is just marketing or more a breakthrough.
Also, we have less diversity now, every new tech getting momentum is quickly defacto standardizing. Look at the way we run LLMs now, tons of models, 5 lines of Python, within 2 years, everything kind of standardized. You can now quickly pick up the subject (ironically, the LLM will help you there) and run with it.
It is way harder for young people, because of this FOMO, they try everything and nothing, they copy/paste what "God" GPT told them and have no understanding of how things are working in the background. For them to learn "through the stack", without experience, with the new big thing coming out every week but without the ability to judge, it is very hard. I am happy that my first website was static and cgi-bin was still a thing, happy that I learnt how to get my Fortran code to run fast on an multi-core system (yes, Sun stuff), that I was able to build relatively slowly my experience.
I second you, just for that, I would continue paying for a subscription, that I can also use it for coding, toying with ideas, quickly look for information, extract information out of documents, everything out of a simple chat interface is incredible. I am old, but I live in the future now :-)
This is because they are built to go through the machine after each rental. Good retails skis have less "robust" but faster, thinner base, they would be dead after 3 months of rental.
Source: I spend way too many hours each season in a ski shop taking care of a mix of rental and competitive hardware.
My advice, for the moment:
- Tune out both the most heated and the most dismissive rhetoric.
- Focus on tangible changes in areas that you care about that really do seem connected to AI—read widely and ask people you trust about what they’re seeing.
- Beyond that, however, follow AI news with a large grain of salt. All of this is too new for anyone to really understand what they’re saying.
AI is important. But we don’t yet fully know why.
With that, it shows that he is not really using the AI tools, he would be using them he would have given this advice :
- try the tools and look where they can improve your life.
I don't know a single person with a bit of seniority, using Claude Code, who wants to go back to any IDE from 5 years ago.
I do think that for most of the people, you are right, you do not need to know a lot, but my philosophy was to always understand how the tool you use work (one level deeper), but now the tool is creating a new tool. How do you understand the tool which has been created by your Agent/AI tool?
I find this problem interesting, this is new to me and I will happily look at how our society and the engineering community evolve with these new capacities.
Exactly my thinking, nearly 50, more than 30 years of experience in early every kind of programming, like you do, I can easily architect/control/adjust the agent to help me produce great code with a very robust architecture. By I do that out of my experience, both in modelling (science) and programming, I wonder how the junior devs will be able to build experience if everything comes cooked by the agent. Time will tell us.