3 ms·
13 years ago. When the Pentium II was around. This is what I don't get about questions about linked lists. They're so utterly irrelevant in 99% of startups tod
by mattmanser 15y ago
13 years ago. When the Pentium II was around. This is what I don't get about questions about linked lists.
They're so utterly irrelevant in 99% of startups today, where knowing how to lay out your classes and methods for maintainability is so much more important than any trivial and pointless performance gain.
The complexity of solutions is at such a higher level now than it's ever been and yet we're still worrying about structures that shaves less than a ms off something that's called once every 10 seconds.
The reason why ruby and python have grown in dominance in the last few years is because you don't actually have to worry about this any more.
- kenjackson 15y agoI don't generally ask about linked lists, but I will say that if you can't reason about them, it's a pretty big red flag. They're an extremely simple data structure. With that said, a lot of startups (and web apps in general) are effectively consumer CRUD apps w/ nice images and transitions. Perf generally isn't important until scale becomes an issue (and until then you're main perf bottlenekck is some DB and/or network code that someone who cared about perf wrote). So I agree. It makes sense to use effectively a domain specific language/framework like RoR when you're in that domain. And linked lists may not be applicable. But I'd still be weary of hiring people for whom reasoning about them is off-limits.