As a frontend developer, I get stuck during interviews whenever I am asked to solve an algorithm problem.
So, I am asking do you really need to know algorithm to be classified a good (frontend) developer?
For further actions, you may consider blocking this person and/or reporting abuse
Sreeju S -
Vincent Kipyegon -
Mainak Chattopadhyay -
Moisés Santos -
Once suspended, oghenemichael will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, oghenemichael will be able to comment and publish posts again.
Once unpublished, all posts by oghenemichael will become hidden and only accessible to themselves.
If oghenemichael is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to Oghene Michael.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community safe. Here is what you can do to flag oghenemichael:
Unflagging oghenemichael will restore default visibility to their posts.
Top comments (4)
Solving that kind of interview questions is something I always struggle with. I understand they are trying to see if you, as a candidate, can tackle complex problems. The problem is that the way they force you to solve them is not realistic.
I'd say that aside from the context of the interview, a developer should be able to solve algorithm-related problems, because that'll help them face harder problems down the road. It doesn't matter really if you're a front-end or back-end, or data architect or whatever, these types of problems should be something you can tackle.
That's my take on it anyways.
Yes, learning them and being able to solve them hardens your mind for stronger challenges.
And also, I think (some of) the unrealistic approach of some interviewers is also an issue. Thank you for your insight.
Probably stepping into a minefield, but here goes ;-)
Yes and no. Knowing algorithms (and design patterns, for that matter) and how they're put together inform how you approach problems you'll encounter as a developer.
Most of the time there's not much cause to create your own sort, search, etc. from scratch -- we all tend to reach for a library -- so it is possible to get by without them.
But if something with the library isn't working the way you think it should, you won't understand the fundamental concepts that would help you to solve the issue.
Put it like this: Learning will only make you better. Algorithms are no exception.
As an aside: Keep in mind that there's no one who knows every algorithm. I think we all encounter a few basic ones then tend to drill down into others that we encounter, have a specific need for, or just find enjoyable.
Thank you for your insight. It is very relatable.
Personally, I have taken it upon myself to learn more about algorithms (including design patterns).