Readit NewsThis 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.
It might be as simple as creating awareness about how everything works underneath and creating graduates that understand how these things should work in a similar vein.
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.
I'm actually producing code right this moment, where I would normally just relax and do something else. Instead, I'm relaxing and coding.
It's great for a senior guy who has been in the business for a long time. Most of my edits nowadays are tedious. If I look at the code and decide I used the wrong pattern originally, I have to change a bunch of things to test my new idea. I can skim my code and see a bunch of things that would normally take me ages to fiddle. The fiddling is frustrating, because I feel like I know what the end result should be, but there's some minor BS in the way, which takes a few minutes each time. It used to take a whole stackoverflow search + think, recently it became a copilot hint, and now... Claude simply does it.
For instance, I wrote a mock stock exchange. It's the kind of thing you always want to have, but because the pressure is on to connect to the actual exchange, it is often a leftover task that nobody has done. Now, Claude has done it while I've been reading HN.
Now that I have that, I can implement a strategy against it. This is super tedious. I know how it works, but when I implement it, it takes me a lot of time that isn't really fulfilling. Stuff like making a typo, or forgetting to add the dependency. Not big brain stuff, but it takes time.
Now I know what you're all thinking. How does it not end up with spaghetti all over the place? Well. I actually do critique the changes. I actually do have discussions with Claude about what to do. The benefit here is he's a dev who knows where all the relevant code is. If I ask him whether there's a lock in a bad place, he finds it super fast. I guess you need experience, but I can smell when he's gone off track.
So for me, career-wise, it has come at the exact right time. A few years after I reached a level where the little things were getting tedious, a time when all the architectural elements had come together and been investigated manually.
What junior devs will do, I'm not so sure. They somehow have to jump to the top of the mountain, but the stairs are gone.
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.
As I recall, the system was set up with 3 branches of government in tension. Obviously, that was naive.
Context: we developed chemicals toxicity prediction models. This was 20 years ago, this allowed the EPA to quality check applications made by chemical companies.
I try everywhere I can to install an Emacs mode for code/text navigation. But they tend to be inconsistent and for some software, it is simply not possible.
Do you have good resources to help there (running Linux/Gnome)? Do you keep the faith or switched "out"?
I find that to be a massive understatement. The amount of time, effort and emotional anguish that people expend on handling emails is astronomical. According to various estimates, email-handling takes somewhere around 25% of the work time of an average knowledge worker, going up to over 50% for some roles, and that most people check and reply to emails on evenings and over weekends at least occasionally.
I'm not sure it's possible, but it is my dream that I'd have a capable AI "secretary" that would process my email and respond in my tone based on my daily agenda, only interrupting for exceptional situations where I actually need to make a choice, or to pen a new idea to further my agenda.
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 :-)