All the time! I used to work for an agency, and Devs were very much hires for their ability "to figure stuff out and get it done", regardless of the stack.
I think it can be very daunting, especially at first. My observation is that usually coding newbies adapt much better to that environment than longer serving developers who have an area of expertise (I guess probably because the newbies are more comfortable not feeling like experts!)
My strategy when starting with a new project/language/stack depended on whether there was already a codebase or not.
If there is an existing codebase, I tend to start by following through the code on a few user journeys. It gives me a good sense of how things are hanging together and what the conventions of this language are. I would then dive right in, using previous code as a reference point and Google as my language coach 😂 The principles of good code are largely consistent across languages and frameworks and I'm often surprised how quickly you can get going. I'd then look for some informal learning courses or opportunities online (e.g. a cheap udemy course)
If there's no existing codebase I would spend a lot more time on formal learning (ideally through something more official than udemy), finding a good course to complete or other developers to learn from.
Over time I've grown to love the challenge of a new language or framework, and I think a lot of that has been because with each new language/project I feel a little less like an imposter. I feel way more comfortable now in owning what I don't know, questioning and asking for help without feeling like I am failing for doing so.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
All the time! I used to work for an agency, and Devs were very much hires for their ability "to figure stuff out and get it done", regardless of the stack.
I think it can be very daunting, especially at first. My observation is that usually coding newbies adapt much better to that environment than longer serving developers who have an area of expertise (I guess probably because the newbies are more comfortable not feeling like experts!)
My strategy when starting with a new project/language/stack depended on whether there was already a codebase or not.
If there is an existing codebase, I tend to start by following through the code on a few user journeys. It gives me a good sense of how things are hanging together and what the conventions of this language are. I would then dive right in, using previous code as a reference point and Google as my language coach 😂 The principles of good code are largely consistent across languages and frameworks and I'm often surprised how quickly you can get going. I'd then look for some informal learning courses or opportunities online (e.g. a cheap udemy course)
If there's no existing codebase I would spend a lot more time on formal learning (ideally through something more official than udemy), finding a good course to complete or other developers to learn from.
Over time I've grown to love the challenge of a new language or framework, and I think a lot of that has been because with each new language/project I feel a little less like an imposter. I feel way more comfortable now in owning what I don't know, questioning and asking for help without feeling like I am failing for doing so.