Reply to thread

Message: <blockquote data-quote="Janx" data-source="post: 7652196" data-attributes="member: 8835">I'm a figure it out myself kind of guy.I taught myself how to program when I was 10 by sitting at the PC and reading the language reference guide on all the commands.I taught myself how to read sheet music by googling the note reference and then spending a 3 day weekend computing and visualizing where those notes were on the guitar neck in reference to the location on the musical chart.  By the end of the weekend, I couldn't sight read (that is play a song straight off the sheet), but I could parse any sheet music into what I needed to do and memorize that).  You could call out a note and I could nail it on the guitar or place it on the chart.Pretty much most of what I know for programming technologies, I figured out.   Generally, a business need is presented, and I find a technology that could solve it, and then I figure out how to use that technology from articles and exploring the specification.I read 60 pages an hour, and I've keenly honed my ability scroll through titles, tables of contents, headings to jump to the exact section I actually need from a google search or given site/book that allegedly holds the answer.  Basically, I know what the answer should look like before I find it, allowing me to ignore anything not shaped like the answer.As a result, I really hate YouTube tutorials.  They force me to sit through blather on irrelevant content. Other than moving the slider to see a freeze frame that might be near where I need to start watching.  Unlike real text which contains section headings and such that I can pick out from the whole cloth.  Video is a terribly linear experience.In most games, I just jump in and figure it out.  Most games play the same nowadays, and it is usually a matter of finding the differences in the control scheme, rather than fretting about "how do I move forward".  bear in mind, I'm used to the old days of getting pirated Apple IIe games with no directions and having to figure out how to play Aztec (a game that used MOST of the keys on the keyboard).Part of my trick to learning is that I build a mental model of how a thing should work before I even approach learning how it should work.  So I know what to expect from a banking program before I run your banking program.  At that point, I am merely revising my model with the artifacts I find in the actual model.Contrast that to the typical clueless user, who approaches the computer banking program and it's like they've forgotten how to manage their money at all, let alone what data structures and interfaces one should expect to see when dealing with the topic of money and Your Banking Transactions.this methodology is part of what helps me spot what the right answer is when I'm googling for it.  I have already deduced what the general solution should look like, and am merely looking for something in that shape with the exact actual details that I need.I loathe sitting in a classroom while somebody runs through their lecture.  I could have read the same content in a fraction of the time, or simply meditated on the concept the session was intended to teach and come to the same conclusion.If I have to ask somebody for help, I want to sum up the situation ,clarify a term that I didn't know, and find out what I should expect to find when I remove the cover, or how to remove the component without causing damage.  If I have to start over with troubleshooting every prior step with that person so they can catch up to where I am in the problem, they are wasting my time, more often than not.</blockquote>

Verification