shortpgh

when working on technology products, we solve problems as we see them instead of as our audience sees them.

When working through ideas or designs (brainstorming), don’t state a problem without having a solution.

When creating and describing digital products, we use the term "user" too much and it's a problem. Substituting a more meaningful term helps with your internal communication, decision making, and empathy.

have you ever tried to throw a ball at a target? I bet you missed.

What makes up a good development environment? These are the principles that I follow to build my development environments.

Building a static web app limits the amount of things that you have to maintain to build an app. But I’ve been wondering to myself -- Is this cost effective?

A reality map helps you define the real world process you are trying to solve. It's my favorite way to start a new software project.

Static web apps have an interesting architecture. The app is front-end based and uses 3rd party services instead of having it own server component. The architecture sounds simple -- you just need to build a UI. But the separation can make things complex because you have to mash up different services. This is my attempt to identify the architecture. I also want to outline it so I can see how this can work for a non-static web app.

The Web Speech API gives you the capability for both text-to-speech and speech-to-text in your web sites and applications. And it's easy to work with.

Chrome's DevTools is one of my favorite development tools. It is one of the best - if not the best - tools available to web developers. I provide some reasons why I believe this.