3 ms·
I used to think the CS-y whiteboard interview stuff was a complete waste of time. But now I look at it as a way to prove objectively you have a computer scienc
by ilaksh 10y ago
I used to think the CS-y whiteboard interview stuff was a complete waste of time. But now I look at it as a way to prove objectively you have a computer science skill/knowledge-set. Which is nice because it evens out the playing field because many who have the degree don't have the skills and many who don't could acquire them. So its like a bar exam.
There is still an issue though because computer science base knowledge generally lags behind industry-relevant practical knowledge. For example, algorithms and data structures generally accepted as core knowledge do not take enough advantage of today's relatively high RAM availability. And there is not enough emphasis on higher-level components.
You could argue that everyone has to know that old-fashioned basic stuff well and then layer on newer knowlege or perspectives, but I think some of what is considered computer-science core knowledge should be replaced with newer practical things like understanding components and modules and being able to use contemporary tools.
So maybe less emphasis on optimizing algorithms at the procedure level for starters. It might be more important for most engineers to be good with profiling tools and understand the order-of-magnitude differences between memory/CPU/network latency etc. than do be able to do a third-degree low-memory optimization of a function.
- plussed_reader 10y ago"For example, algorithms and data structures generally accepted as core knowledge do not take enough advantage of today's relatively high RAM availability." Wouldn't it be prudent to keep your algorithms as lithe as possible? I would think an algorithm/scheme that chews up large amounts of ramm would be perceived as inefficient? Kinda like the dumpster fire that is Chrome, currently.
- ilaksh 10y agoCase in point. Read the Google engineering articles describing the work optimizing V8's memory usage. That primarily involved using profiling tools on lots of web pages and then changing the initial size of buffers. But they still have to use relatively large buffers from an old-fashioned CS algorithm perspective and they couldn't make them smaller without impacting performance the other way. And they can't know that without doing the profiling on the whole system. So yes you want functions to be lithe but you have to also focus some time, skills and knowledge on optimizing the entire system using tools and real-world data.