I'm currently a post-doc doing language technology/NLP type stuff. I'm considering quitting soon to work full time on a start-up. I'm working on three things at the moment.

• The start-up is a language learning web app: http://www.cloze.it . What sets it apart from other language-learning software is my knowledge of linguistics, proficiency with text processing, and willingness to code detailed language-specific features. Most tools want to be as language neutral as possible, which limits their scope a lot. So they tend to all have the same set of features, centred around learning basic vocab.

• Something that's always bugged me about being an academic is, we're terrible at communicating to people outside our field. This means that whenever I see a post using an NLP tool, they're using a crap tool. So I wrote a blog post explaining a simple POS tagger that was better than the stuff in e.g. nltk (nltk is crap): http://honnibal.wordpress.com/2013/09/11/a-good-part-of-speechpos-tagger-in-about-200-lines-of-python/ The POS tagger post has gotten over 15k views (mostly from reddit), so I'm writing a follow up about a concise parser implementation. The parser is 500 lines, including the tagger, and faster and more accurate than the Stanford parser (the Stanford parser is also crap).

• I'm doing minor revisions for a journal article on parsing conversational speech transcripts, and detecting disfluent words. The system gets good results when run on text transcripts. The goal is to allow speech recognition systems to produce better transcripts, with punctuation added, and stutters etc removed. I'm also working on a follow up paper to that one, with further experiments.

Overall the research is going well, and I find it very engaging. But I'm at the point where I have to start writing grant applications, and selling software seems like a much better expected-value bet.

This is about personal improvement. My wife and I have parted in september and that is the major life change I have been 'working on' with all my rationality. Incidentally most changes by that are complete now.

So this is a good point to announce and pre-commit on writing a post on dealing rationally with a major life crisis (as I believe I did). I planned and started to write that post but I am not sure how to present the case esp. without giving too much private details.

Maybe you can help:

• Is there interest in such an account? What kind of interest?

• Are there any existing posts on dealing with a major life crisis on LW?

• What questions would you like to see answered by such a post?

• Would you like to discuss this topic in private?

• Would you recommend such a post for Main?

Note that I don't need counseling and gladly are psychologically healthy despite being the one who was left with four children by my wife for another one. I also don't need recommendations or further readings as I researched the topic sufficiently in depth during the hard times (I will provide some references on this in my post).

For the curious: The solution I orchestrated is that my wife and her new significant other now live in a house we bought (mortgaged) over the street and the children live in both houses (since today). And we negotiated a (notary) marriage contract that spells out the terms of the whole thing.

Interestingly I hit on LW not long before the breakup (no: LW had no part in that) and it did help to deal with the situation sanely (maybe you can find some hints in my posts from that time; I got much strength from things we did right esp. for the children).

I will post the writeup on Monday, January 20th, 2 AM CET at the latest (or refrain from it altogether).

I am translating the upcoming Sequences ebook to Slovak language. At the moment of writing this, the first of the six parts is fully translated and converted to DocBook, which allows me to export it to PDF, HTML, EPUB and a few other formats. Also, a half of the second part is translated but not converted yet. (For anyone interested, the first part in PDF is available at this temporary link.)

If anyone else is interested in translating the ebook to their language and would like to use the DocBook technology, I would be happy to help: to explain the system, share my scripts and configuration files, provide some tips and best practices about the technology in general and its use for the Sequences; also how to use non-English characters. Actually, I could even coordinate multiple volunteers for your language, so you could just focus on translating one chapter at a time and ignore the big picture. (I have some experience with coordinating translators in an open-source project.) A short introduction: you write each chapter as an XML file (just like in HTML, only with different tags), and the details of converting the XML files to the resulting format are specified separately. You can do a lot of customization, some of it requires merely setting some variables, but you could do anything using XSLT. Installing the whole toolchain on your computer is very easy (at least in Windows); I could send you a ZIP file that you'd simply extract in a directory and everything should work out of the box. (The worst case, if everything fails: you will have to write a simple script to convert the XMLs to some other format you decide to use.)

Why? As a part of attempt to create a rationalist community in my country. I am already translating the web articles (I had the first part of the book mostly covered already), so the book provides me a limited scope for what I was doing anyway. I believe a book has some advantages over blog. One of them: people are used to reading books from the beginning to the end, so you can cross larger inferential distances. With blogs, many people would just read an article or two, and then complain about the text being too long; also the comments are distracting and reading them multiplies the size tenfold.

So the idea is that after translating, I can distribute the PDF files freely, but I can also print a copy or two of the book (each of the six parts would be one physical copy) and lend people the paper version. Assuming they are similar to me, if they read the first chapter and like it, they will be very likely to read it till the end.

