Domain Driven Design (DDD) is a methodology I’ve heard about more and more over the last year, from technical book clubs to interviews. It focuses on how you design your application, including the language and naming used within it. Namely, everything should match the business domain it is serving, a so-called “ubiquitous language”.

“Scott! I need you!!”

“Oh, Meg’s calling me, I got to go. I’ll talk to you later sis.”

I could tell from the sound in her voice what had happened

I recently had the priveledge to attend the Recurse Center, which if you have not heard of, you should definitely check out. It was a really interesting time to attend, given the current global pandemic we all are finding ourselves in now. The entire experience was moved online,

Previously, Explorable Places used Capistrano to deploy to one droplet in DigitalOcean. This setup had a number of downsides and limitations. Among them,

At my work, we use Marko as our templating engine, which supports progressive rendering out of the box. So maybe that is why I took it for granted when I decided I would try to implement the same thing for Explorable Places. There are a few pages there that are data-heavy and it would help