To a certain extent, yes it does! For my cases, I'm often running 3 parallel implementations that get 10 to 20 iterations deep, and then Claude has to sort out the pros and cons of the options and also take the best bits of each. Easy to hit the context window with Claude just running those on its own, so giving `/cook` to Claude, it can offload a bit more via cook and stay higher level.
I second that! This is also how I feel about Raspberry Pis. There's so much they can't do, and yet in a way they can do everything. It's not the power of the machine, its about how much control you have or how close you can get to the metal. At least that way you learn about why you need more powerful hardware.
It's one click to set up a Debian environment on a Chromebook. Same on an Android phone. You can learn plenty from that. Once you've learned the limits of what you can learn within that environment, it's not difficult to then unlock the bootloader and learn even more.
To be honest, anytime I see someone recommending how easy it is to install Debian I always feel like they’re some relic from the nineties. Kids likely won’t follow any advice starting with “install Debian”.
They will if they are at all "technically curious" and bump-up against the limits of "ChromeOS" and running software they want to execute. A couple quick searches will find them some instructions, and boom - after a week or so, they are running Debian, their own Minecraft server, Blender (poorly), or whatever had prompted them to look for alternatives.
Never underestimate the time investment and frugality of a "technically curious" young person... Myself, I would have been a happy end-user, loading/playing games, running software - except, I bought a cheap modem - with physical IRQ jumpers - and no documentation - and it's default jumper settings conflicted with my mouse in Windows. If it hadn't been for that cheap/frugal purchase and then having to invest the time to troubleshoot, I wouldn't have become "technical" and moved on to greater and greater challenges and learning experiences. Most people would have just returned it and got an external modem instead, or given-up on even the possibility of connecting to BBS's...
What is fundamentally different from the late 80's/early 90's, is now there is a tremendous wealth of knowledge on the internet to actually facilitate that troubleshooting type of learning activity. Is that better? Well - there will always be a "known solution", but what I find many people do now, is follow whatever the first set of instructions they find, treating them like a "magical spell", without knowing/learning "why/how"... [And if the first set of instructions doesn't work, the majority just "give up"]
Overall - in my experience, the percentage of people who are truly "technically curious" is about the same as it ever was - single-digits... It ultimately depends on whether or not their interests/passions/blockers align with being forced to go "beyond" their comfort zone.
The advice isn't "install Debian." It's click the "Turn On" button next to "Linux Development Environment." They can learn whatever they're curious about from there.
Yeah, that really resonated; the author captured something about the way kids explore.
It brought back memories of when I first started using a Unix time share at university, and exhaustively read all the man pages. Didn’t know why, just wanted to discover everything.
AI is making everyone faster that I’ve seen. I’d say 30% of the tickets I’ve seen in the last month have been solved by just clicking the delegate to AI button
I'll be honest, just the idea of working there makes me feel like vomiting. For me, they are bizarrely evil. They're not evil like, "we're going to destroy our competition through anti competitive practices," (which they do), but "let's destroy a whole generation of minds."
And now with the glasses. I mean, jeeze. Can there be a stronger signal of not caring for others?
It's as if Meta sees people as cattle.
Though I think a lot of techies see humans as cattle, truthfully.
What was your rationale?
I guess this question is out-of-the-blue, and I don't mean for you to justify your existence, but I've never understood why people choose to work for Meta.
I feel the same - would I like a meta paycheck, sure, but I couldn't look at myself in the mirror knowing what the company I'm giving my work to does to people's brains (not just the young, though that is the most reprehensible).
I told my son I would disown him if he worked for Facebook, for the reasons stated above.
Then he took a contracting gig for Meta. His rationalization was that the project was an ill-specified prototype that would never see the light of day - if they wanted to throw money at him for stuff like that, he would accept it.
That gig is finished, and he's now thoroughly disillusioned with working for big tech.
From this angle, what's the difference between Meta and a junk food company?
Both sell things that are bad for you, but that the consumer has complete control over whether or not to consume.
And not all of what Meta is selling is bad. There's a lot of information exchanged on Facebook, Instagram, etc. that are good for society. Like health/nutrition advice, etc.
I've always attributed it to people being very good at convincing themselves they aren't one of the bad guys. A big paycheck makes it even easier to ignore to what you are a part of.
Where livelihood is concerned, rational individuals with strong morals can do irrational, and immoral things (e.g., work at the Palantir's of the world).
TLDR: incentives don't just shape perception, they form it
I wrote a SaaS project over the weekend. I was amazed at how fast Claude implemented features. 1 sentence turned into a TDD that looked right to me and features worked
but now 3 weeks later I only have the outlines of how it works and regaining the context on the system sounds painful
In projects I hand wrote I could probably still locate major files and recall system architectures after years being away
But in general this is meta to the CLI agent.
So if you were to use the CLI to perform a review of some code. This tool would allow you to loop the output of the code review 5 times onto itself.
reply