Reddit reviews Learn Python the Hard Way: A Very Simple Introduction to the Terrifyingly Beautiful World of Computers and Code (3rd Edition) (Zed Shaw's Hard Way Series)
We found 19 Reddit comments about Learn Python the Hard Way: A Very Simple Introduction to the Terrifyingly Beautiful World of Computers and Code (3rd Edition) (Zed Shaw's Hard Way Series). Here are the top ones, ranked by their Reddit score.
Pearson P T R
Buy this book first.
Learn Python the Hard Way: A Very Simple Introduction to the Terrifyingly Beautiful World of Computers and Code (3rd Edition) (Zed Shaw's Hard Way Series) https://www.amazon.com/dp/0321884914/ref=cm_sw_r_cp_apa_i_WgE2Db53ZBZ58
Then set aside 1-3 hours a day to do the lessons, read the book and/or look up additional material on the internet.
The first chapter or the introduction tells you to try and memorize basic powershell commands, its useful but don't spend too much time trying to get them all down.
[Here](Learn Python the Hard Way: A Very Simple Introduction to the Terrifyingly Beautiful World of Computers and Code (3rd Edition) (Zed Shaw's Hard Way Series) https://www.amazon.com/dp/0321884914/ref=cm_sw_r_cp_api_A4dTAbN5P7PEM)
Edit: the name of the book has parentheses in it so the link isn't very pretty.
Learn Python the Hard Way
and
The Definitive Guide to SQLite
The first one will teach you python, the second one will teach you SQL using one of the simpler engines to manage. Once you've got that down, MySQL, Oracle and Postgres are similar to a point.
> Right now I don't even know the limit of what can be done with Python. Idk what it is used for.
Literally anything - Django is one of the most popular web frameworks. You have PyGame if you want to make video games. Heck, it's even used in Deep Learning via Theano. You can also use it as a script language - be it as an "addition" to a different language in your application or a separate script to run. Easily ones of the most versatile languages.
Of course there are certain aspects of a language that might make it not suitable for specific tasks too. You do need a Python interpreter installed on your computer to make use of programs written in it after all (meaning it's pretty much useless for embedded devices), it's raw performance is but a small fraction of what C++ can do (but in exchange it's much easier and faster to code) so it's probably not the best choice if you want to write your own server/game engine/computation heavy application.
As for where to find some tutorials - I would look for Learn Python the Hard Way, it's pretty often recommended. Despite the name, it's not hard. There's also Automate the Boring Stuff with Python.
But learning of a language itself is like knowing words in a foreign language. But you still need to understand how to make sentences in it. So I also suggest visiting /r/dailyprogrammer to do their beginner and intermediate level quizes and/or eventually getting a book on algorithms and data structures. This should be enough for you to understand how to actually program things.
Afterwards it's a question of what you WANT to do, it will be a good time to pick up a project to work on. Be it a game, website, some kind of a program - whatever. This is where you learn the most but also a time when you won't find answers lying directly in the books and you will need to self study while understanding how to use google/ask correct questions.
I've read this book: https://www.amazon.com/Learn-Python-Hard-Way-Introduction/dp/0321884914
And I have also used: https://www.codecademy.com/ quite a bit and I highly recomend it!
And it's awesome and accessible because its free! Check it out here. There's also a physical book you can buy here.
In no particular order:
The big thing is to learn concepts! Technology changes fast but understanding why backups are important and how they should work or why access control is important doesn’t.
I mentored at DevBootcamp localhost here in Columbus, Ohio and have worked as a software developer for the last 10 years (6 of which in consulting for startup companies). I don't know what program you'll be attending, or the curriculum they teach. Not all bootcamps are created equal, and if you have a scholarship I HIGHLY RECOMMEND you do extensive research into which program you'll be attending.
So first off, I want to say beyond a reasonable doubt, you should do it if you have an interest in software development. I don't want to discourage you from wanting a better life, and it's absolutely true that the best companies hiring devs don't give a shit about your degree or lack of it. The best developer I ever met had a Masters in Psychology, and I've met PLENTY of devs with CS Master degrees that couldn't code their way out of a paper bag.
A degree has no bearing on your ability to be a great developer.
That said, there are three things that will. Practice, patience, and passion. Software development isn't for everyone, and staring at a computer for 8 hours a day desperately trying to get something "simple" to work, that isn't working (sometimes for weeks at a time on a single bug) can be incredibly frustrating. It requires patience, very strong problem-solving skills, lateral thinking, creativity and a DEDICATION to life-long learning.
What you learn in your bootcamp will be invalid (or rather legacy code) in 2-3 years. You must keep learning, above all else.
That said, as much as I believe great developers can come from anywhere, I honestly think you need to have a mind for it. A sort of natural talent. It is completely possible, that you'll find you if you do this, that you're not cut out for it. If you go to a good program, they will guide you through that. Do not let it discourage you in your goals for a better life. For me personally, I struggled a lot in the beginning. I almost dropped out of college, twice. But I kept going, and that innate talent started showing itself.
For some people, they get programming right away. For others, like me, it takes awhile. And for others still, no matter how hard they try they just aren't capable of it. Walk this thread carefully. At first, it will seem like you understand 2% of what people are teaching you. It's like going to China without learning mandarin first. Everything will be confusing as fuck. You're going to think "This isn't for me. I can't do it", but odds are you can. If you are struggling seriously think "I can do this" over "I'm not cut out for it", especially if that 2% starts turning into 10% and then 15% and so on. In this case, it just means you need to get across some barriers to learning. Keep at it.
On the other hand, if you are doing everything you can to learn, and you've put in a TON of work and time and you're not retaining 5% of the stuff you're learning (or keep forgetting the same simple concepts over and over) after you've been doing it for awhile, do not be ashamed to throw in the towel. You gave it a shot. The only way to know if this line of work is for you, is to try it.
Here's how.
Before you start this bootcamp you need to start programming today. Like right now. Seriously. NOW. I don't give a shit about how your situation might be holding you back. Crash in the park. Start couch surfing. Go to the library. Find local tech events. Buy a shitty laptop off craigslist and dump linux on it, and start hacking. Go through this and this and this and this and this and this and buy this book. Start EASY. Pick the simplest looking thing, something targeted to kids, or middle-schoolers and start there and work your way through whatever you can. DO IT SLOWLY. Understand the fundamentals. It will seem like your not accomplishing anything for awhile (as far as writing cool looking apps). It's not a race. Understand what is going on with the code. Why does it do what it does? Why does it keep erroring? Why isn't the compiler doing what I think it's doing? Ask Questions. If you don't understand something, and you get stuck, go learn something else about coding, and come back. Learn to walk around problems. You're not going to get everything all at once. Some concepts are REALLY hard at first. Go learn the easier stuff first, then come back and try to climb that mountain again.
One of the most common thing people learning programming have told me, is that they did not realize it took so much effort just to do seemingly simple things. You will be surprised at the amount of code you have to write to get something to work, and you will beat your head against the wall every step of the way while you're learning. The compiler will fight you. The program will crash. The code just won't work, and it will seem completely unreasonable why. Shit will break without telling you, or giving you obvious error messages. Just realize, that every problem is a wall, and every wall you knock down gets you closer to your goal.
Once you feel like you can't learn anymore on your own. THEN start your bootcamp. Have a list of questions ready for the bootcamp. Write down specific things you weren't able to learn on your own, that you need help with there. ASK A SHIT TON OF QUESTIONS. Get a mentor and bug the ever living shit out of them.
Top 5 things that will fuck with you while you're learning.
---
Now, for the reality check, after you graduate. It's extremely unlikely you'll get a job as an entry-level dev in Omaha (I looked up the stats) for more than $60k/year. It will take you at least 5 years to work up to $100k/year and that will require you to learn at an incredibly breakneck pace (and to hop jobs about once every 2.5 years). To get to that level of skill you will need to be writing code, on average 60 hours or more a week, and you'll need to experiment with shit that you aren't using at work and work on side projects at home. You'll need to do this non-stop.
Lastly, even with DevBootcamp (which I think is an absolutely great program), the graduation rate was around 60%. Not everyone makes it, and even of those that did, not everyone got jobs. You need to go in there with everything you got, and even if it doesn't work out at the bootcamp, DON'T STOP PROGRAMMING. If this is what you want to do, and you keep learning, you can do it. I promise you. Just don't pump yourself up thinking it will be a cakewalk and you'll make out with a nice job in the end. It might not happen. If it does and you find yourself at a nice company, and you aren't putting in the work to learn, and grow, soon you'll be without a job and without the ability to find one. But if you work hard, and break through every wall that is holding you back, and you persevere you will make it in the end.
The life of a developer is incredibly rewarding, and I would love to use some library you write in 3 or 4 years that makes my life easier. So go give it a shot, give it everything you go. Don't let failure (or the fear of it) hold you back.
Good luck.
Well...
http://www.amazon.com/Learn-Python-Hard-Way-Introduction/dp/0321884914
However you'd better get used to work with documentation in electronic form. Besides other thing it allows you fast browsing and searching over the text.
Learn Python the Hard Way was recommended to me by one of the tech managers I work with. Note that I haven’t read it yet, but it’s on my list per his recommendation.
Edit: it’s late and I formatted the first link backwards.
I second Python as a great beginner language.
Here you go /u/moonknightspidey - http://learnpythonthehardway.org/
You don't have to buy the book, it's available through the web site for free. If you prefer a physical book: https://www.amazon.com/Learn-Python-Hard-Way-Introduction/dp/0321884914
The person I'm replying to also recommended Ruby. Zed Shaw also wrote a ruby book.
Online (free): http://learnrubythehardway.org/book/
Print: https://www.amazon.com/Learn-Ruby-Hard-Way-Computational/dp/032188499X
And if you're feeling crazy then you can learn you a haskell (don't do this).
Bookmark these for when you get into C later:
http://c.learncodethehardway.org/book/ Same guy who wrote Learn Python the Hard Way. The online (free) copy of Learn C etc is incomplete, but is now available in print in full: https://www.amazon.com/Learn-Hard-Way-Practical-Computational/dp/0321884922
Then there's beej: http://beej.us/guide/
And the obligatory TCP/IP book: https://www.nostarch.com/tcpip.htm
If anyone's wondering about why I just spammed the shit out of Zed Shaw's books, it's because his writing style is very easy to get into and keeps your attention. It's anything but dry, and focuses on making you write code, break it, and figure out why it broke.
There are other good Python books as well, like this one: https://www.nostarch.com/automatestuff
And here's another No Starch book on Ruby (I like No Starch - Absolute OpenBSD is a great reference) - https://www.nostarch.com/ruby
Learn Python the Hard Way was written a long time ago. The most recent edition of the book was released about one year ago. Since then, many of the top downloaded packages have been updated to support Python 3: currently 165 of 200 of the top packages support it.
There isn't a strong reason for beginners to start with Python 2, unless they absolutely need a Python 2-only package.
Try finding a book with exercises. I haven't used it, but I'm told this one works pretty well for Python: http://www.amazon.com/Learn-Python-Hard-Way-Introduction/dp/0321884914
I struggled to keep my momentum up, as well, and ended up taking a course at a community college. This helped me stay motivated, as I felt a sense of competition with my classmates.
If it has to be a book, my only advice is do the opposite of what I did. I got Learning Python, 5th Edition, which is a huge, dry book. It's great, but it was daunting & more than was even good for me to know about at the time. I would suggest any guide meant for beginners.
I should mention that Learn Python the Hard Way & Automate the Boring Stuff with Python are the standard suggestions. I still suggest a beginner's book, but this is what the community likes.
That being said, I usually insist that people follow this order.
1) CodeAcademy's course on Python
a) It only teaches you things that are essential.
b) It provides you with an editor & a runtime environment. These two steps may become a little confusing later, but it's good to not have to tackle them all at once.
c) It provides training that is still hands on
Note: I specifically suggest doing the course more than once. As many times as needed to feel excruciatingly bored and unchallenged by it.
2) Lynda's Learn Python 3 Standard Library. It is free through the Public Library. It is a series of videos so it is not hands on, but it helps you see what is possible before you're able to write it. Knowing what is possible is a big part of the process. Once you know what is possible, the how is often mostly irrelevant & figured out with Google.
Note: I specifically suggest watching the videos more than once. As many times as needed to feel excruciatingly bored and unchallenged by it.
3) Only here do I usually suggest a book. Any book will do, but once you're swimming in ideas & have been prepped & re-prepped. You should be ready to go.
There is a very good chance that installing Python, picking en editor & running the code will give you a hard time. Python is a pain to set up in Windows the first time you do it. Though, if you're running Linux, it's seamless. Once you get here reach out to me (or /r/learnpython). There are some tricky steps, but once you're up and running, you won't look back.
Good luck. If you have any trouble with any part, shoot me a message.
Edit: I like this guy's setup too. https://www.reddit.com/r/learnpython/comments/6f7ybq/_/dig45b0?context=1000
Learn Python The Hard Way
Reading Rainbow
http://smile.amazon.com/dp/0321884914/ref=wl_it_dp_o_pC_nS_ttl?_encoding=UTF8&colid=2A173IT97LDXL&coliid=I364I660611P3T
Hope I linked it right
If you are a beginner coder like myself (someone who procrastinates and is distracted very easily, most of the time by random subreddits :) This method of learning python has helped me tremendously:
Shaw does a great job at breaking it down into small chunks to consume and a lot of repetition typing code so you get familiar and comfortable before he moves on to more difficult concepts; at which stage if you follow the exercises and do the study drills the concepts should be easier to understand.
Learning python the hard way actually turns out to be the easier way in the end
Okay yeah sorry, I'll try to do more research on the reddit next time. A less knowledagable friend suggested I try my hands on with VBA and, I asked my more knowledgable friends about that and php. He said that VBA is kind of outdated and PHP, although easier, is really specific for what you want, and Python encompass both VBA and PHP better. Do you agree with that?
Also is this the book you were talking about? https://www.amazon.com/Learn-Python-Hard-Way-Introduction/dp/0321884914
My friend said he said he heard good things about this book https://www.amazon.com/Automate-Boring-Stuff-Python-Programming/dp/1593275994?ref_=nav_signin&
What do you recommend?
THIS