... because we've allowed it to become what it is.
Leetcode is the industry standard because developers continue to humor this stupid hazing ritual. That is what it is.
Let's not pretend that real-world developers don't spend 75% of their time Googling how to do X on the job.
Let me use Google on a technical interview if you actually want to test my ability to solve problems in the real world. That's what your developers are going to be doing day in and day out. They're not going to be regurgitating D&S textbooks for brownie points.
"Oh, you had to Google that? I have my entire D&S lecture notes memorized."
Companies (unicorns in particular) rarely do let you use resources during a tech interview. They're looking to see if you're willing to endure the Leetcode grind. If you are, great! You're more than ready to become yet another cog in the FAANG wheel.
Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
Let's not pretend that real-world developers don't spend 75% of their time Googling how to do X on the job.
Especially if you frequently move from project-to-project and language/framework-to-language/framework, you now how to solve the problem but you probably need a refresher on the specifics of how to implement it in the language or framework you're being asked to use. Let's face it: if you didn't know how to solve the problem, any useful Google searche-results would be nearly blind-luck.
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.
... because we've allowed it to become what it is.
Leetcode is the industry standard because developers continue to humor this stupid hazing ritual. That is what it is.
Let's not pretend that real-world developers don't spend 75% of their time Googling how to do X on the job.
Let me use Google on a technical interview if you actually want to test my ability to solve problems in the real world. That's what your developers are going to be doing day in and day out. They're not going to be regurgitating D&S textbooks for brownie points.
"Oh, you had to Google that? I have my entire D&S lecture notes memorized."
Companies (unicorns in particular) rarely do let you use resources during a tech interview. They're looking to see if you're willing to endure the Leetcode grind. If you are, great! You're more than ready to become yet another cog in the FAANG wheel.
Especially if you frequently move from project-to-project and language/framework-to-language/framework, you now how to solve the problem but you probably need a refresher on the specifics of how to implement it in the language or framework you're being asked to use. Let's face it: if you didn't know how to solve the problem, any useful Google searche-results would be nearly blind-luck.