that CS stuff you can look up and understand when you need it, like when you&#x27;re looking for an efficient algorithm to do xyz, and so you should have curiosity and a wise intuition but beyond that as a web developer that knowledge should not sit in your brain because it will occupy precious thinking resources that you should dedicate to building great UX and making the code modular and maintainable which takes dedicating brain cells to understanding the world around you, not just a commodity piece of textbook knowledge that makes you feel smarter and covers up insecurities about  having produced dull or even terrible UX -- &quot;hey I know how to balance a red&#x2F;black tree or build a hashmap implementation so I must be a under appreciated genius&quot; when in fact that is commodity knowledge anyone can pick up from Google and a few hours of research and benchmarking (and having ability to allocate regions of your brain to tasks of wildly different nature on the fly which means you never keep crap in your head unless you&#x27;re using it on daily basis)<p>We could write a thesis on this, right? and we would disagree wildly, but in the end go put up your amazing UX n youtube and show me how memorizing the Algorithm Design Manual helped you create that amazing UX. UI work is mostly art and craft, with math&#x2F;cs still relevant but applied from an intuitive dynamic center of your brain, not stored and ready to put on a white board on demand.