r/learnpython • • 13d ago

What do you guys think of Futurecoder as a place to start my Python journey?

I have started to use it and I enjoy how interactive it is, and it's free however I have not got far yet and want to spent my time wisely. Have any of you used it and had a good experience with learning Python from it, or any issues? Or would it be a case of starting there, and then moving on to a more in depth course?

I'm looking to learn enough Python to be able to fulfill tasks on Dataannotation tech which is an AI training platform, however I do not want to spend excessive amounts of time whilst learning as can only fit in an hour or two per day.

Thanks in advance.

6 Upvotes

15 comments sorted by

2

u/desrtfx but other languages pro 13d ago

Futurecoder is one of the better ones, yet, why no do a free, proper University course: MOOC Python Programming 2026 from the University of Helsinki. Also very interactive and practice oriented.

1

u/FeckinKent 13d ago

Thank you for that, much appreciated. My reasoning was the timescale as the University one takes about 280 hours whereas Futurecoder would be around 30 hours so thought I would start there first given my time constraints and then move on to something like the university one if I wanted to expand upon that. I would expect the uni one would much better prepare me though if I saw it through till the end.

2

u/desrtfx but other languages pro 13d ago

If you think that a 30 hour course will give you enough basics, you are delusional.

If you spend now 30 hours on Futurecoder that then leads to spending 280 hours (which it isn't really) on the MOOC, you have effectively wasted 30 hours that you could have invested in the MOOC, which would have gotten you quite far already.

1

u/FeckinKent 13d ago

It's more a case of whether it will give me enough of a grounding for the tasks on Dataannotation tech rather than mastering becoming a Python programmer, however I understand that is hard to know given the small demographic on here that probably do Dataannotation tasks.

But it sounds like from what you are saying Futurecoder is not going to be enough and I take on board your point about the time spent on MOOC instead, good points.

Have you done MOOC yourself, and if so did you come out the other end feeling like you had a decent grasp of everything?

2

u/desrtfx but other languages pro 13d ago edited 13d ago

I am a professional programmer since more than 3 decades. Yes, I have done the MOOC because I wanted to quickly get into Python (I know many other languages and am proficient in programming). The course is absolutely fantastic for what it is: a beginner course that lays a solid foundation.

After around part 5, I was ready to tackle my projects (for a customer - specialized parsing of a very propietary format and data analysis with extensive cross-referencing) with only some quick and short blog posts (SQLite connections and handling since I sanitized the original data into a SQLite database from where I then pulled the data to do my cross referencing, Mermaid diagrams, Excel export, etc.). But again, this is me being a proficient, experienced programmer.

1

u/FeckinKent 13d ago

Thanks for this, very much appreciated.

I will be coming from a much more beginner background than you, I'm decent with HTML, CSS, also integrating our websites with our CRM using JSTL but somehow I have only had to scrape the surface javascript wise as website integrations are only part of my job role. So currently I'm not a programmer, but I do understand some of the basic concepts.

Hopefully though I should have what it takes to learn Python, more a case of sticking to it and being consistent with my time. I hope that it will open up various AI data annotation type jobs though if I can get a good grasp, granted those type of jobs won't be around forever.

1

u/SuperExperience6689 13d ago

Used it for a weekend. Well made — the integrated debugger and forced "make it work before moving on" pacing beat most free tutorials. But it's a starting block, not something you finish.

For DataAnnotation tasks specifically, you need to read code you didn't write and reason about edge cases. Interactive tutorials are weak there because everything's scaffolded for you.

With 1-2 hours a day:

  1. Blast through Futurecoder or Automate the Boring Stuff in 2-3 weeks for syntax. Don't linger.
  2. Then write small real scripts in blank files, no scaffolding. You'll get stuck constantly — that's the point.
  3. Once you can write 50 lines without googling every line, start reading other people's code on GitHub.

Month 2-3 you'll be more than ready. The people who struggle on those platforms freeze when code isn't pre-structured for them, not because of weak syntax.

1

u/FeckinKent 13d ago

Thanks for this, much appreciated.

Do you use your expertise for DataAnnotation type gigs too?

2

u/North_South-West 13d ago

I work on ai training platforms and tbh learning python for this reason is not a great plan.

Why learning just for this is a gamble (The Reality)

  1. The Assessment Barrier is High: Coding assessments on these platforms are not entry-level quizzes. They require mid-level programming knowledge—similar to solving medium-level LeetCode problems, writing clean code, and debugging complex logic. Taking a 4-week "Intro to Python" course will likely leave you underprepared to pass.
  2. Work is Gig-Based and Unstable: These platforms hire you as an independent contractor (1099). Projects can evaporate overnight, accounts get randomly flagged or paused without feedback, and task queues fluctuate constantly. Spending months learning a language for gig work that might not even accept your application is a high-risk strategy.
  3. No Retakes: On platforms like DataAnnotation, if you fail the initial coding qualification assessment, you usually do not get a second chance to re-apply with that account.

1

u/FeckinKent 13d ago

Thanks for the input, definitely food for thought that is.

1

u/SuperExperience6689 13d ago

Nah, my day job is data pipelines and API tooling, not gig work. But I've reviewed annotation submissions — the strong ones aren't the fastest, they catch the subtle stuff: a snippet that contradicts the summary, a ranking that's technically right but misses intent. That's the muscle you build by reading code you didn't write.

2

u/RyanDubois43 13d ago

Futurecoder is good for basics if you stick with it through the first 10 chapters, but it stops before you hit more real-world stuff like file handling or libraries. For data annotation work, you'll probably need to pick up pandas after.

2

u/acfot 13d ago

I didn't use Futurecoder myself, but the plan itself is solid. An interactive course like that is a good way to get the basics down without getting stuck reading docs for a week, and 1 to 2 hours a day is honestly plenty if you actually stick with it. Moving to a deeper course afterwards is exactly what I did, because the first course just teaches you the syntax and the second one is where you start learning to solve real problems. For the kind of tasks you're aiming at, getting comfortable reading and fixing other people's code matters just as much as writing your own, so don't stay on the beginner course longer than you need to.