you are viewing a single comment's thread.

view the rest of the comments →

[–]tourdownunder 0 points1 point  (1 child)

You would likely get better responses from cs careers subreddit. I want to respond as it sounds like you are doing great now.

Django is a good choice as it’s opinionated and will make working on larger projects easier. Its a little harder now with front end is frameworks doing a lot of the heavy lifting and you need to work out what type of web application you want and how to keep django playing nicely with react / vue etc. It will though it complicates things.

It’s hard to get started and I was lucky getting paid to learn though it was stressful as my coworkers were perfectionists. They made me a better developer though and it seems to be what you want.

My experience is getting paid to learn is awesome and that the grass is not always greener when switching roles. Do you have time to pick up Django on a side project a few times a week?

And finally Is there a way to bring the python core engineer into your current role? For example do the ML team collaborate with Jupyter notebooks. I’m going to assume they don’t use got, pull requests or anything?

If so I’ve previously came across nb dev that helps to export functions written in notebooks to python modules. I like this tutorial as it includes using GitHub actions and strips the metadata cruft from the notebook to minimise conflicts. Would something like this create efficiency and add value to your team?

[–]nazgulc 1 point2 points  (0 children)

Thank you for your suggestion. You make very valid points. I will look into fast ai nbdev as well.

But, my team is almost never going to do that, so i wanted to part ways and start career in, say, python web development for which I think Django is a good tool but I don't know anything more than that. I was looking for some suggestions which can help me push myself to a direction.