:wq - Writequit

I am currently employed as a core developer for Elasticsearch Inc, working on Elasticsearch itself. I've worked on a number of parts of ES, including:

• Disk-based shard allocation
• Circuit breakers
• The simple_query_string query
• The Groovy scripting engine and (now removed) sandbox
• Translog checksums and the translog truncation CLI tool
• Shadow replicas
• Plugin checksums
• Cluster Allocation Explain API
• Adaptive replica selection and automatic queue resizing
• Index and Snapshot Lifecycle Management
• Data Tier formalization
• Node Shutdown API

I've also contributed some patches to Lucene itself:

• Support for slop and fuzzy to the SimpleQueryParser
• The MatchNoDocsQuery

And also a bunch of other various stuff :)

clj-http is an open-source idiomatic HTTP client for Clojure that uses the Apache HTTP client. It supports a ton of features that Apache's client supports, and uses the middleware patterm (if you can call it a pattern?). I took over clj-http from Mark McGranaghan a ways back.

Cheshire is an open-source JSON encoding/decoding library for Clojure, using Jackson's³ java library. It was designed to be as fast as clj-json, but still allow custom encoders for various Java objects. It also has some experimental stuff like encoding a stream into a single field without copying it twice (once for the source, once for the JSON string).

es-mode (aka Elasticsearch-mode) is a major mode for Emacs to send requests to Elasticsearch. It supports the same syntax as Sense⁴, as well as completion, indentation, and formatting of responses. It also supports executing ES requests from org-mode, which I use a lot in my everyday work. It also supports some neat things Sense doesn't have, like auto-tablification of aggregations and Elasticsearch Command Center.

java-imports is an Emacs library to deal with managing import statements in Java source code. Since I am employed working on a large Java codebase, it came about as a necessity for my own use.

This replaces the blog below. No guarantees on what sort of content it will have. It's mostly going to be non-technical.

My email newsletter. I only recently started this. A curated selection of things I’ve found interesting recently, or things from my commonplace book. May include theology, literature, philosophy, art, music, and technology.

This is a static copy of my old blog. It hasn't been updated in a long time, but it could still be useful for reference. It's mostly technical posts, though there are a few others scattered about.

This is my all-in-one Emacs configuration (along with Zsh) designed to do as much as possible in Emacs, using the wide range of tools available. It's a collection of .org files tangled into a configuration. The source for it can be found here on github. It's quite extensive. I used to be a hardcore Vim guy, but had to switch to Emacs for work in 2010 and have been using it ever since.

My old all-in-one configuration (called "The Setup", github) is still available, in case someone references it.

A collection of various notes, examples, and how-to documentation for Elasticsearch. Whenever someone asks a question on IRC that requires me to do some sort of research, I add it here.

Listing mostly defunct projects (everything else has moved to my github account).

I've collected a few notes about it, since a lot of people seem not to understand how it works. It includes some good links to blog posts and videos and various settings.

I switched to git-annex for distributed file backups in 2014, so I am keeping some notes here for others or in case I forget how to use it. It has a slight learning curve because I used the CLI instead of the git-annex assistant.

With the proliferation of dozens of different packet analysis tools, a network traffic analyst has a dizzying amount of tools to choose from to analyze network data. As the number of tools will only increase, a framework to unite and manage each of these tools is necessary. This framework should provide a central and uni ed way to change the options for each of the tools. My solution to this problem is NSM-Console, or the Network Security Monitoring Console.

This paper was written as in introduction to the NSM-Console project I originally created while working on the HeX FreeBSD-based live CD.

NSM practitioners and packet analysts rejoice, the HeX System is a project with your best interests at heart.

Scientists are continually faced with the need to express complex mathematical notions in code. … we demonstrate and provide applied, scientifically substantial examples of functional programming which we present as the multi-language RudolF source-code repository for software integration and algorithm development, which generally focuses on the fields of machine learning, data processing, bioinformatics.