Remix.run Logo
ddalex 6 hours ago

I just got Claude to download and install all the models and servers and agents and prepare all the launch scripts for me... no need to learn, just ask it to do it for you

dofm 6 hours ago | parent | next [-]

Right, but I am a middle-aged bloke who is experiencing existential angst about whether I can carry on in this industry.

I have a pretty deep, maybe paranoid need to be confident I have an intrinsic understanding, and I have found in my life that lessons come to you when you make yourself open to learning.

So I need to build on top of what I know, taking as much of the hard way as I can bear to take at any one time — it has to be not quite difficult enough to put me off.

I can't really explain what I have learned this way that is different, but I feel it in a way that I wouldn't if I'd simply pushed a button.

For the same reason, I have a really basic 3D printer that I've set up myself, set up Klipper, configured how I want it, learned how to calibrate, all that. And now I can say that I feel I have an understanding of 3D printing. I could hold my head above water in a discussion with a real expert, maybe find work in an adjacent field where my insights would keep me grounded.

I can afford a really good printer that has all that set up, and more, has no problems. But I'd just be someone who has a 3D printer.

(Also who am I kidding about the existence of a printer with no problems)

greyskull 4 hours ago | parent | next [-]

This really resonates with me, and I'm only a decade and change into my career. I use claude a lot day to day. I try to use it sensibly, making me more productive and produce better work. I'm also trying not to lose understanding along the way. I want to be able to actually talk to the conclusions I'm reaching.

I have colleagues that seem perfectly content to delegate too much to the agents, and it saddens me. It feels like there will be swaths of engineers that didn't train some of the critical thinking skills that I take for granted.

I certainly see it in slack discourse around anything more complicated than a feature implementation. Maybe I'm just cynical. Time will tell, I suppose.

bluGill 3 hours ago | parent | next [-]

You will not live enough to learn everything. Eventually you have to say "I could figure [something] out but I won't take that time." Most things are that way - I probably could learn brain surgery (I used this example because it has a reputation of being a very difficult course of study). I would like to make a lathe from scratch - but I don't have easy access to enough iron ore to get started - even if I start from scrap metal, I probably wouldn't spend months making my own surface plate (...) and so I own a factory made lathe instead.

That is why I'm content to delegate to agents - I have more code/features I want to write than I have time to debug (writing is the easy part).

sanderjd 4 hours ago | parent | prev [-]

For me (about halfway between you and dofm in my career by your own statements in this thread), it's a dream at the moment. I can delegate all the tedious stuff that I've done "the hard way" a thousand times already and feel I have very little of value remaining to learn, so that I can spend more time on all the things that are actually new and thus much more interesting.

greyskull 3 hours ago | parent [-]

It's been a great multiplier for me in similar ways. The "dreamiest" thing has been that it has freed up time that I would normally have spent doing sprint work, to work on things that just don't make the cut until it's bad enough to deprioritize other work.

Over the last few months, I've been digging into performance problems with a high throughput service that my team owns. I started working on the problems in my own time, put out short and medium term improvements that legitimately avoided operational issues, and started developing an alternate architecture that should meaningfully address the problems for the long term.

I've learned new things and made improvements that probably wouldn't have ever gone in otherwise.

sanderjd 3 hours ago | parent [-]

Yes exactly. There is a narrative that it's driving everything toward low quality slop, but in my own work it's exactly the opposite. We're doing work on quality and performance that we never would have gotten to in the past.

I've spent my whole career being frustrated by the pile of low severity bugs and performance issues that "I could fix that if I could only justify putting a couple hours into it!". And now I can just fix all those. Nobody is going to question my use of time to write prompts and do code reviews of those things, when I can to my "real" work simultaneously.

sanderjd 4 hours ago | parent | prev [-]

Yeah, this is just the engineer's mindset. It's not surprising that this is a popular view here, even if it is not (and does not need to be) the mainstream perspective.

greyskull 3 hours ago | parent [-]

> mainstream

What does "mainstream" refer to when we're talking about software development and LLMs? As opposed to "engineers".

sanderjd 2 hours ago | parent [-]

This is a very fair question! When I wrote this comment, I was definitely thinking of the "real" mainstream, i.e. users of llm chat to generate text, not software engineers.

But I think there is (and has always been) also a distinction between the "mainstream" of software developers vs people who are working on new tools and capabilities to be used by that "mainstream".

IMO it is certainly true that the most efficient and cost effective was to do "mainstream" software delivery at the moment is hosted frontier models. But for people thinking about "what's next?", it makes a ton of sense to be exploring different models in anticipation of a possible (but certainly not inevitable) sea change.

