upvote
Some things are simply about repetition to fully understand.

For example, I've been around make files for over a decade, I can read them fairly fluently, but if you asked me to write one from scratch, I would be chained to the docs.

Another example, I can read Spanish to the level of understanding the gist, but I'll lock up if I need to speak more than a sentence or two.

With the agents, you can have it generate it, and you'll understand it on a cursory glance, but you won't actually know it. IMO the difference between knowing something, and understanding is whether you can bring it into existence with minimal outside reference.

With LLMs you feel like you're learning a lot, but you lose out on the hard part that actually commits it to memory.

To be fair, on the flip side I've written enough basic xxd style debug print functions that I know I don't want to do it again.

reply
Who gives a damn if you know the syntax of a Makefile. This is exactly the type of non-skill that should be automated away. All you need to know is what its capabilities are, and when to use it.
reply
I do because I often need to fix things in locations without any internet connection.

To fix and debug things, you need a better understanding than you do to introduce the bugs in the first place.

reply
Well in that case you would have an offline copy of the docs before, and now you have a local LLM which includes that in its weights- but better yet, have both (luckily we still have manpages).
reply
deleted
reply
> What about the code you were never able to write because you were time constrained?

I was still never able to write it, even after I had Claude create it.

reply
> I’ve learned more in the past year than any year prior in technology. All this learning is now possible, because I’m not spending my time wiring a react front end to a backend for a simple table crud operation.

I was hoping that, for every “write X for the Nth” time we would get better tools to obviate that need, only needing to do it one time. The reality is a million times more disappointing.

reply
> What about the code you were never able to write because you were time constrained?

This makes no sense to me. If something needs doing, it takes the time it needs to.

> because I’m not spending my time wiring a react front end to a backend for a simple table crud operation

This also makes no sense to me. Either this crud aint simple, or you’ve invested nothing in automating it.

reply
"This makes no sense to me. If something needs doing, it takes the time it needs to."

Triage comes from war hospitals, where the number of people would and needing treatment would often outnumber the staff. Those people need treatment, but the staff didn't have time to attend to them, and so many died.

Adding technologies often reduces the time or takes to do a thing, allowing you to do more things overall. For example, if you seal a wound with super glue instead of stitches you save time, and more people as a result. (And yes, that was the original use case for super glue!)

AI assistance is letting us find and fix bugs that we previously didn't have time to discover or to fix. And a million other things that were previously outside our time budget.

reply