chewbranca.com

---


layout: post
title:  "Emacs + EDTS + (big)CouchDB... a journey"
date:   2014-03-14 21:05:46
categories: tech
tags: emacs edts couchdb bigcouch erlang
---



If you use Emacs to write Erlang, you might have heard of
[EDTS](https://github.com/tjarvstrand/edts). It's a recent Erlang
development suite for Emacs, and it has some impressive features, but
it can be a beast to get setup and working properly with CouchDB and
the BigCouch merge branch.

<p>This is archived from chewbranca.github.io. Old metadata:</p>
<ul>
  <li>layout: post</li>
  <li>title:  "Emacs + EDTS + (big)CouchDB... a journey"</li>
  <li>date:   2014-03-14 21:05:46</li>
  <li>categories: tech</li>
  <li>tags: emacs edts couchdb bigcouch erlang</li>


</ul>

If you use Emacs to write Erlang, you might have heard of
[EDTS](https://github.com/tjarvstrand/edts). It's a recent Erlang
development suite for Emacs, and it has some impressive features, but
it can be a beast to get setup and working properly with CouchDB and
the BigCouch merge branch.

---


layout: post
title:  "On the Viability of Erlang Releases and CouchDB"
date:   2014-05-07 20:17:51
categories: tech
tags: erlang releases couchdb deployment
---



There has been some discussion on what versions of Erlang CouchDB
should support, and what versions of Erlang are detrimental to
use. Sadly there were some pretty substantial problems in the R15 line
and even parts of R16 that are landmines for CouchDB. This post will
describe the current state of things and make some potential
recommendations on approach.

<p>This is archived from chewbranca.github.io. Old metadata:</p>
<ul>
  <li>layout: post</li>
  <li>title:  "On the Viability of Erlang Releases and CouchDB"</li>
  <li>date:   2014-05-07 20:17:51</li>
  <li>categories: tech</li>
  <li>tags: erlang releases couchdb deployment</li>


</ul>

There has been some discussion on what versions of Erlang CouchDB
should support, and what versions of Erlang are detrimental to
use. Sadly there were some pretty substantial problems in the R15 line
and even parts of R16 that are landmines for CouchDB. This post will
describe the current state of things and make some potential
recommendations on approach.

---


layout: post
title:  "Rewriting the CouchDB HTTP layer"
date:   2014-08-17 10:19:23
categories: tech
tags: erlang couchdb http chttpd2
---


With the light at the end of tunnel on the BigCouch merge, I thought
it was time to get the conversation going on cleaning up the current
HTTP stack duality. We've got a good opportunity to do some major
cleanup, remove duplication, and really start more clearly separating
the various components of CouchDB.

<p>This is archived from chewbranca.github.io. Old metadata:</p>
<ul>
  <li>layout: post</li>
  <li>title:  "Rewriting the CouchDB HTTP layer"</li>
  <li>date:   2014-08-17 10:19:23</li>
  <li>categories: tech</li>
  <li>tags: erlang couchdb http chttpd2</li>

</ul>

With the light at the end of tunnel on the BigCouch merge, I thought
it was time to get the conversation going on cleaning up the current
HTTP stack duality. We've got a good opportunity to do some major
cleanup, remove duplication, and really start more clearly separating
the various components of CouchDB.

---


layout: post
title:  "Does this thing still work?"
date:   2018-04-20 09:35:51
categories: general
tags: blog
---


Is the mic on? Does this thing still work? It sure has been a while
since I've updated this site. Truth be told, I don't really care for
the current technology I'm using to power this site. I've got a
handful of grand ambitions on what I want a personal "homepage" to be,
but they all require a considerable chunk of development time, which I
haven't invested in yet. As a result, I typically don't bother

<p>This is archived from chewbranca.github.io. Old metadata:</p>
<ul>
  <li>layout: post</li>
  <li>title:  "Does this thing still work?"</li>
  <li>date:   2018-04-20 09:35:51</li>
  <li>categories: general</li>
  <li>tags: blog</li>

</ul>

Is the mic on? Does this thing still work? It sure has been a while
since I've updated this site. Truth be told, I don't really care for
the current technology I'm using to power this site. I've got a
handful of grand ambitions on what I want a personal "homepage" to be,
but they all require a considerable chunk of development time, which I
haven't invested in yet. As a result, I typically don't bother

---


layout: post
title:  "Lisp Game Jam - Day one update 01"
date:   2018-04-20 09:35:51
categories: lisp-game-jam
tags: gamedev lua love2d lisp game-jam fennel
---


I'm very excited to be diving into the [2018 Lisp Game
Jam](https://itch.io/jam/lisp-game-jam-2018)! My plan is to make a
Diablo-esque pvp deathmatch game! I stumbled upon the awesome open
source [Flare Game](https://github.com/clintbellanger/flare-game) that
is a single player action RPG inspired by Diablo. What really
intrigued me about the game is all of the artwork.

<p>This is archived from chewbranca.github.io. Old metadata:</p>
<ul>
  <li>layout: post</li>
  <li>title:  "Lisp Game Jam - Day one update 01"</li>
  <li>date:   2018-04-20 09:35:51</li>
  <li>categories: lisp-game-jam</li>
  <li>tags: gamedev lua love2d lisp game-jam fennel</li>

</ul>

I'm very excited to be diving into the [2018 Lisp Game
Jam](https://itch.io/jam/lisp-game-jam-2018)! My plan is to make a
Diablo-esque pvp deathmatch game! I stumbled upon the awesome open
source [Flare Game](https://github.com/clintbellanger/flare-game) that
is a single player action RPG inspired by Diablo. What really
intrigued me about the game is all of the artwork.