Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
sariel7334128dOne of two things is happening here.
1) they don't see the type of experience you think you have. You should update your resume or provide a small portfolio of products you have worked on and what your role was in them.
2) they are inexperienced and are reading these questions from some blog on "how to find the best node dev"
Crost4169128dIn my experience a CV isn't really trustworthy. Never assume anything when interviewing someone.
rov3rand0m1263127dI was once asked the version number of a language I used in the past.
I replied that I didn’t remember and anyway it was not important as everything changes too fast.
He said it was important.
So I asked what version were they using then
He replied that he had to ask the lead programmer
Oktokolo7567127d@vvinu9876: If you have millions of lines in Fortran, what you need is someone who can do Fortran. Doesn't matter how fast the industry moves.
Same for any other "tech" that is well-established in a company. Can't just dump it all because hippest framework of the week has arrived...
Oktokolo7567127d@vvinu9876: Also, it is impossible to not rely on any "tech" - as the manifestation of the solution to the problem has to be written in _something_ and probably needs to use _some_ framework/API/libs. As it gets written, the comitment to the used "tech" is factually done.
Surely you can always rewrite or upgrade - but that isn't free. And it might be impossible depending on the size of the existing code base and resources of the company. Legacy is the norm - not the exception.