[m3mpp]

Of course you should, you're gonna live a good additional 50 years, do you want to spend them doing something you don't like?

Python is good language to start, concentrate on that first and keep js for later, it's a complex language that may confuse you more than anything else.

Mix theory and practice, learn and build console apps, avoid web dev for now, you don't want to confuse yourself with all the web framework stuff. Your goal at that point should be to learn the language and how to think like a software dev, not learning some apis or frameworks.

27 is a good age to learn, technologies are always changing so, even at that age, you can learn and become an expert at something, and after a few years, nobody will ask you for how long you've done it.

[ax0ar]

Thanks for the advice.

When should I dive into frameworks? What concepts should I be familiar with apart from the basic building blocks (var, loops, control flows, etc)?

[m3mpp]

As you said, the first level is the language syntax, var, control flow etc. Second level, data structures, list and list comprehension, dictionaries etc. Third level, recursion and algorithms, or how to solve problems in python, what you'll often see it referred as "the pythonic way".

Don't be too academic with these that it becomes boring, but just enough that you start feeling comfortable building some small console apps, that can read and write files, crawl some pages from the web, that kind of thing.

Once you're good with that, you can start with frameworks. The danger you want to avoid is to start too soon, and have a hard time separating the complexities of the language with the ones from the framework.

[chipuni]

The MOST IMPORTANT thing is to start practicing, and keep practicing.

Very few people stay motivated to study, unless they have some kind of goal.

So try finding your goal first. Perhaps it would be to create something that would help your life as a journalist.

Then, once you have your goal, try to create it. You'll discover what you're missing. It might be that you don't know how to store things so that they can be found flexibly -- so you then study databases. It might be that your code is far too slow -- so you study algorithms. It might be that you need to plug in functionality that others have written -- so you study frameworks.

Good luck.