Far future coding
It's good to think long term.
This morning, I was designing a programming exercise for a course I will probably release a year from now. Maybe two.
Yes, that's a long time.
And the reason it will take a while, is that in order to code up the complex component this lab challenges you to create....
You have to know a LOT.
You have to know a lot about very advanced coding in Python, like:
- Writing decorators... a "dark art" fewer than 1% of Python developers ever learn.
- And not just the basics of decorators... but the super-advanced level even expert Pythonistas rarely get to.
- You need to fully exploit "magic methods"... special hooks in Python's object system.
- You need to master UX design... even psychology... to create a component interface that's easy to use, while hiding insanity-inducing complexity that would make Cthulhu proud.
- You need to creatively leverage type annotations... A newer feature of Python that is still little used, and even more poorly understood.
- You need a deep understanding of Python's object system, and how it ties in to Python's memory model.
- And finally, you absolutely must have a level of abstraction in thinking that requires new cognitive skills... new ways of calculating, visualizing, insight and thinking... using resources of your mind most humans never tap into.
You need all of these, and more, much more... before you can even START the lab. And there's no guarantee you'd be able to finish it.
Those of you who have been reading this newsletter for a while... you're starting to realize something.
That the road we're walking together here is not just about Python.
It's certainly not just about selling courses.
It's about tapping into your greatest, massive potential as a developer. A level that - out of the ten million software developers on the planet - only a small fraction will ever reach.
(Though maybe we can change that.)
Most people overestimate what they can do in a month, but underestimate just how much they can utterly transform their life in a year.
So, one year from now... where do you want to be?
Do you want to be doing the same things you're doing now? Coding in the same way, thinking the same thoughts, going through the same routine?
Or do you want to be on a different level?
Do you want to be taking on coding projects you never imagined before... and nailing 'em?
Do you want to be the "star" on your team, feeling all the other developers around you appreciating you? Looking up to you?
Do you want to be contributing it outsized ways?
(And - why not - making LOTS MORE MONEY?)
If you don't want this for yourself...
Then this blog, and my newsletter, are not for you. I mean it.
But if you're on board... I'm going to keep pushing you. Because I know your potential.