Is my Java book good to go?
So ive been reading a thread on spoon feeding people answers , and i like it makes total sense. In an attempt to help myself along i have this over here "Java The Complete Reference". Is this a good book to go with for leaning i see there are many recommendations on books here for leaning many more than i expected on the topic.
Or should i expect to be referencing from multiple books while learning is tat i better option? As i know from my html and javascript and php learning days i used multiple book and online resourea which lead to a kind of conflict since there are many away to achieve one thing however later i found this valuable in the case of knowing what is not optimal or if there are better suited options for a programming function about. It took more time however to learn in this fashion .
Thanks guys
Re: Is my Java book good to go?
Everyone is different, but personally I found it helpful to choose a simple application as a goal (i.e. make a calculator), and then learn what's needed to get that working, from books, online, asking questions, etc. To me, that's a lot more fun than analysis paralysis with my nose in a book, and it's a good exercise in troubleshooting bugs and getting familiar with computational problem solving in general. And it ends up giving you unforseen sub-goals (how do I respond to a button click?) to achieve as well. Not to mention it divides the huge programming world into smaller, more manageable chunks instead of trying to absorb everything at once.
For the most part, you can't really go wrong with a published Java book. But you might find, like I did, that it's more valuable to actually finish a simple program, and learn/refer as needed along the way to get it working.
Re: Is my Java book good to go?
Quote:
Originally Posted by
BinaryDigit09
Everyone is different, but personally I found it helpful to choose a simple application as a goal (i.e. make a calculator), and then learn what's needed to get that working, from books, online, asking questions, etc. To me, that's a lot more fun than analysis paralysis with my nose in a book, and it's a good exercise in troubleshooting bugs and getting familiar with computational problem solving in general. And it ends up giving you unforseen sub-goals (how do I respond to a button click?) to achieve as well. Not to mention it divides the huge programming world into smaller, more manageable chunks instead of trying to absorb everything at once.
For the most part, you can't really go wrong with a published Java book. But you might find, like I did, that it's more valuable to actually finish a simple program, and learn/refer as needed along the way to get it working.
hahaha i have a interesting story ... When i started web dev my gf was a graphic design student , well had just finished , i was in a technical trade so i though i knew all about problem solving. I then later decided what i was doing wasnt making other people money and wasnt challenging me enough so i went into web development .My gf suggested just use templates why reinvent the wheel , i refused , because i knew better , man i coded websites from scratch crappy ones , pasted with bad coding , and patch coding. I sat for hours tearing my hear out on simple javascript issues lol . But the time came when t paid off . today i use templates for most clients but because of that ealy struggle i learnt the inner workings of those languages and man it has served me well. When i looked at my first bootstrap template 6 months later i thought hell this site structure is poor , that code is unnecessary ect ect , im no pro , i dont think anyone ever is . But alot of people just accept answers without questioning. Why is this the best way ? Is it the best under all circumstances ? ect ect I think to truly understand something a person must know those answers too.
Perhaps you are right ive done it the way you describe with web design , it just took alot of time . But honestly i believe that it is the best way to learn.
