Code Readability
“Code Nazi.” That’s the phrase that was used to describe me lately. It’s pretty much on target, and I’ll explain why that’s true.
“Code Nazi.” That’s the phrase that was used to describe me lately. It’s pretty much on target, and I’ll explain why that’s true.
I’ve been looking a lot lately at getting a tool together that allows developers to easily set their projects up and encourages a good workflow without being forced into a specific paradigm. For instance, I think it’s a good idea to review before commit, but some projects only have a couple devs, and that can be painful when the other is out on vacation.
In the past, I used ssh almost solely for remote administration of a couple of boxes, which were well within my physical control (in the server room at work, the one at my desk at home, etc.). However, I’ve started using my laptop more and a number of services/tools that I want to use (Gitorious, Bazaar, Git, Launchpad, etc.) build on top of ssh. So I figured it was finally time to up my game on that front.
This has been a long time in the making.
I was sitting down last week looking at (yet another) problem where I needed to parse some data and bust it up into a tree, so that I could walk it and generate some specialized output. Generally, my need for doing this has been smallish, very specialized, and I know exactly what I want, so cranking out the code by hand is pretty painless. In this case, however, I need to parse some C, which isn’t all the friendly to parse without a compiler front-end. Which then lead me to think about ANTLR.