Also I think knowing data structures is essential cos you are using them ALL the time you just don’t know it cos you never bothered to learn them. But they are corner stone of every program.
On the other hand imagine how much could you get done if you worked 16 hours a day. Why even take vacation? Imagine how much time you are wasting when you are off on vacation. Oh wait, studies have shown that amount of hours sat in the chair doesn't translate directly into quality work. It might work when you are doing it occasionally as a one-off but won't work everyday.
>Also I think knowing data structures is essential cos you are using them ALL the time you just don’t know it cos you never bothered to learn them. But they are corner stone of every program.
Did i say that? I know what a graph, BST, Tree, Linked List, Stack and Queue is. Do i know fancy algo's off the top of my head? No. But i also know how and what to google and how to convert that pseudo-code into actual working code.
Probably a lot less. Exercise is associated with better mental acuity and reduced risk of mental deterioration with age[1].
Edit: Oh, and if you instead trade sleep for learning you're shooting yourself in the foot as well[2].
[1] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3951958/
[2] http://healthysleep.med.harvard.edu/healthy/matters/benefits...
You'd reach burnout extremely quickly. You'd literally go insane. Your body would break down rapidly. None of these are good for anyone involved.
Disagree.
Most data structures fall into four categories:
1. Basically a list/array/set
2. An association (map/hash table/dictionary)
3. A struct/record
4. A union/enum/choice amongst finite options
It is only in specialised algorithms and when strictly necessary that one must deviate from these (and the second two aren’t even really data structures). In such situations it can be useful to have other things known but even then I think a lot can be done with some combination of:
1. Binary tree
2. Trie
3. Hashing and Bitvector magic
4. Canny
I don’t think much is lost by getting stuck and needing to research in such cases.
I like programming as much as the next person here but i'm not going to code 80 hours a day. I also like going to gym and working out, riding my bike, playing soccer and hanging out with friends.
Companies these days expect you to have side projects or contribution to popular open source libraries while having a job. Oh and did i mention asking you questions about algorithms and data-structures that you most likely haven't used in years and won't be using for foreseeable future?