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

Respect and Code Reviews

Code Reviews in a development team only function best, or possible at all, when everyone approaches them with respect. That’s something I’ve usually taken for granted because I’ve had the opportunity to work with amazing developers who shine not just in their technical skills but in their interpersonal skills on a team. That isn’t always the case, so I’m going to put into words something that often exists just in assumptions.
You have to respect your code. This is first only because the nature and intent of code reviews are to safeguard the quality of your code, so even having code reviews demonstrates a baseline of respect for that code. But, maybe not everyone on the team has the same level of respect or entered a team with existing review traditions that they aren’t acquainted with.
There can be culture shock when you enter a team that’s really heavy on code reviews, but also if you enter a team or interact with a colleague who doesn’t share that level of respect for the process or…

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 operate on. The only re…

How To Care If BSD, MIT, or GPL Licenses Are Used

The two recent posts about some individuals' choice of GPL versus others' preference for BSD and MIT style licensing has caused a lot of debate and response. I've seen everything as an interesting combination of very important topics being taken far too seriously and far too personally. All involved need to take a few steps back.

For the uninitiated and as a clarifier for the initiated, we're dealing with (basically) three categories of licensing when someone releases software (and/or its code):
Closed Source. Easiest to explain, because you just get nothing.GPL. If you get the software, you get the source code, you get to change it, and anything you combine it with must be under the same terms.MIT and BSD. If you get the software, you might get the source code, you get to change it, and you have no obligations about anything else you combine it with.The situation gets stickier when we look at those combinations and the transitions between them.

Use GPL code with Closed S…