Why did I decide to go to grad school? I don’t know. It’s a decision that feels like it’s been forever in the making. I have had an interest in hardware since my undergraduate days. I’ve read online plenty lately that most developers think all there is to this field is web development. Most developers that I know locally this is definitely the case. SaaS culture and other startuppy concerns dominate the day and the programming that I first heard about was a niche pursuit and discipline.
My degree program will be in Computer Engineering, which I’ve heard from plenty of people online is a bad idea. Why? Because it’s not relevant anymore, but why is that such a pervasive argument? It’s a common refrain too to hear from people that money isn’t as good. When did money become the chief aim of education? I understand that people need to make a living, but I want to learn about hardware because it’s fun! Having a family now too, I want my kids to see my learn about something that isn’t strictly required but nonetheless is being pursued.
In understanding the computing stack all the way down, I also want to know when the abstractions that we use are too much and put too much of a burden on the software that we write. Plenty has been said about this, but slapping layer after layer of abstraction on things (coupled with AI writing code for many now) leads to layers that you may not understand and code that doesn’t work exactly the way you want it to. In his post https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-abstractions/, Joel Spolsky says it best. He used to work in just C code that could come straight from the K&R book. Now, he requires many books to keep up with all the abstractions present in the stack. Abstractions break, and a lot.
So my goal? To peel back the layers of abstraction for myself and see what’s inside. Looking forward to getting started.