This "instant" loop is so fast because it doesn't involve the part where you learn

You seem to be hung up on the part about "learning". Do you know how x86 registers work? Or atomic instructions available on ARM, SPARC, or POWER architectures?

No, of course not. Because all of that got abstracted to higher-level instructions decades ago.

▲

hvs 4 hours ago | parent | next [-]

Yes, I do. And it wouldn't take you that long to learn, either.

▲

petcat 4 hours ago | parent | next [-]

Well that's great for you. That's some knowledge that you will possess for the rest of your life.

I want a green lawn and big bushy shrubs in front of my house. Do I need to know the intricate biology of my soil and habitat? No, of course not. I just do the surface-level things that make the lawn and shrubs thrive.

	▲	Johnny555 4 hours ago \| parent [-]
		>No, of course not. I just do the surface-level things that make the lawn and shrubs thrive. And others want the green lawn and big bushy shrubs, but don't want to learn all of the surface level things to make their lawn thrive so they hire a service to do it for them. And there's nothing wrong with that - not everyone enjoys the yard work, but they still want the thriving lawn and shrubs... and they are happy to write a check to OpenAI... err...Lawn Doctor every month to get that result since the time they save by not dealing with their lawn, they can pursue things they do want to do. Not everyone wants to (or needs to) learn every detail along the way of getting the results they want.

▲

NegativeLatency 4 hours ago | parent | prev | next [-]

I understand your point, but also imagine applying that across the whole spectrum of computing.

It's very useful that there's an intermediary that knows how that stuff works so I can build things without thinking about it in excruciating detail the whole time, I can dip down lower and learn stuff when it's relevant (like cache access and nested arrays) but I can also not do that in many situations.

There's also the argument that you can do engineering without understanding the underlying science as seen in th pyramids, the beautiful old european churches, etc

▲

nonethewiser 4 hours ago | parent | prev [-]

Who is more productive? A python dev who learns about x86 registers in his free time or one that uses AI at work?

	▲	JSR_FDED 3 hours ago \| parent [-]
		The one who uses AI at work will eventually be replaced by someone cheaper who uses AI at work. The one who learns about x86 registers is much more likely to continue to evolve

▲

vouaobrasil 4 hours ago | parent | prev [-]

But maybe there's a limit to the usefulness of this abstraction. Perhaps forgetting too many basic skills lower down isn't always as useful as going from Assembly to C. I'd argue that there's a law of diminishing returns there, and it's not an endless series of benefits.

▲

nonethewiser 4 hours ago | parent | prev | next [-]

Learn what? The thing the tool can do instantly? Take the win and spend your energy on bigger problems.

▲

hgoel 4 hours ago | parent | prev [-]

In a world where there are endless things to do and only limited time to get them done, not every issue needs to be a learning matter.

▲

Jtarii 4 hours ago | parent [-]

If you are making something that you care about you should probably understand how it works. I didn't know this was such a hot take.

▲

hgoel 4 hours ago | parent [-]

So, since you care so much and caring requires knowing everything about everything that even remotely intersects with your project, as (presumably) a software developer presumably you understand in detail how every bit of the CPUs you're targeting, plus the lithography, chemistry, and how solid state physics, and the underlying quantum mechanics work?

▲

dbalatero 3 hours ago | parent [-]

You seem to be massively exaggerating here for effect.

I think the main point is, if you're building frontend web apps, you should probably know how HTML, CSS, and JavaScript interact to some decently high level. Can you look stuff up on the margins via AI, or StackOverflow, or whatever? Sure.

If you're building <something else>, you should probably know the core tools and concepts at the appropriate level to build them.

No we do not need to know every aspect of CPU branch prediction and whatnot to make a webpage.

	▲	hgoel 3 hours ago \| parent [-]
		I think it's pretty obvious from the context of "if you had technical gaps (say, you couldn’t write CSS)" that this isn't about someone that regularly works on frontend web apps, it's about someone that is having to do something that is not normal for them. E.g. I mainly work on HPC code, maybe once in a year or two I need to throw together an animated poster to accompany a printed one. It's obviously ridiculous to claim that this means I have to learn frontend web dev.