When Code Becomes Cheap, What Happens to the Engineer?
What becomes valuable when implementation is abundant?
Technical writing on software engineering, systems architecture, and developer tooling.
What becomes valuable when implementation is abundant?
What is life to me? What is life to you?
I have been thinking about that question for a while now, although I am not sure I know what I mean when I ask it.
How We Missed the Joke
The defining artifact of software engineering is not the source code, nor is it the compiled binary.
The following is my own thinking, worked out in fragments and still unfinished.
We have all experienced the particular euphoria of initialization.
We do not all have to go to school or follow the established pattern for gaining knowledge.
The Layer That Leaks
Here is something I think is really interesting about mathematics that we usually never stop to notice: there isn’t actually some inherent “order of operations” built into the universe.
why losing focus is so easy, and why maintaining it is so valuable
On Shallow Modules, Indirection, and the True Cost of Artificial Abstraction
A first-principles exploration of structs, memory layout, and why compilers arrange data the way they do.
How do you actually start a project?
There is no judgment for the wicked, nor rest for the hopeless.
It matters more than it often seems
I want to pose three questions to myself and perhaps others.
I have read Cal Newport’s Deep Work, and while the concept is insightful, I’ve been wrestling with how to actually apply it when you are still searching for your direction.
A promise is given to that which ought to have been.
Is there fundamentally a trade-off between speed and quality when solving problems with code?