If you're building something technical, the authority for final decisions must rest with someone capable of truly understanding what can actually be built.
Any kind of synchronous debate is more a charisma competition than a way to discover the truth.
The term is so loaded, and evokes both fear and awe way more than current systems deserve.
By building more accountability into crowdfunding, we can make it safer to fund unknown creators and large projects.
We could have genuinely open and sustainable open source, but we need to slightly tweak our social expectations.
Easy but clear binary operators, chainable everything, and better whitespace sensitive concepts.
Using the Shape Up methodology to balance the requests of community members and the contextual expertise of builders.
What does the open source social contract demand?
A new way to support open source work that fluidly allows any kind of community governance.
The solution to broken social media is obvious: democratic cooperative ownership.
Iterative media could be a better way to think about meaningful ongoing work, and could improve personal blogs, research journals, and a lot more.
By avoiding effect aware functions a language hobbles engineers and makes programs sloppier than they could be.
If we can figure out a new business model to support real journalism, we can create a better kind of journalism institution. And that could be just the start.
Statically typed languages really feel incomplete without true macros, so I hacked that functionality together for typescript.
We all implicitly assume that elections are events that begin and end. What happens if we get rid of that assumption?
By only focusing on making ourselves laugh and feel better, we're failing to actually make any progress. We have to start persuading conservatives, not just mocking them.
My first attempt used a recursive system that was too opaque and potentially confusing. By pulling apart the different qualities of the library it's much more clear now.
I got annoyed with the sass feature freeze, and decided to just implement retrievable properties myself. Here's my first try.
Various scripts to solve various freelancing problems.
The Gear Guide area of the skiracing.com needed to be updated and improved.
A page showcasing the background and role of each of the Skiracing.com team.
The user paywall and reporting tool needed to be fixed and improved for the skiracing.com team.
A system allowing the skiracing.com team to mark their articles with a sponsor.
A streamlined and intuitive subscription page to reduce complaints to the skiracing.com team.
Our modern storytellers are trying to tell ever larger and more complicated stories in movies, but the genre isn't up to the task.
Star Wars is different and special, and all because of the very first line.
The first version of this blog was written in the Meteor framework.
A small side project I did in response to the difficulty of putting together a crowdfunding budget that won't end up screwing the creators.
I built my current piano studio website with Meteor, and it has several interesting features.
An Ember.js app I was building for my piano studio that I scrapped once I discovered Meteor.
A Digital Systems Design class project I did in 2012.
A series of python scripts for managing my customers, website, and studio.
An android app I built out of irritation for how difficult it was to change my contacts' custom ringtones.
Before the simple-schema and autoform packages appeared in the Meteor ecosystem, I cobbled together a package to automate form validation, among other things.
The first website I ever built and deployed, when I was just barely learning about web development. It isn't well made, but I see myself in it.
A school report I chose to write in html.
Facebook and the other social media sites use your participation to hold you hostage to an ecosystem they (mostly) created: the closed social network. But it doesn't have to be that way.