patrickcteng
With GraphQL, you're just pushing N+1 calls and figuring out the mental contortion needed to support all the graphy-ness from non-graph structures. Most that say GraphQL is the bees-knees must be an FE developer. There's nothing wrong with that, but GraphQL is just NOT as cracked up to be.
Now, as an adult, I find that I have my screen's brightness turned up way more than my peers. For example, although it's currently very sunny right now in LA, I have my brightness turned up 100% on my 16" MBP. Though, in the evenings, it's more comfortable at 3 or 4 steps down from 100%.
I can't help but to wonder -- did she condition my eye to be less sensitive to light and have thus slightly ruined my low-light vision?
I use those History skills daily from writing documentation, synthesizing concepts into a coherent work, and figuring out the intent of the original coder.
My History degree is definitely not useless.
Maybe it's because I code in multiple languages daily, but I tend to not use a lot of the language features for each language. A part of it is definitely thinking about the ones that come after me, and wanting everyone -- from every background -- to be immediately able to reason about the code without having to look up what every syntax feature does.
I guess it's a fine line between depth of language features used vs. readability once one is gone from the project.