I talked to a close friend approximately two years ago, and at that moment, he decided - while having a promising career in corporate finance - to learn Python "just for himself." With later transitioning to crypto, I guess this helped him immensely. And some people, like myself, need time to catch up with essential skills.

There were some thoughts I played around with for some time before donning my explorer's hat and diving into Python. "In the world of ever-present AI, Python is your friend." "What else do you want to fill a few hours of your day for the foreseeable months?". The main reason was much more prosaic: rebuilding ThinkPink with a razor-thin team requires wearing multiple hats simultaneously. I estimate that we're now better off with at least one person capable of reading and comprehending Python. It took me a few months last year to jump into JS; now it's Python time.

Short term plan looks like this:

• Learn the basic syntax, data types, and functions – enough not to feel overwhelmed by the simplest things.

• Dive into the technical debris of machine learning and AI algorithms.

I know it's stupid to write something in the style of "here's how you should learn duh," but for purposes of accidental fun, I'll share my go-to sources as of now:

• Replit's 100 Days of Code is solid and practice-oriented, with occasional mistakes here and there (some commentators on YouTube videos highlight them pretty accurately)

• Python All-In-One For Dummies by John C. Shovic, Alan Simpson. Yeah, I got that one from Shkreli's videos. A good book and probably the most comprehensive one at this stage of my involvement with Python.

A few random observations so far:

• Knowing JavaScript helped a lot. But honestly, that's the case with any previous experience coding.

• For an untrained eye like mine, the Python world looks more friendly: fewer brackets and more readable syntax.

• Indentation is a matter of life and death.

I talked to a close friend approximately two years ago, and at that moment, he decided - while having a promising career in corporate finance - to learn Python "just for himself." With later transitioning to crypto, I guess this helped him immensely. And some people, like myself, need time to catch up with essential skills.

There were some thoughts I played around with for some time before donning my explorer's hat and diving into Python. "In the world of ever-present AI, Python is your friend." "What else do you want to fill a few hours of your day for the foreseeable months?". The main reason was much more prosaic: rebuilding ThinkPink with a razor-thin team requires wearing multiple hats simultaneously. I estimate that we're now better off with at least one person capable of reading and comprehending Python. It took me a few months last year to jump into JS; now it's Python time.

Short term plan looks like this:

• Learn the basic syntax, data types, and functions – enough not to feel overwhelmed by the simplest things.

• Dive into the technical debris of machine learning and AI algorithms.

I know it's stupid to write something in the style of "here's how you should learn duh," but for purposes of accidental fun, I'll share my go-to sources as of now:

• Replit's 100 Days of Code is solid and practice-oriented, with occasional mistakes here and there (some commentators on YouTube videos highlight them pretty accurately)

• Python All-In-One For Dummies by John C. Shovic, Alan Simpson. Yeah, I got that one from Shkreli's videos. A good book and probably the most comprehensive one at this stage of my involvement with Python.

A few random observations so far:

• Knowing JavaScript helped a lot. But honestly, that's the case with any previous experience coding.

• For an untrained eye like mine, the Python world looks more friendly: fewer brackets and more readable syntax.

• Indentation is a matter of life and death.