There is nothing about learning how basic data structures and algorithms work that won't help you in your day to day development.
You might be "fine" without it in a certain category of job, but rather than be dismissive about it you could be excited about having a massive wealth of information that you can use to do your job better.
There will always be something else to learn, wether it be how to apply Domain Driven Design to your work or how to work with graphs when munging data.
It's always worth it.
> There is nothing about learning how basic data structures and algorithms work that won't help you in your day to day development.
Having a basic understanding of these things is NOT the same as being able to regurgitate them on a whiteboard, under the stress of the interview process.
The reason we test for things is to verify you have enough domain knowledge to "look it up". A bad interviewer will ask you to write quick sort on the board, because if we've already gotten to the point of "implement quick sort" yeah we can just look that up. However, if you're given a collection of nodes and asked to do something with them; that's a bit more interesting. If you know nothing about graph traversal, or have never seen a tree (both not uncommon in people claiming to be principle engineers in my industry) how do you even know what to search for? Best case is you're smart and waste time coming up with a new solution from first principles; most likely it just never gets done.
Gentoo taught me Linux. The Handbooks are really good.
I think that much of early Gentoo ideas - the OpenRC init system, the ports system, the handbooks - were inspired by BSD traditions. OpenBSD and FreeBSD each have good documentation. Working through the FreeBSD handbook, and then study of McKusik's BSD Book [0], are a good way to get another perspective if you get into this sort of thing.
Just like the other non programming book on the list(Thinking Fast and Slow) GEB is a lot about perception to me.
Understanding that nothing is purely logical nor is it purely expressionistic; by pigeonholing your perception of any design whether it be Code, Math or Art to either Logic xor Expression you are blinding yourself
The other angle for GEB is design
I read GEB along with Design of Design years ago following my mentor at the times suggestion, I would highly recommend doing this.
Think of it as the Gödel, Escher, Bach, Brooks (Although Brook's writing style can be laborious at times)
Recognizing patterns in all design work helped my understand my own design process better.
I'd suggest you pay a visit to your nearest ER and have the staff there give you some advice.
Melancholic depression, fairly often is a symptom of other known health problems, that we as humans have ways of alleviating.
I'm sure you've spent time and effort towards trying to solve what you are wrestling with now, but if you would like to give it one more chance the best possible thing you could do is pay your nearest ER a visit.
Thanks for advice. This is long term. I don't need nor want er. I want to die.
This is a lifetime desire. I decided as a child this world was shit. I've since seen more and more reasons to never procreate, and my desire to die has been consistent.
I've seen enough of this world. Thank you again. You're doing your part. Some people just want out, however.
I respect that, and accept that you have the right to your own life.
You and your life have had great meaning to me and I will forever be thankful for that.
You might be "fine" without it in a certain category of job, but rather than be dismissive about it you could be excited about having a massive wealth of information that you can use to do your job better.
There will always be something else to learn, wether it be how to apply Domain Driven Design to your work or how to work with graphs when munging data. It's always worth it.
[edit] Run on sentence