swiftcoder 5 hours ago | parent | prev | next [-]

I don't necessarily think your answer is wrong for all people, but if you work in software... how do you plan to differentiate yourself from everyone else out there, if the depth of your understanding is "Claude can do it for me"?

dofm 5 hours ago | parent [-]

This ultimately is the discussion I am here for.

I mean one of the things I use a local LLM for, because I can, is to generate starter documentation. But I ask it to — I want it to give me overviews, plans, all that. It can make something bespoke for me.

I guess I could also ask it to do the work. But where do you draw the line?

The universal labour-saving device is the great provocation of the next 100 years I think, and both Star Trek and Wall-E have grappled with it.

coldtea 6 hours ago | parent | prev | next [-]

>no need to learn, just ask it to do it for you

And that's how skills die.

CamperBob2 5 hours ago | parent | next [-]

When's the last time you shoed a horse?

The reason I delegate so much of local LLM installation and administration to Claude Code is simply because there's no point learning practical things that will work completely differently in a couple of years, or in memorizing procedures that I'll forget long before I need to perform them again.

No longer having to sweat all the details is a Good Thing, not a Bad Thing.

dofm 5 hours ago | parent | next [-]

I am not sure I disagree, and I certainly don't mean to disagree very fervently.

But I think if you want to really learn to ride well, understand horses well, there might be some benefit in learning how to shoe a horse. At some level it should never only be someone else's job.

verdverm 5 hours ago | parent [-]

At the same time, most people can drive without understanding how a car works.

saganus 5 hours ago | parent | next [-]

You actually do need some understanding of how a car works, no?

For example, you need to know it uses gasoline (or diesel), it requires oil changes every certain amount of time, break pad replacement, etc.

You also probably need to know that you can't operate cars over a certain amount of water, that you need a driver's license, stopping at red lights, etc.

Sure, you might not need to be a mechanic, but that's far from not understanding how a car works, which to me sounds similar to knowing how to shoe a horse, which is different than being a horse vet.

coldtea 3 hours ago | parent | prev [-]

Yes, and they're all the worse, more at the mercy of car companies and mechanics, and less aware of the world they live and operate in, for it...

WickyNilliams 5 hours ago | parent | prev | next [-]

If I worked with horses for 8 hours a day I imagine the answer would be "recently"

psychoslave 5 hours ago | parent | prev | next [-]

Having to shoe a horse never was a general skill.

Maybe a more apt analogy would be a skill like making fire without a lighter.

sanderjd 4 hours ago | parent [-]

Writing software never was never a general skill either though? Or am I misunderstanding your point?

psychoslave 2 hours ago | parent [-]

Yes, LLM are thrown through pretty much everyone digital life whether they like it or not, it's not just devs. It might even unlock exploring things that need code that average user wouldn't have dared to do before.

coldtea 3 hours ago | parent | prev [-]

>When's the last time you shoed a horse?

That skill died too, so what's your point?

CamperBob2 2 hours ago | parent [-]

Skills sometimes do that. What's your point?

coldtea an hour ago | parent [-]

Skills are good. They shouldn't do that.

charcircuit 5 hours ago | parent | prev [-]

Except with AI models it's possible to make a backup of them creating a permanent artifact of a skill.

sorokod 6 hours ago | parent | prev | next [-]

Then what is the point of ddalex?

dofm 5 hours ago | parent [-]

I think if you really don't feel the need to know the "why" of everything, sometimes this might be the right approach. It is quick, pragmatic, gets you started.

Maybe my biggest problem with the world of agentic AI, and the reason I am putting myself through learning it the way I am, is that the need to know the "why" of everything is so fundamental to me, that I don't know if there is any point to me without it.

So this is really the only way I know how to proceed.

sanderjd 4 hours ago | parent [-]

To me, this is just a question of specialization. Not everyone needs to be a "I understand how the system actually works" person. In fact, not many people need to be that person. But every system does need some of that person to exist!

And we happen to be discussing this on a forum where the type of people who will be the specialists for the kinda of systems we're discussing are likely to gather.

I'd be surprised if in my casual discussions out in the real world, I were to run into a lot of people who care exactly how all this works, to the extent that they want to invest significant money into hardware that allows them to run things themselves and dig into what's actually going on. But I'm not at all surprised to come across such people here! (Indeed, it would be very disappointed if I didn't!)

kdkdjduxnd 6 hours ago | parent | prev [-]

[dead]