Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Other Sellers on Amazon
+ Free Shipping
+ $3.99 shipping
+ $9.83 shipping
A Smarter Way to Learn Python: Learn it faster. Remember it longer. Paperback – August 9, 2017
|New from||Used from|
Frequently bought together
Customers who bought this item also bought
Customers who viewed this item also viewed
If you buy a new print edition of this book (or purchased one in the past), you can buy the Kindle edition for only $2.99 (Save 63%). Print edition purchase must be sold by Amazon. Learn more.
For thousands of qualifying books, your past, present, and future print-edition purchases now lets you buy the Kindle edition for $2.99 or less. (Textbooks available for $9.99 or less.)
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
Object Oriented Programming concepts, specifically class. The analogy
that is used to explain a class is a form in a doctor's office. OK, that is a
reasonable starting point to explain what a class is.
What I found after that, right away disturbed me to the point that I had to
write this review. There is a thing about Python and classes where there
is a keyword called "self" that is basically a reference that an object gets
so it can refer to itself. I am not that clear on this which is one of the reasons
I got the book. There are two lines I found right away about this that cast
doubts on the whole book:
> When you become a full-fledged computer scientist, you can come back
> and explain to me the deeper meaning of
> def __init__(self,….
> In the meantime, let's just say that it's always the same abracadabra:
That's it? I should come back and explain what the author is writing about
I cannot relate to the frivolous joking tone and non-explanation for this line
and the "self" keyword. Furthermore, I don't buy a book so I can come back
later and explain it to the author? So, OK, one drop of the ball is not a big
deal, but then just a page or two later this:
> You may wonder why it's necessary to tell Python that the last_name in line 3
> has the same value as the last_name in line 2. That's another one you can
> explain to me when you're teaching at Stanford.
What??? This is the second spot where the books makes a joke when it
should be explaining a concept or at least marking the point for later explanation.
To top that off, within moments of reading that there is a typo:
> For learning purposes, our paper form has only on blank to fill, Last Name.
"On blank" should be "one blank"
I don't what kind of quick, careless slipshod writing this is, but this is unacceptable.
If you write a book about a subject, you must know the subject well enough to
explain it, and have good enough skill with language to write to be understood,
proof-read your writing, and find ways to explain concepts, not joke about having
your readers explain them to you.
This book looks like a beginning student's notes from a programming class that
includes, but glosses over the subjects and issues that the student did not understand.
This is unacceptable. Do not buy this book. 1/5
I recently purchased "A Smarter Way to Learn Python" and I am just flying through it. I got it a few hours ago and I'm already approaching chapter 20 :)
It's like with each book release the writing gets better, the examples more enjoyable–surprising because his first books are already amazing and well written, the coding exercises really encouraging, fun, and progressive–and with the exercises relating to Mark's newest release, I'm thoroughly enjoying myself to a point where I don't want to stop learning and practicing.
I really wish all books dealing with a learned skill were like this.
Just to sum up my story, around the summer of 2015, I was a total newbie at web development, struggling with HTML...HTML! I didn't know how to conjure up a simple website well at all. Didn't quite know how to properly use CSS either.
But it all started with Mark Myers first book. I am very grateful for his way of teaching that enables one to learn well with great efficiency.
His Python book is just amazing, it keeps true to his "read a little, practice more" type of learning which really gets the information to stay with you.
I already can't wait for his next book, I wonder what it will be :)