Every article I've ever read about technical debt always talks about how technical debt was a deliberate choice to get a product out the door quicker. In over fifteen years of professional development I've never, ever, seen that choice being taken on purpose. I have seen absolute horror shows of a code base brought on by:

1. developers of questionable experience
2. developers of questionable skill
3. developers of questionable passion
4. developers of questionable taste

Don't get me wrong, I've written stuff and been happy and proud of it but then six months later when I know more and understand the problem better I'm, to say the least, no longer proud of said code.

My point is, lets get off our high horse and stop pretending that shitty code was a choice called technical debt and own up to the fact that once upon a time the royal we wrote some crap and it's time to fix it.

A random neuron fired in my brain and I was curious as to which grew faster, Fibonacci or n^2. While I was at it I also plotted 2^n.

more…

Here's how you can get Dropbox to run as a user service from systemd under Feodra. If you use a different distro that uses systemd the commands are probably the same but your mileage may vary.

For the most part I like systemd but good luck remembering all these commands in 6 months when you want to make another user service.

more…

NameChanger is a quick and easy way to bulk rename files on OSX. But it took a bit of trial and error for me to figure out how to use back references when I wanted to use a regular expression. This brand of regex syntax uses $.

Quick howto:

1. select and drag some files into the left pane
2. eg file: 301 - some.show.name.avi -> Some.Show.s3e01.avi
3. left box: ^(\d)(\d\d).*, middle box: regular expression, right box: Some.Show.s$1e$2.avi
4. click the rename button

I recently needed to have a pool of objects and it would make everyones life a lot easier if those objects would automatically return themselves to the pool when they were done.

Here's my take on a shared pointer pool.

more…

This is a quick and dirty config guide to setup git-http-backend with uwsgi from supervisord on nginx. I did this on Fedora 20 so on a different distro some paths will likely be different.

I've also ignored security in this post as I have ssl termination handled elsewhere. This will send your password in the clear if you don't have ssl setup correctly! Don't forget to setup git permissions as well. This config allows any authorized user (somebody who can login) to push.

more…

OMG I HATE MY LIFE SOMETIMES

So… I'll hopefully write more about this later, but the TL;DR is do not use monitor.py and uwsgi.

So if you have something like this in your wsgi.py, comment it out with extreme prejudice.

import monitor
monitor.start(interval=60)

Symptoms include, but not limited to:

• workers not shutting down
• workers appear to hang and cause 50x errors
• workers not restarting if you send appropriate signals
• workers appear to work once or twice then hang
• workers never work
• randomness and non-determinism all over the f'in place
• little to no helpful log output
• propensity to start adding lots of config variables that you don't understand
• propensity to start drinking
• wondering htf everybody else seems to use this software without a problem
• wondering if perhaps computers where a poor career choice after all

I haven't looked into too closely but I suspect the fact that the monitor opens up it's own thread and runs forever has something to do with it. Open files, open sockets, stuff like that.

In your muttrc you should have something like the following:

set query_command = "goobook query '%s'"
bind editor <tab> complete
bind editor ^T    complete-query

and if auto-completion of aliases isn't working make sure you don't have:

bind editor <tab> complete-query
bind editor ^T    complete

Note that the complete-query vs complete. Ctrl-T runs your query_command whereas tab auto-completes as appropriate (likely from your alias list).

That took too long to figure out…

For funsies I ported my mazesolver to pypy.

See update 2 for reference.

more…

This pattern which I thought up (but is likely not unique) can very nicely manage your service configurations, automatically reload/restart your service, and even give non-root users (if desired) the ability to modify system config files.

All through the magic of git hooks. This example tracks config files for Apache (httpd).

more…