The crux of my issue is, "Is it always this time consuming?"
Is this just not what I should be doing?
Does that sound like you? It's something I hear a lot.
You're a Python programmer. Knowledge is your lifeblood; you turn caffeine and specs into functional, tested, beautiful code that makes your business money. Maybe you've even released some code as a library so other people can use it.
But you wonder…
- "Is my learning curve steeper than most?"
- "How can I learn to build bigger, better, and faster applications?"
- "Where can I go to learn more than basic syntax—the idioms and cultural values?"
- "How can I keep up with new technologies?"
- "What process do I go through to figure out how to write this thing?"
- "How can I learn the real power of the language?"
To completely answer these questions, you have to keep up with the whole Python ecosystem. And that's like drinking a river: there's always more of it than you can handle. And besides, you'd rather be knee-deep in code than searching for information you may or may not eventually need.
But not having the answers to these questions makes you feel behind, like you're stagnating. That sucks, and of course it means that you could be missing out on much simpler solutions to your problems.
I've also found that Python is deceptively simple, and the more I learn, the more I start to feel that things that have annoyed or puzzled me about the language are really trivial, compared with the rather huge things of which it's capable.
How much better would your life as a programmer be if keeping up with the ecosystem was simple, and you were able to do so in minutes per month?
- You'd know you were learning efficiently.
- Your skills would increase faster–like shifting up on a bicycle.
- Problems you find hard would become simple.
- The code you write would become more "Pythonic".
- New technologies could solve your problems more simply.
- And you could finally learn the real power of the language!
And while you're thinking about this… what if, while doing the learning itself, you produced useful byproducts: libraries, art, blog posts? What would that do for how you feel about your work?
What if that knowledge came to you, and let you learn it as you wanted?
The most important thing I used to learn Python (and any other language for that matter) was a useful project. If you've got that then you can't go wrong.
I run STL Python, a hundreds-strong Python meetup group in St. Louis, MO. These are problems my members have constantly, and I have them too! There's a lot of river to drink out there.
That's what setattr is for. From start to finish it's designed to help you learn what you need to do your job in the limited time you have.
When you use setattr, you get:
- Recommendations from the best of the Python ecosystem.
- Short videos packed with the kind of knowledge you need.
- Exercises to take that knowledge from "what was that thing…" to knowing you're picking up the right tool for the job.
- A community of like-minded learners who keep you motivated.
All this on top of things you've come to expect: the videos are DRM-free, setattr works great on your phone or tablet, and I'll answer any questions you might have right away.
If you're not ready to buy yet, no problem! How about a free video and exercise set? You haven't got all the time in the world, let setattr give you the advantage of learning more efficiently. Just put your email in the box below.