We need to ship what we started and let our newer contributors shine and lead.
What ambitious web application developers need to learn from game developers. Presented at EmberConf 2018 in Portland.
This is a wide-ranging talk on learning and why you need to understand how people learn if you want to build good software. Plus I build a fun orbital mechanics demo. Presented at
There is definitely an intimidation factor some people feel about integrating things into Ember apps. While there are plenty of things I want to make easier too, I think a large amount of
"Mens et Manus" (latin for "Mind and Hand") is the official motto of MIT. Lots of schools have Latin mottoes, and they are usually pretty bland. But mens et
When Google set out to measure what makes their best software development teams successful, they found a strong correlation with psychological safety: A shared belief held by members of a team that the
“A lot of beginners under-appreciate the degree to which googling things is part of a programmer’s job,” says @steveklabnik #wednesdaywisdom pic.twitter.com/FnXo3rBfPb— Glitch (@glitch) May 31, 2017 That quote
Lots of software projects struggle when they try to implement search-related features. I was reminded of this by @trek's reaction to this Algolia marketing tweet: Development teams often delay building search due to
Many people have expressed an interest in contributing to Cardstack and have been clamoring for some docs to help them get started. This is the first of three posts I intend to ship
There is a strain of thought in the web development community that believes there's a tension between having comprehensive developer tools and delivering good user experiences: This is exactly backwards. At the scale
The most reliable way to evaluate programmer candidates is to hire them to do a bit of realistic work. This is widely understood, but not widely practiced. The biggest barrier is finding projects
The amount of complexity a single human programmer can handle is fundamentally limited. Until our brave cyborg future comes, even the best programmers can only hold so much in their minds at once.
There are two very different kinds of simplicity in software engineering: simple interfaces and simple implementations. Simple interfaces are absolutely critical, because the budget for interface complexity is paid out of your head.
An inflammatory anti-Rails post has been getting lots of discussion lately. The author's frustrations are legitimate, but his articulation of the problem takes an absurd turn: The really challenging part in this discussion
Drupal project lead Dries Buytaert recently launched a community discussion by asking "should we decouple Drupal with a client-side framework?". My high-level takeaway from the discussion is that the Drupal community