You've never seen project managers basically propose the equivalent of getting a baby delivered in 1 month instead of 9 months by adding more people to the project?
But yeah, if the recruiters start asking for "10 years experience with Claude Code", then I guess a tongue-in-cheek answer would be "sure, I did 10 projects in parallel in one year".
> I think the older AI users are even held back because they might be doing things that are not neccessary any more
As the same age as Linus Torvalds, I'd say that it can be the opposite.
We are so used to "leaky abstractions", that we have just accepted this as another imperfect new tech stack.
Unlike less experienced developers, we know that you have to learn a bit about the underlying layers to use the high level abstraction layer effectively.
What is going on under the hood? What was the sequence of events which caused my inputs to give these outputs / error messages?
Once you learn enough of how the underlying layers work, you'll get far fewer errors because you'll subconciously avoid them. Meanwhile, people with a "I only work at the high-level"-mindset keeps trying to feed the high-level layer different inputs more or less at random.
For LLMs, it's certainly a challenge.
The basic low level LLM architecture is very simple. You can write a naive LLM core inference engine in a few hundred lines of code.
But that is like writing a logic gate simulator and feeding it a huge CPU gate list + many GBs of kernel+rootfs disk images. It doesn't tell you how the thing actually behaves.
So you move up the layers. Often you can't get hard data on how they really work. Instead you rely on empirical and anecdotal data.
But you still form a mental image of what the rough layers are, and what you can expect in their behavior given different inputs.
For LLMs, a critical piece is the context window. It has to be understood and managed to get good results. Make sure it's fed with the right amount of the right data, and you get much better results.
> Nowadays I just paste a test, build, or linter error message into the chat and the clanker knows immediately what to do
That's exactly the right thing to do given the right circumstances.
But if you're doing a big refactoring across a huge code base, you won't get the same good results. You'll need to understand the context window and how your tools/framework feeds it with data for your subagents.
I think GP meant 'longer time users of AI', not 'older aged users of AI'.
Their point being that it's not really an advantage to have learnt the tricks and ways to deal with it a year, two years ago when it's so much better now, and that's not necessary or there's different tricks.
Yeah I meant it in the context of the comment I was replying to, to be precise in the context of the comment that one was replying to, i.e. "10 years of certified Claude Code experience required".
The technology is moving so fast that the tricks you learned a year ago might not be relevant any more.
Long term it probably even is better if the US just leave, especially if the next president is aligned with the current government, we might as well cut our losses early and restructure before they bully the rest of their allies.
> If I wanted to convince NATO to take arctic security seriously without having to deploy troops and resources of my own, this is how I'd do it.
Sure, you can convince a close friend of yours to take his home security much more seriously by telling him that you'll come by later and rob him at gunpoint.
But do you think he'll be even remotely friendly to you after that?
Depends what you mean by large areas. Most of it is an kce sheet, the interior is uninhabitable and the habitable sections are hundreds of miles apart.
Depends what I mean with large areas? Ever been to Greenland?
Greenland is about 25% of the US excluding Alaska, the ice sheet covers 80% of that.
This means that the ice free area of Greenland is a bit larger than California. Thats the third largest state in the US. I would say that is a large area.
I think what I mean by colonial remnant is "administration and control from afar", not "subjugation of indigenous peoples", and it's concerned with what's happening now, rather than what happened 1000 or more years ago and it's no longer particularly relevant. By remnant, I mean that it's administered by Denmark as a byproduct of a colonial gold rush, not because they are the best entity for that job.
USA had its own legislative assemblies too before the declaration of Independence, look what happened.
The vikings landed there, not Denmark, who were Norse, Erik the Red was from Norway (But was considered by then an Icelander exile?). Before Danish control Greenland was a Norwegian colony, this was the colony that died out.
Norse colonisation tended to reflect their origin e.g. the Norwegians colonised the north west of Scotland and Iceland, which were more similar to Norway; Danes went to England and Normandy which were more southerly, flatter and more fertile, much like Denmark; the Swedes with their long Baltic coastline turned their attentions eastward.
Denmark got the North Atlantic islands through the union with Norway, and retained them after Norway became independent.
I know, but that was much later and had a very different dynamic, due to climatic changes etc.
The earlier Norse colonisation of Greenland seemed to consist of farmers and independent settlers, mostly via Iceland. In some areas, they never interacted with Inuit, or rarely.
The later effort seems more focussed on Christian missions to the natives, and commercial whaling and sealing.
More like the VT-05. The VT-52 came a few years later. But yeah, the VT-420 is way later.
Fun fact: The VT-52 didn't have a loudspeaker for the bell sound. Instead, it had a electromechanical relay which was set up to self-oscillate.
"Typing a character produced a noise by activating a relay. The relay was also used as a buzzer to sound the bell character, producing a sound that "has been compared to the sound of a '52 Chevy stripping its gears."
But yeah, if the recruiters start asking for "10 years experience with Claude Code", then I guess a tongue-in-cheek answer would be "sure, I did 10 projects in parallel in one year".
reply