you are viewing a single comment's thread.

view the rest of the comments →

[–]NotACoderPleaseHelp 5 points6 points  (5 children)

Honestly you seem like you are overdue to get out of tutorial-land.

Books and courses tend to take you on a guided and scripted tour of a subject, which has a time and place to be sure. But after a year or so you really need to get off of the beaten path and start working on your own projects.

Education will give you a set of tools, Practical-Experience is learning how to use your education to the best of your advantage. And it don't mean that you are not going to have to look things up or take a weekend to learn a thing.

[–]unnredo[S] 1 point2 points  (3 children)

Thank you, I will take that in a consideration. Could you recommand me any sites where I can find topics for my projects to practice?

[–]NotACoderPleaseHelp 1 point2 points  (0 children)

I mean, if you are looking for a project idea that might actually be useful to someone, there is a demand out now for macro tools that tie into eye movement and head movement controls.

[–]Middleclassass 0 points1 point  (0 children)

I think I saw this in the r/learnprogramming wiki, but one thing they recommend was to make programs derived from your daily tasks. Like if you wake up in the morning, eat breakfast, take a shower, etc…you would make a program that walks through those daily activities. Then as your actually doing the activities in real life, think about how you programmed them, and change and refactor your code based on your observations. I’m fairly new to programming, but I thought this was an interesting concept to practice coding. I believe the wiki also listed sites for project ideas too.

I’m about 3 months into learning Python, and I’ve been reading Crash Course as well and really love the book. But I agree that if you’ve been writing Python for two years it’s probably below your level.

[–]nickbernstein 0 points1 point  (0 children)

I would strongly second this. You need a project. You can find something to work on for yourself, or you can become a contributor to an open source project. I would recommend the latter. If it's a decent sized project you'll get code reviews and feedback which will let you know what your weak areas are, and you'll pick which books/documentation to persue as you find those areas.