Perhaps between 0 experience and a junior programmer, but not a senior programmer; you need a lot of experience with different designs to gauge how to model and approach different problems appropriately. There are many working solutions to problems, but the space narrows drastically when you consider what's appropriate to abstract and what isn't, what can be maintained easily and what can't, what can be tested easily, what can be explained easily, etc.
Re:Curse of knowledge
by logicallee on Sunday April 23, 2017 @11:06AM
(#14178435)
But that experience, isn't exactly information. You can't really learn it in a book... My comment was about passing on the required information -- and how much of it there is (little) and how well it's hidden (very well, in a pile of things that will waste anyone's time.)
your sibling comment (by andromeda__) gives a good example.
Re:Curse of knowledge
by andromeda__ on Sunday April 23, 2017 @07:44AM
(#14177753)
True. Laravel is probably the best PHP framework I've come across but the error display page seems like the only thing I didn't like. It can be quite daunting at first; errors that are easily decipherable using PHPs inherent error message display can seem quite arcane using Laravel.
Everything else is teachers and documentation and compiler errors being stupid.
For example when starting with C++ who starts out with the importance of semicolons, how you have to not leave them off, find the missing semicolon, and have a teacher watch over you pointing out your missing semicolons? Nobody. You get a stupid abstract sentence : "statements are terminated by semicolons" after some bullshit definition of a statement. You can spend 90 minutes looking at definitions of the latter without acquiring a skill that the former could show in - not an exaggeration - 17 seconds.
17 seconds : 90 minutes is 1:317, so 3 years becomes 3 days of someone actually showing you.
You know it's true. You've seen it!