News for hackers. Stuff that matters.
Re:How I learned to program by robocat on Tuesday December 26, 2017 @04:35PM (#16011188)

  "but that’s so obvious that it’s not even worth stating"
Intelligent people I know say this or something similar. What is obvious to a smart person for something they are skilled at, is not obvious to the rest of us!
Re:How I learned to program by smarks on Tuesday December 26, 2017 @05:17PM (#16011406)
Thanks for mentioning this. I don't know whether or not this is related to intelligence, but it does seem to be a fairly common pattern where someone will underestimate the value of writing something down. I did notice this a couple times in danluu's article. A couple comments:

1) There's a lot of value in writing down something about one's experiences, even if the result is "obvious" to anyone else who has gone through the experience. There are likely a lot of people who HAVEN'T gone through that experience who would benefit from reading about it.

2) I worked on a project, mostly independently, for a year or so and produced something useful. To me, it seemed fairly pedestrian: some basic data structures, some ordinary algorithms, nothing particularly novel. A mentor suggested I write a conference proposal about it. I resisted, using the "it's obvious" argument. He came back and said "You've worked on this for a year, and no one else in the industry has worked on it. By definition you're the expert. It's worth a conference talk." Indeed it was, and it launched a significant portion of my career as a conference presenter.

I think this is largely about the difficulty of thinking about what others think when one is too close to a topic. After working on something intensively for a time, one develops a familiarity and intuition of the knowledge about that area. When working with that understanding, things may seem "obvious" but that are totally non-obvious to someone who hasn't worked in the area. This is less about absolute intelligence per se than it is about expertise, and so it's a variation of Kay's aphorism "A change in perspective is worth 80 IQ points."

Re:How I learned to program by Sinidir on Tuesday December 26, 2017 @05:37PM (#16011491)
God i absolutely hated this kind of "this should be obvious" statement made by professors in lectures.

It absolutely poisens the learning atmosphere. And after 20 minutes of lecturing on a difficult topic they ask if anyone has any questions and wonder why noone raises their hand or says anything.

Re:How I learned to program by mikebenfield on Tuesday December 26, 2017 @11:20PM (#16012791)
FWIW, at least in mathematics "obvious" doesn't mean "you're an idiot if you don't instantly understand this." It means, "this isn't deep. If you're thinking about really deep, complicated things beyond what we've been talking about, you're missing the point."

I have on multiple occasions sat down and worked with another mathematician on a problem for an hour+, only for us to find the solution and both conclude that the answer was "obvious."

Re:How I learned to program by paultopia on Tuesday December 26, 2017 @11:28PM (#16012819)
As a professor in a non-math subject, I agree with this and think it generalizes. I often say "this is obvious" as a way to communicate to students "you're overthinking this like woah."
Re:How I learned to program by AnimalMuppet on Tuesday December 26, 2017 @07:41PM (#16012015)
Heh. The worst I heard of was a professor (in a math class, IIRC) saying "this is obvious". A student questioned whether it was obvious. The professor looked at the board, left the room for 45 minutes (!), returned and said, "Yes, it's obvious."

Dude, if you had to think about it for 45 minutes, it's not obvious.

Re:How I learned to program by EpicEng on Tuesday December 26, 2017 @05:42PM (#16011514)
>Maybe the moral of the story should be “leave bad roles more quickly and stay in good roles longer”, but that’s so obvious that it’s not even worth stating

Is that not inherently obvious? Good things are... good, and bad things are not?

Re:How I learned to program by AnimalMuppet on Tuesday December 26, 2017 @07:42PM (#16012019)
Well, it wasn't obvious to me in the early stages of my career. But maybe the problem was that I hadn't seen enough situations to have a decent grasp on what was "good" and "bad".
Re:How I learned to program by torstenvl on Tuesday December 26, 2017 @06:22PM (#16011690)
Agreed. Not a perfect comparison, but this type of thinking reminds me of the history of Fermat's Little Theorem. "I would show you, but I don't want to ramble on too long" and of course it was almost 100 years before a solution was published.

Assuming something is obvious is dangerous.

Re:How I learned to program by pasta on Wednesday December 27, 2017 @04:06AM (#16013716)
Related to the topic: it took me almost 3 years to understand what a variable is and does.

Looking back I can't understand why it took me so long. It's so obvious.

Sometimes it's really hard to understand why some things are not understood.

Re:How I learned to program by yummy on Wednesday December 27, 2017 @07:56AM (#16014483)
Maybe they're smart, but not intelligent