4 ms·
> You also have to understand data structures like linked lists, queues, b-trees..., and to top it all of understand algorithm analysis to judge the efficiency
by dabockster 9y ago
> You also have to understand data structures like linked lists, queues, b-trees..., and to top it all of understand algorithm analysis to judge the efficiency of the code you write or look at.
While it's true that you need to know how to judge efficient code, the bit about data structures is HR bullshit. If the only indicator about an organization's coding styles during the interview is a bunch of cargo culted questions from HackerRank, then you should think about whether you really want to work there or not.
Remember that hiring is a two way street. As much as you're offering them something, they're offering you a paycheck (among other things). Don't accept a bad deal just because their "innovative".
- locococo 9y agoI am not offering the ultimate truth here, just my opinion. However I notice that people seem to be offended by the notion that some knowledge of data structures is required. It's a very basic concept of how to efficiently handle and store data. I am not sure what people think a basic requirement for a development job is. Being able to learn is a very low threshold in my opinion, and how do you prove that when you don't have a degree and don't know the basics? See the catch there? Again, If someone want's to be a front end web developer what I am saying is most certainly not required. For anything else I think it holds though.