There's the overall "move to Portland and start at my awesome new job" Project, which is coming along well. A friend and I drove here from Ohio (pretty much across the entire country) in a little over two days. We drove because I have a very old dog that I didn't want to fly. My POD arrives tomorrow, and I'm excited to have all my things back in my possession (I didn't bring any nice shirts or sweaters with me, so I've been feeling slovenly-ish), but I am NOT excited for having to unpack and move furniture.

More specifically, I'm working on helping to launch the Beekeeper program at Beeminder. If you want to read more about that you can read this blog post we just released on the subject.

Personal-life-wise, I've just started on the "find my tribe here" Project, which I don't like. I like HAVING a tribe (and very much miss the awesome group I left in Columbus), but actually having to go out and either find one or put one together sounds like less fun.

I've been mainly working on my graduate studies, but as a side project I've been working on developing a more efficient way of doing Solomonoff induction. The idea is that Solomonoff induction requires some language over which to construct programs. But most 'formal' languages we know of - such as Turing machines - do not fit well with observed reality, in that you wind up requiring a very large additive constant complexity to the complexity of your programs. So the goal is to find some computational substrate that will not require such large additive complexity. The most obvious solution to this would be probabilistic graphical networks (such as Bayesian networks), but searching through Bayesian networks is extremely hard because there are a huge number of possible network topologies. So my idea is to restrict the network topologies. It is known that ANNs are able to, in principle, simulate any function, but I suspect most ANNs are too crude. Instead, I've been working on combining ANN approaches with hierarchical bayesian networks. I suspect the resulting structure has enough power to produce most sequences found in real life while also being very easy to optimize over due to the recursive structure and the fact that good learning algorithms for ANNs are known. My initial experiments in this direction have been positive; the main goal now is to derive a more efficient learning algorithm and to prove bounds on time- and space-complexity.

I've been practicing stenographic typing daily for the last couple of weeks, but still am not at a point where I have a serious write-up or a better typing speed ready.

I'm working on this mostly to prove to myself that I can see long-term projects through. Sure, the promise of doubling my typing speed on English language input is promising, but it's really too far off to be that tempting. So it's mostly to show that I can keep working on a project if I keep my mind to it. That, and there are some people on this site who are rather interested in how it turns out - how much work it was, how difficult, how long it takes to get good enough at it, etc. I almost forgot the big one: if typing in steno makes a difference in the ease of writing.

When I get significantly faster than my QWERTY typing speed - 140 WPM over my original 90 - I'm doing a write-up on the experience.

Here's links with the software and learning tools I'm using: http://plover.stenoknight.com/ http://qwertysteno.com/Home/

Keyboard: Microsoft Sidewinder X4. You need a keyboard that can correctly send combinations of key presses to the system - it's called N-key rollover - and this is a $50 option that satisfies my needs.

EDIT: I realized that my write up was missing a lot of the actual strategies I used to practice. There are three skills I am working on. Steno theory, keyboard use, and brief memorization.

Steno theory is how you figure out the chords needed for an unfamiliar word. So for the word "needed", I'd type that as "TPHAOED/-D". TPH is the letter N, AOE is the long E vowel sound, and D is the final D. Then the -ed final sound is an unvoiced vowel and a D, so it's a final D. I practice this by typing things using steno - I invariably find words that I don't have memorized chords for, and then I figure it out or fail to and look it up.

The keyboard use is mostly a byproduct of use, with a little bit of http://stenoknight.com/stengrid.png for the multi-key consonants. I got started with the key drills either in qwertysteno or the typing drills at https://sites.google.com/site/ploverdoc/lesson-1-fingers-and-keys

For brief memorization, I'm using the top 100 words drill at http://qwertysteno.com/Practice/Words1.php , and limiting the range to a manageable few common words to spam out quickly (I started with ten). Once there's little thinking involved, it's time to add more words. This is really the nuts and bolts about how to type quickly with steno - the most common words are most of what you're going to be using, so it's where you get the most bang for your drilling buck. Well, if you get hung up on unfamiliar words you're better off working on that - occasionally needing twenty seconds to get a word out is a lot of time even if it's one word in sixty. But the words you want to get faster on are more common, so it's a good tool to get the most common words practiced first and most.

I'm working on a new imperative programming language called Akasha. It's a language where genetic programming can be done in a few lines. The language will allow for the user to use a default function set or they can specify what function set to include in their program generation. The programs generated will be Turing complete unless otherwise specified by the user by limiting the function set. Users will be allow to specify the amount of time a program generated will be allowed to run to prevent infinite loops. Also, the language will allow for a memory limit. It will also allow for program generation by other methods such as hill-climbing or simulated annealing.

The user will be allowed to specify parts of the program he wants generated. So for example, they might know the code they want is in a for loop, but don't know the content of the for loop. They can write something like: for(int i = 0; i < 10000; i++){

}