_Tyler

Right, but this library is designed only to be used with a fast.ai model (and the hope is that fast.ai practitioners will find it helpful). I suppose you could create your own backend that worked with another library if you wanted to take the time, but that's not how it's designed.

EDIT: Regardless, I've updated some of the language on the readme to be more clear that this is not an official fast.ai product (and made it more clear in the header that it uses fast.ai models), because I do think your criticism had some validity and I really do appreciate the feedback.

Hi! I can see where you're coming from; however, since this product is initially intended to tightly work in conjunction with Render, which uses the fast.ai name in it's repo (https://github.com/render-examples/fastai-v3) and the fact that this model (to my limited knowledge) only works with models produced by fast.ai, making a clear naming distinction was crucial so that someone creating models using another library would realize they couldn't use this. If you have a suggestion for how to make that distinction in a clear and concise manner without coming across as an official product I would definitely be willing to hear you out!

Good question! Like I mentioned in the readme, I'm hoping to add a flask server soon; however, render is recommended on the fast.ai website and is the simplest way to get a model running (https://course.fast.ai/deployment_render.html), so I thought connecting my app to render would be the most helpful way for fast.ai practitioners to get started.

OP here: I shouldn't have added the word 'etc' to the list of things it classified, but have changed the readme to show a full list of objects that the demo works with. My intent was not to make a classifier for any and all objects, to serve as a demonstration of what someone could use the app for.

I would push through if I were you, because I was in the exact same situation only a few months ago.

I had wayyyy less experience than you, and took over most of the work for a react/typescript/node project that was MASSIVE compared to anything I had worked on before (static websites and small Django projects).

I felt like I could cry and started having issues with heartburn for the first month, and even told my boss about 2 weeks in that was not qualified for the job. Thankfully, they told me that they knew that it would take a while, and encouraged me to stick with it.

Even now, 7 months in, there are still so many things I'm learning, but I would really recommend pressing in to the job, (especially if your manager has the wisdom to see that it will take you a while to get up to speed), as after I had been there about 6 weeks things started to make a little more sense.

Also, if it makes you feel any better, the stack overflow survey from 2018 shows that 44% of devs expect a new coworker with 4 years of experience to take one to three months to be productive (https://insights.stackoverflow.com/survey/2018/#work-how-lon...), so I think you have less to worry about than you think. I'd keep with it until and unless they make you leave!

tl;dr - You should definitely do it!

I am around the same age, and recently made a shift from a sales career to coding. I started teaching myself python using treehouse (no affiliation) and then moved on to using blogs and such. I was doing this for a few hours a week for about two years, and then got an opportunity only a few months ago to join a small team as a React Native/Typescript Dev.

The learning curve was huge for the first 2 months, and every day I felt so stupid, but a few months in and I am so glad I made the switch. I think that if you are really willing to put in the time and don't mind not knowing what you're doing making the career switch is totally worth it.

a basic Django CRUD app with social logins, an alexa skill using Node.js, and a few static websites

I like it!