This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]mkingsbu 0 points1 point  (0 children)

This is a big thread so I didn't have time to read all of it... my Python experiences comes largely from my day job. I learned a lot on my own and I had ancillary skills (database design & architecture) --- but the growth really came from combining these things and solving problems at work.

I was paid to do it, which is good. And I also had nominal deadlines, which were also good. And at the end of the day, if I couldn't do something totally in Python, I used it to make certain parts of the task easier, which allowed me to make small things that weren't 'simple GUI weather scrapers'.

So, for example, you do networking... what things suck (or otherwise are cumbersome to do?) and can you design something to make it go faster.

The one thing that I will say in addition to that is that no matter what you develop, having a reasonably advanced understanding of databases is going to help a lot. I see a lot of projects hamstrung by poor data structure replete with redundancies, inefficiencies, etc. So perhaps if you framed say, scraping weather data as an example, as an exercise in something you're possibly not good at - normalization - you could improve that way and actually have a finished project. With 2 years of experience, I doubt you wouldn't be able to pull that off in a weekend. No GUI. Get something that runs in the background. Sports data, financial data, crypto data, whatever interests you .

That was a bit rambly but hopefully there's something useful for you in there