Skip to main content

My New Laptop

Celebrating both my new bussiness and my birthday, my wife and I purchased a new laptop. I'm in hyper-joy over my new geek toy and I'm still settling into it. I've decided, for various reasons, to leave XP installed on this one. I haven't used Windows, for anything besides checking my e-mail, in nearly four years now. I remember most of what I need to know to keep things running, but it will be an expirience to get back into things. I've had some trouble getting my NFS shared visible to the laptop, and decided to just migrate to Samba instead. I was disappointed to find out about DVD decoding being a little off with Windows, I suspect for anti-trust purposes, so I might have to pay ten bucks for a decoder. Overall, I am very happy with my new laptop. DVD burner, S-Video input, large screen, faster than my desktop. I was walking around the house carrying the laptop to test the WiFi strength, and its pretty good.

I've finally got Samba running, and learned how to get those shares accessable by all the users on the laptop by setting up a batch script to configure the drive mappings triggered by all user logins, even though I'm the only user. I've exposed my subversion repositories so I can collaborate with myself, and I've installed all the usual tools I'll need for Python work. I might still be missing some dependancies, but I'll work those out as I find them. I'm surprised that I'm actually missing linux packaging, because as much as I complain about it, at least it usually has automatic dependancy installation handled pretty well. I've had to search for some missing python packages already with no errors indicating them at all (pythonw hides all errors onto the console, so be careful for that).

Yay.

Comments

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…