2 ms·
In the abstract this is true, but can still be daunting. I remember early in my career I had done a fair bit of C. I'm in a meeting with some architects and t
by kenjackson 16y ago
In the abstract this is true, but can still be daunting.
I remember early in my career I had done a fair bit of C. I'm in a meeting with some architects and they start writig up structs with bitfields. For some reason I must've skipped that section in K&R and never seen it code. My first thought was, "you can't do that in C", but then I noticed that no one else was having a problem with it. Then I realized I didn't know for sure what it was.
I wanted to say, "What is that thing after the colon?", but I feared hearing, "This is 'C 101'. You haven't seen this? It's not possible to write good code w/o it. We need to revert all of his changes. Please escort him from the building now".
In other words the concern is not that you'll feel dumb relative to smart people. But rather people thinking that this is so basic, how could you possibly not know that.
With that said, I did consult at a place where one guy didn't know what free/delete was. He had only worked with garbage collected languages, and I was tracking down tons of memory leaks in his code. When he asked me why he had to free memory (in a C++ application) I did have to pause to avoid saying something I might regret. Everyone has their experiences, and I'm sure he would laugh at my naivette when it comes to Lisp macros.