Who Am I? Why Am I Doing This?
Why did I start a publishing company? Why is it focused on computing? Why Invisible and Seamless Technology? This entry answers some of these questions.
Learning In Public
The Shaded Garden is a digital garden combining thinking and learning with a pen in hand. We plan to publish as our learning happens. The Shaded Garden shows not just the path but also the dead-ends and back tracking required to discover knowledge. If you like exploring, this is a place for you. Below you can find a list of our entries.
Why did I start a publishing company? Why is it focused on computing? Why Invisible and Seamless Technology? This entry answers some of these questions.
Markdown is ubiqutous and really good for basic drafting, but I've found the process of actually using it for a content publishing pipeline frustrating.
Build versus buy is an often debated topic. For Skriptble Press, we've opted heavily for build. In this entry, we'll discuss why we've done this and evaluate some of the arguments against building your own stuff, showing why it often makes sense to do so.
In this second part of the Build Your Own Stuff series, we're discussing some of the challenges that we encountered while building a custom static site generator for the Skriptble Publishing and Skriptle Press websites and publications.
Hardware has advanced a lot over the last 70 years. These advancements are difficult to comprehend. In this entry, we dig into one way to represent those advancements.
In this dispatch, we discuss message passing and its lack of a satisfactory definition. We attempt to define such a definition using distributed systems terminology and contrast it with shared memory.
In part three of the Build Your Own Stuff series, we discuss adding proper <title> tags to our website pages and improving internal linking for the websites.
Designing your own identifiers is a fun exercise, but you can sometimes get distracted by the more basic things. In this dispatch, we discuss a recent deadend path involving probability, collisions, and entropy.
Software powers the modern world and it's quite expensive to develop. So why is it that so much software is written, maintained, and given away for free? In this entry, we discuss freely available software, how it relates to commercial software, it's unsustainability, and joy.
In this second part of the series on The Joy Economy, we discuss a potential solution to economy's lack of sustainability: money. While many operate on the theory that we can simply buy our way to sustainability, the way the joy economy functions suggests otherwise.
A question I had when thinking about the two software economies is why the Joyous Software Economy, with a fraction of the resources, is consistently able to produce software of equal or higher quality compared to the Commerical Software Economy. This entry provides a conjecture as to why: there is a ceiling that caps how productive software development can be.