gsabo
I've been working a lot on my math skills lately (as an adult). A mindset I've had in the past is that "if it's hard, then that means you've hit your ceiling and you're wasting your time." But really, the opposite is true. If it's easy, then it means you already know this material, and you're wasting your time.
How awesome engineers ask for help
Awkward Moments in JavaScript
Tips for writing internal docs
Hypothesize Your Way Out of the Ebb
Some Fun Hacking Platforms to Try
Xmas Flights: A Biz game
Wizardry – you can ask for anything you want
Simhash protects you from evil fashion
Tips for running HBase on low-memory EC2
Generate syntactically correct nonsense programs in Python
How programmers should write their resumes
How to nail the URL shortener interview question
No spambot could ever be as funny as horse_ebooks
Eight things you need to know about Python 3
Here's why you still need a programming resume
The Prom Server Becomes Sentient
These copyright issues only become interesting when you consider works which assert more transformative power on the samples.
Destroy All Scrollbars
Short Files Are Un-Pythonic
That approach seems similar to learning to program by typing random words into iPython until something happens - it could work, but it's going to take you months to even discover a "for" loop. It's better to read a tutorial and the documentation while experimenting.
I finally caught on to TDD after watching the screencasts at destroyallsoftware.com, and I highly recommend it to others wanting to learn. TDD is a completely different way to develop, not just an additional step on your old routine.