Interesting. I tend to learn better when I don't perceive something as "hard", as that creates a mental block of sorts for me. Acquiring proficiency requires si

Interesting. I tend to learn better when I don't perceive something as "hard", as that creates a mental block of sorts for me. Acquiring proficiency requires significant amounts of time investment + effort, but it would seem "hard" should denote something above that. I tend to prefer terms like "tractable", where it's less about whether the given problem is "easy" or "hard", and more about whether I can find a productive way to reason about the problem. An easy subject can be made intractable by the wrong kind of presentation. Most subjects that are very /new/ to a given person may be intractable on the onset. Some subjects, ones that I would call truly "hard", do not become tractable for a very long time. So I don't know if I'd call software development hard, but it's still a new and unfamiliar thing to a lot of people, and it can be quite intractable at various times, which is basically what "bad documentation" means.