|
That way, they can rub in all that knowledge.
The best way to improve Windows is run it on a Mac.
The best way to bring a Mac to its knees is to run Windows on it.
~ my brother Jeff
|
|
|
|
|
I'm really not a fan of video. There's nearly always a lead up you have to skip and you can only go as fast as the video, which is either too fast or slow but never just right, creating pausing and rewinding points. Then, depending on the source platform, there will be annoying interrupting adverts.
I like to skim through docs/written tutorials to find the relevant parts, you can't really do that with video tutorials.
|
|
|
|
|
This is so true that I prefer reading to watching movies, and I don't watch TV series (unless physically restrained and coerced by my missus, who devours them).
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
The most irritating videos of all are where instead of narrating, the presenter types (usually very badly and with lots of backspacing) into Notepad, what they ought to be speaking. I turn those off and find something else immediately.
The next most irritating ones are where the narration is in so heavily accented English that it is virtually no easier to understand than if the speaker was using his first language.
Thank god you can set the playback speed in YouTube these days. X2 and the pause button are your friends.
|
|
|
|
|
Some of my oldest university text books, from the 1970-80s, are pedagogical masterworks: Consise, well organized, treating each topic separately, and with well chosen chapter headings and index entries. The author is clear on what is the expected background, and the material is organized in a way that if you know the elementary stuff, you may skim the first parts of each topic.
No more. First, any book less than 1200 pages is a "booklet" nowadays. There is so much talk, talk, talk, with no real substance.
Second, lots of books assume that you are closely familiar with some older technology that the new one replaces, and explains how the new thing works by telling how it differs from the old one. Or it explains a mechanism by showing e.g. which machine code (or .net msil), rather than its logical operation.
Third: The text assumes that you have read any preceeding page of the book in every minute detail, even those chapter covering topics that is way outside your needs. You must learn the whole thing, all the functions of the system, and work through every single example and exercize, to gain the background for understanding following examples; they are based on stuff that is completely irrelevant to you, but you must learn it anyhow. Otherwise the examples are useless.
Finally: Creating good indexes is a forgotten art. Nowadays, it looks as if authors believe that the more voluminous, the better, so they throw something, whatever, in there, whether useful or not, just to bring the size of the index up.
I guess that some newer books are like the old ones: consise, well organized, with an awareness of the reader's need for information. But on the average, the pedagogical value of textbooks have dropped dramatically the last 15-20 years. (When I think of it, the decline started long before that! Some of the books from the 90s are outright terrible!)
|
|
|
|
|
We had a newbie dev who did this. We were still finding bugs five years after they left the group.
|
|
|
|
|
Linking some to achieving something.
Even if that goal is to learn something new, but how do you measure that without regurgitation being the solution?
|
|
|
|
|
By asking on QA sites, we (may) get multiple answers and multiple views.
By answering on QA sites, we learn far more than any other method. That is because, our understanding is cross checked against huge audience.
Amit Joshi
Value of the value is valued only if its value is valued.
|
|
|
|
|
Not just that, but the fact we're there looking for an answer means it's something we don't know and needs learning. Whereas, sometimes with books, tutorials etc. it's just going over things you already know.
|
|
|
|
|
Books give a set amount of knowledge. Asking questions is meaningless if you don't know what questions you have. A book is a map, questions add details.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
I disagree that books give a set amount of knowledge. Two people reading the same book may learn different things, and one person reading a book for a second time may learn something new.
I'm not suggesting I don't use books, in fact I rather like them for specifically learning a medium depth overview on a topic, such as a brand new language or stack. I like that the author has (hopefully) considered all the basics one might need to get to grips with a given subject.
Answering the survey question, however, for me the ongoing learning is a combination of trial and error, and also QA sites. When I'm stuck I may know the question, or if not be able to formulate enough of a question to find what is often a detailed and explained solution to what is blocking me. In getting past that problem, I'm learning. Another aspect, is that sometimes we can reconsider a problem and learn about it simply by trying to formulate it as a question. Somewhat like rubber duck programming.
|
|
|
|
|
That's not for learning. Random copying and pasting is an activity performed while doing ACTUAL production level work.
|
|
|
|
|
I'd argue that it's a good form of learning with the addendum that you then reverse-engineer it or research what the different functions, operators, etc. in the code does. Sort of a miniature version of the "modifying and extending an existing application" option.
|
|
|
|
|
Abdullah Leghari wrote: Random copying and pasting is an activity performed while doing ACTUAL production level work.
That should be exactly the opposite... specially with the word "random" starting the sentence.
Doing that is the source for a lot of bugs, security holes and many other nasty things.
If you don't understand a code, don't use it in production, ever.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I think that's actually the joke. You copy random code and hope for the best.
|
|
|
|
|
Next time, he should use the joke icon.
Sadly, it would not surprise me to see someone saying it for real
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I don't understand what Spring does but I have to use it. Fortunately, I don't have to delve into that area of the code.
|
|
|
|
|
If I don't know how to solve a task, I may find some code that does it, and paste it in. Then, by studying the code and tracing its execution, I learn how it works, look up documentation of the library calls it uses etc.
Often it ends up with me tailoring the code to my task, simplifying and cleaning it up to such a degree that the resemblance to the original code is rather vague. Yet, the example code is where I learned the technique I needed.
|
|
|
|
|
For the most part I deal in SQL, and may of my questions on code and development can be answered within a single thread/blog post. For more detailed knowledge I tend to broaden my horizons. my first port of call is generally the Documentation of the framework on line. Secondly Duck n Go.
modified 15-Apr-19 10:38am.
|
|
|
|
|
I learn best through pictures and videos, very rarely through writing or text books with no pictures.
I also learn best through hands on, trial and error.
A lot of times there is only text, and then I just make do the best I can, leaning heavily on the trial and error.
|
|
|
|
|
For me these days a combination of
Written tutorials
Video tutorials
Online interactive tutorials
Using the docs and trial-and-error
But occasionally some of the others.
Kevin
|
|
|
|
|
I prefer the learn-by-doing approach.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
With due consideration, one realizes it's really the only way to learn as, until you actually do something with what you've learned you never know if you've actually learned it.
And like all things, theory is one thing - practice (like confronting asinine users) is quite another.
I believe we call this, as it progresses, "experience".
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
I stay away from theoretical stuff because I'm too busy trying to make code work in a real-world app.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Sure but you still need a reference of some kind, I think they are looking for what type of reference you prefer.
All types of reference require you to do the examples. Just reading a reference in totality is boring a batshit.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
