3 ms·
Yeah, so they threw you in over your head. Sorry about that. If they let you sink, it's not all on you and don't be afraid of the next gig because not all compa
by awb 5y ago
Yeah, so they threw you in over your head. Sorry about that. If they let you sink, it's not all on you and don't be afraid of the next gig because not all companies are like that.
As others mentioned, I'm also entirely self-taught and it comes from personal projects.
I'm sure you've seen it, but if I was going to learn it I'd start here: https://fastapi.tiangolo.com/tutorial/ https://fastapi.tiangolo.com/tutorial/
Then I'd build something for myself, something that actually works, that I actually deploy. Because so much learning comes from doing.
Pick a project you want to launch, or build an open source tool. After 3-5 you might feel quite comfortable. But it probably will require a lot of extra time outside of work. I learned Rails outside of work and I spent most weekends and a few nights a week for a month before I felt comfortable enough to work on production code.
I also like video tutorials, so maybe try Googling and see if there's a YouTube video series that clicks for you. Sometimes the medium of spoken word just works better for me than reading.
The other thing to remember is that no two projects are the same. The FastAPI project you might be working on might be in a very different style than the ones in the tutorials. Just so you don't overwhelm the other dev, maybe write down a few questions in the morning and ask them all at lunch time. Otherwise, if you're asking every hour it might get overwhelming.
Good luck!
- Arisaka1 5y agoThank you. To be honest, I haven't really asked them much, because they (senior devs) have their own plate full, and I'm only trying to ask project-specific questions not things that I would find on Google. Also, I'm feeling like I may get too obsessed with syntax. I author multiple anki cards throughout the day. Some are things like "difference between concurrency and parallelism", while others are like "3 ways to add a new item in a list", "docker command to run a container detached".
- LilBytes 5y agoThe Senior devs are there to help out new starters, especially those that have just started their career let alone starting a new job. I respect they might be busy but two new starters who are at an equivalent experience level should be getting support. Reach out to them, find the one that has the best personal skills and lean on them. If they are really busy make sure you're making the most of their time. * Take notes * Ask good questions * When they provide you information, ask for them to provide you a link to supporting documentation so you don't need to ask the same question twice Even with all of this, you might not get the support you need. If that happens, it's not a reflection on you but a reflection of the organisation or it's current (or permanent) situation.