In my perspective, once you get how to build a CRUD, you're a developer! People overthink things saying that you need to know a set of tools in order to work or get the job.
Why a junior dev should know by heart technical concepts, pros and cons? How much experience they have to state something they haven't experienced yet?
I usually say that there are topics juniors are not prepared to understand. And that happens to every level of seniority!
Some might say that I'm crazy or that I'm not a good professional... But why recruiters still requiring an extensive list of skills, frameworks and even 3 years plus of experience for juniors?
Building a CRUD has enough complexity to learn how to develop quality software! Then, as it goes, you'll see that new knowledge will be required in order to make that software better and better!
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.
Short Answer: Know how to build a CRUD.
In my perspective, once you get how to build a CRUD, you're a developer! People overthink things saying that you need to know a set of tools in order to work or get the job.
Why a junior dev should know by heart technical concepts, pros and cons? How much experience they have to state something they haven't experienced yet?
I usually say that there are topics juniors are not prepared to understand. And that happens to every level of seniority!
Some might say that I'm crazy or that I'm not a good professional... But why recruiters still requiring an extensive list of skills, frameworks and even 3 years plus of experience for juniors?
Building a CRUD has enough complexity to learn how to develop quality software! Then, as it goes, you'll see that new knowledge will be required in order to make that software better and better!