Skip to main content

Big Changes A-Brewin'

I've been working up to this for quite some time now, but things have begun in motion that will cause some big changes coming my way, which will probably be reflected in the quanitity and quality of posts here. In short, there will be more of them and they'll be better, because I'll have more time and more to draw from.

I closed my first large contract, which will allow me to quit the dayjob and work full-time from home. This is fantastic timing, and freightening timing: I have a child on the way due right around the end of this project. So I'm taking something of a risk here, but things a already lined up to make sure we're secure for enough time to handle any misfortunes that come our way, and it will be fantastic to work from home instead of going away to work each day, when the baby arrives and I won't want to leave. Ever.

These changes will give me more time to focus on things going on in the communities, and comment and theorize and contribute more to everything going on. I'll probably be taking my hand at some kind of personal project, which I'm narrowing in on and will likely talk about in the near future, when I decide on some things and maybe get some funding (might need to make a call to that Rich Uncle everyone always talks about).

Wish me luck, everyone.

Comments

Steve said…
Congratulations! This must be a scary time ...

The classic mistake on a first contract is to over-promise and then piss the customer by delivering late. If you haven't made the mistake of winning work by lowering your price to what you think will just keep you alive then you're already ahead of the game.

As far as the project goes, you don't need a Rich Uncle, you need a Business Plan: it's the classic way to get funding, and signs are that banks and venture capitalists might now be sufficiently far on from the "dot-com bubble" that they will look favourably on sensible proposals (like Bram Cohen's BitTorrent, which obtained $8.75m in the last year).

Good luck!

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful...

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally! I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you don't know a lot about software development, and probably don't even know a lot about computers in general. Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year: Python needs LÖVE . LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build ...