> I've gone literally years of my working life without touching a single pointer in production code.

But you did use references, right?

What baffles me is how many young developers code without caring about the underlying infrastructure. Not caring to understand what makes their coding possible.

I have met many that deal with programming like car owners that just want to drive down to the supermarket, so to speak.

> You can make them feel crappy by signalling that they are damaged or deficient,

I explicitly stated I wasn't targeting the OP with my comment.

> or your attitude can be positive and inviting.

That is why I pointed out a few, quite good, books where the subject of reference vs pointers happen to be described quite well in a programming language that isn't as intimidating as C or C++, while allowing for the same type of coding.

One of them even shows how to build an entire computer.

A couple other people have jumped on this, but it's also worth pointing out the specialization that goes on in the field now.

For example, I'm almost exclusively writing web applications, and have been for years (coming up on 15 years soon).

Granted, I do know a bit of C and some other more systems-y languages (and more than a little bit about the underlying implementation of Python, which is the language I prefer to use), and I even know a fair amount of underlying fundamental theory, but... ultimately my brain is of finite size and I have only finite time. So I have to prioritize like everyone else, and choose what I will spend time learning and what I will devote brain cells to remembering.

The result of this is that there are things which, to someone outside of web development, would seem horribly arcane and irrelevant, but which I have to know, and as a result there are things those other people have to know which, to me, are horribly arcane and irrelevant.

And the further result is that when I see people wading into web development from other fields of programming, I often see them make mistakes -- sometimes big, security-hole-opening, money-losing mistakes -- that are on par with someone blundering into C with no knowledge of pointers, memory management, bounds-checking, etc.

So just remember that what seems hugely important and required-learning to you may not be to someone else, and that something which seems irrelevant to you may be hugely important required learning to them :)

Yes, I have come to realize my words were not the best chosen ones.

The link to reference material was nice but what I'm hoping to draw attention to is about about tone. Your tone is scornful, judgmental, and aloof. If we worked together and I had a question on a subject of your expertise I might think twice before consulting you for fear of being dressed down publicly for my ignorance.

"What baffles me is how many young developers code without caring about the underlying infrastructure. Not caring to understand what makes their coding possible."

Our industry has many layers of abstraction, and there's always something to be gained by exploring more of the space (e.g. application domain, high level language, low level language, compiler, compiler IR, assembly, process, os, hardware apis, hardware implementation, electrical engineering, theoretical physics). However it is destructive to the social dynamics of a community when members scoff at or impugn the motives of those who do not know what they do. Both sides probably know things that the other doesn't too, why not learn from one another?

If instead of being content with being baffled with these colleagues of yours who are incurious about pointers, why not show them something cool that you can build with them! E.g. walk them through that elegant implementation of a hashmap in C that uses pointers to pointers from the front page of HN a couple of days ago.

Faire enough, maybe I should have chosen other words.

Just saying you're not targeting someone doesn't stop them from feeling bad about not understanding something that is apparently obvious.

You have a different background to many programmers, is it unreasonable that they don't understand/know something that you do? It certainly doesn't make them stupid and statements like "baffled that people don't understand pointers" definitely imply that they are somehow deficient.

In any case, why does everyone have to care about in inner workings of everything they use? It seems perfectly reasonable for computers and programming languages to be things that people can use without having to understand the details, like cars, microwave ovens, aeroplanes, TVs, radios, analog watches, GPS (the list goes on).

> That is why I pointed out a few, quite good, books where the subject of reference vs pointers happen to be described quite well in a programming language that isn't as intimidating as C or C++, while allowing for the same type of coding.

Pointing out books is nice, but it doesn't make up for effectively abusing people who might need them: "read this to learn more" is way more pleasant than "I can't believe people don't know this, read this to learn more".

https://xkcd.com/1053/

What baffles me is the number of programmers who use technology like cars, cell phones, fridges, planes, trains and advanced medicine without understanding what makes the underlying technology possible.

/s Be nicer.

You don't do processor microcode or memory controller code, why should you care about that? People who work in managed languages don't care about pointers. I don't remember which register stores the result of a division either. Why should I care about it?

> People who work in managed languages don't care about pointers.

Yes we care, they are called references.

Use too much of them without thinking and performance goes down the drain thanks to cache misses.

This is why managed languages that care about performance have value types and padding support. Even Java is getting them.

Except Java hasn't had them for 20 years and most Java programmers don't even think about how it takes 4 levels of indirection to just read something that would be a struct in C.

> There are many programming environments that are both common and quite productive that have no pointers at all.

This is a bit misleading. The vast majority of languages have pointers (languages without object identities exist - functional languages for example - but they are relatively the exception). However, those languages tend to give them other names.

What non-systems languages lack is pointer arithmetic and native notions of pointer-to-pointer (though it is always possible to simulate the latter).

I agree the person you responded to showed a toxic attitude. I believe/hope that the first step to improvement for people who think they don't get pointers is for them to realize they've been working with pointers all along.

As I already mentioned in a sibling thread, maybe I could have chosen other words.

It wasn't clear to me how harsh that sounds in English.

The concept of references was introduced in my introduction to Java course I guess at the same time that the concept of objects were explained more fully. At least in Java, I feel that you have to understand the concept of references, to be mindful of aliasing, the fact that primitive values can't be aliased (I've tried twice to make a method to swap two primitive values, of course failing at that), and so on. Pointers don't really feel like a conceptual jump, coming from Java - the fundamental concept of indirection is still there. The fact that you can do pointer arithmetic and such on them, while error prone and harder to deal with than references, did not feel that hard to understand, conceptually. Granted, I have very little experience with C-level programming, so I be missing some subtle points.

There might be a difference for people who are used to languages which are more consistent than Java (like: "all values are really objects"). Do people not have to know about references in languages like for example Python?