I recently read Information Doesn’t Want to be Free, by Cory Doctorow. It contained a lot of points and themes for such a slender volume, but I found it enjoyable overall. It can be thought of as a collection of short essays organized by their thematic relation to each of “Doctorow’s Three Laws.”
An Ideological Basis
I like Bitcoin a lot, but I kinda see it as the latest development in our ongoing conversation about what currency should be rather than as the final word in it. One of the problems I see with Bitcoin, aside from the mining centralization problem, is the wealth centralization problem. In particular, capitalism tends toward the accumulation of most of the world’s wealth in the hands of a few.
Written in response to /u/robboywonder’s comment on /r/bitcoin expressing a wish for peer-to-peer social media. Reproduced here because it very nicely expresses my feelings on this subject at the moment. Please express your agreement or disagreement in the comments! I’d love to have a real debate over these notions bouncing around in my head.
There have been a lot of attempts at federated social media solutions. I think that approach is played out. As soon as I finish the paid work I’m currently doing, maybe even before then, I plan on beginning work on a true peer-to-peer social network. I’ve been reading and researching the subject for a few months now and feel I’ve just about got a good enough grip on things to take a decent swing at it.
The technology, as it turns out, isn’t all that complicated. Monetizing these endeavors is really the hard part.
I do frontend AngularJS work for a client in Portland. One of the things I really like about their setup is its test-friendliness. They use Grunt to watch the client-side files and run tests and re-compile everything automatically when a change is detected. Everything gets wiped from the “build” directory when the process starts, and a failing test or JSLint warning blocks the whole process. This renders the developer’s copy of the web app inaccessible until the issue is addressed. I’ve found I enjoy this particular workflow as I’m immediately made aware of when I write something that breaks the tests. It keeps me from building on top of broken foundations.
This weekend I decided I wanted to sharpen my C skills by writing a simple CLI utility to convert strings of hexadecimal to memorable phrases and back again. Since my intended use case was encoding and recovering 256-bit private keys, I wanted to take extra care to ensure correctness of output. So I set out with the intention of writing both unit and user acceptance tests using a TDD flow similar to the one I use in my AngularJS work.
This post is meant to be a helpful reference for developers who are either just beginning OpenERP development or who are considering beginning OpenERP development. It’s also a fairly thorough catalog of my gripes with it. Hopefully this will help save someone somewhere some pain. I start with a summarized list of its pros and cons, followed by a more thorough explanation of each of the cons, and finish up with a list of tips that I personally would have found useful back when I was getting started.
For those of you near Portland interested in seeing me speak in person, I’ll be giving my “HTML Reloaded” presentation at Devsigner this weekend. Devsigner conference is for “the coders who paint and the designers who send pull requests.” It’s a rather timely endeavor, in my opinion, as I’ve recently noticed increasing crossover between the graphic design and developer worlds. The advent of CSS compilers like Sass and Less, and of frontend frameworks like AngularJS, seem to be both a result and a cause of this. I’m looking forward to seeing what other people have to say about this emerging cross-disciplinary field.
I have added a “Slides” page to hold all the slides I use in my public speaking engagements. All my slides are available under the GNU Free Documentation License. If you are interested in engaging me as a public speaker, particularly if you want me to present on one of the slide decks I’ve already posted, please send me a tweet.
To send bitcoin from my mobile phone to a plaintext address on my laptop, I like to use QR codes. At first I used websites like qrstuff.com to generate the QR codes, but leaving the command line just to generate and display an image felt like too much of a hassle to me. Then I started using the
qrencode utilities in Ubuntu’s package repositories, but that involved creating an image file on my hard drive and then deleting it afterward, which felt messy. So I found a quick and easy way to generate and display a QR code from the command line without creating an intermediate file.
Since my last post, I’ve decided that I really ought to do as much as possible with other people’s code. It seems to me that “Don’t Repeat Other People” ought to be considered almost as important as “Don’t Repeat Yourself.”
The fact is that WordPress has been a quite serviceable platform for me so far, and I don’t really want to expend a bunch of effort writing a whole new blogging platform. I don’t have much reason for doing so, to be honest, and I will probably be of more use to more people if I build my new platform using other people’s components as much as possible
I’m planning on overhauling this website and moving to a custom platform. Fortune.js would be perfect for the kind of minimalism I’m looking for at the moment, but we’ll see what I settle on. I find the Indie Web very intriguing at the moment.