|
That's the most honest thing I've read in this thread, and reflects the reality as I see it, and tried to state it. If he was Pro-Trump he would be demonized as a Nazi, Baby-Killer, SongBird, WarMonger. But like a TYPICAL Politician, he wanted good press in his dying days, so he went the other way. And "Look, all is forgotten!" LOL!
|
|
|
|
|
RIP ![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif) .
August has claimed many a good man.
|
|
|
|
|
> "good man"
> "John McCain"
Error: incompatible constraints on node 1
|
|
|
|
|
A soldier never dies but becomes imortal.
Thanks & Regards
Puneet Goel
Save Paper >> Save Tree >> Save Humanity
|
|
|
|
|
He was a decent politician.
There are to few of his kind.
|
|
|
|
|
So much for cross-aisle cooperation. Now partisanship will become the standard.
|
|
|
|
|
I didn't care for the man.
When the borders of [fill in the blank]-istan are more important than those of the USA then you're a bad Senator.
|
|
|
|
|
I wonder what are your strategies for learning a new technology. Do you read one or more books first to get a grasp of what a certain technology is capable for, or do you start developing or practicing creating apps after reading some articles and then googling the missing pieces along the way as you code? I know people who never read books cover to cover and just learn on the go.
I like to have a better grasp of the technology first before starting a project, so I try to read a beginner book first, then some intermediate to advanced books, sometimes before even trying to create an app. Sometimes I just try to have a big picture of all the capabilities of a certain technology before starting to code and just go back to a certain topic when I am about to code. It is sometimes a problem of learning to much firsts before starting coding.
If you try to go and immediately code after reading a few tutorials, you may be able to create a full app without entirely knowing the full capabilities of the technology, and so you may try to do certain things the wrong way when there are a more official way on doing it.
Let's put React.js for example. I can simply learn react by looking at the "Getting Started" and some basic concepts, and then start coding immediately. But then I will miss concepts like redux and other patterns if I don't read an entire book.
What are your thoughts? What is the better way to learn and be comfortable with a certain technology?
|
|
|
|
|
First, there must be a need.
|
|
|
|
|
|
Or are you a nerd for speed?
|
|
|
|
|
Shouldn't that be a nerd for sperd?
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Better a nerd than a hunk.
|
|
|
|
|
Unless you are feeling hunky-dory 
|
|
|
|
|
|
I always read first, go through a few tutorials then usually dive in. But always go back and read more to pick up advanced concepts. The stuff I'm trying to learn now I've read/reading 3 books, one of them 1600+ pages before writing any code.
Everyone has a photographic memory; some just don't have film. Steven Wright
|
|
|
|
|
That is a lot of patience. Do you employ zen techniques?
modified 27-Aug-18 4:10am.
|
|
|
|
|
No... he is retired 
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.
|
|
|
|
|
The book is TCP/IP Guide, I started reading it a few years ago and couldn't do it. I have a lot of other things to keep me busy so I allot 50 pages per day, one so I don't overloaded and twould so I can digest information.
I'm not familiar with zen techniques, I'm just old.
Everyone has a photographic memory; some just don't have film. Steven Wright
|
|
|
|
|
Old ain't bad. It equates to experience. The danger is as a fellow employee who is equally old demonstrates, don't get rigid in your thinking or methodology. Of course, the shift from functional code to object oriented isn't easy even if you are young.
|
|
|
|
|
With an open mind you'll learn and grow.
Everyone has a photographic memory; some just don't have film. Steven Wright
|
|
|
|
|
LOL! Poorly phrased, but the equally old dude I was referring to sits about 4 feet from me. His mind is partially open as he can create one giant class to do his entire project, but fails to see why anyone would use properties or break classes into smaller explicit classes.
|
|
|
|
|
Randal Vance Cunanan wrote: I like to have a better grasp of the technology first before starting a project, so I try to read a beginner book first, then some intermediate to advanced books, sometimes before even trying to create an app.
How's that working out for you?
This seems like a very ineffective way of learning to me.
Most of what you read won't even stick because you don't know what you're reading about!
A book is fine, but follow along with the examples.
In the end, there's just one way to learn how to code and that's by writing code!
Personally, I go for tutorials on the internet.
Usually, a new technology has a "getting started" section on their website.
After you've seen some of the technology you can dive deeper, perhaps by reading a book.
Scanning through the different tutorials on a technologies' website can also help in knowing what you don't know, for example, you'll find out Vue.js has components which must be registered (whatever that means).
And, after some years of experience, I'll usually think "there's probably a pattern for this" after which I can do a directed search, for example, "share code between angular controllers".
|
|
|
|
|
I need something the technology I'm about to learn is great for. I remember learning OOP from having a task/scheduler project, I had several (related) types of tasks and have solved that via inheritance. Before that, OOP was for me "Namespaces separated by dots" because that was all OOP was doing for me that I needed.
But that's maybe just me. I'm a practical guy and I strugge big time learning something for the very sake of learning it. I need a project, a goal with the new stuff being a better way to reach that goal, then my previous knowledge. Otherwise, I'll do things the most effecient way and if that means that I won't learn anyting new, then that new wasn't a good idea to learn in the first place.
|
|
|
|
|
Same here. Applied learning works, but theoretical just flows on through.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
