I think knowing the logic behind why things work is pretty vital. Sure, somethings work awesome out of the box, but what if you need an edge case that's not covered there? For some projects, these pre-built SaaS tools are the right choice for the job, for others, you may need to make your own, and in many cases, you'll inherit whatever the company was using before you came onboard.
The "edge case" point you make is definitely convincing.
Would you say that building small, barebone projects (no frameworks, no libraries) is required to demonstrate a good understanding of the fundamentals?
Or should one invest time in learning and utilizing the tools surrounding the basics, and let the interviews challenge his understanding of fundamentals?
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.
I think knowing the logic behind why things work is pretty vital. Sure, somethings work awesome out of the box, but what if you need an edge case that's not covered there? For some projects, these pre-built SaaS tools are the right choice for the job, for others, you may need to make your own, and in many cases, you'll inherit whatever the company was using before you came onboard.
The "edge case" point you make is definitely convincing.
Would you say that building small, barebone projects (no frameworks, no libraries) is required to demonstrate a good understanding of the fundamentals?
Or should one invest time in learning and utilizing the tools surrounding the basics, and let the interviews challenge his understanding of fundamentals?