Entries Tagged as ''

On to Linode

Way back in the far distance of the past, I was looking for a linux-based VPS  provider.  I evaluated several, and went with slicehost instead of linode, because slicehost had slightly better service, and had already moved to xen (as opposed to UML).  Several years ago, slicehost was bought by rackspace.  They swore it would stay the same, and it did.  I was happy.

Then, earlier this year, they announced that slices would be moved to the rackspace cloud, rather than the dedicated xen hosts.  I don’t particularly want a cloud hosted service, and I want to know what technology is running my hosts, and I want to support companies that support FOSS, so I’m moving on.  My slice was just closed, and my VPS is now completely migrated to linode.  Hopefully, no one noticed a thing.

That said, I have slightly better service now for the same price, so it’s a win for me.

T-Mobile #fail

We’ve been considering what we should do with AT&T buying T-Mobile.  There have been a number of options.  We could leave now, and go to Sprint.  We could wait out the deal to see if it happens, hoping it doesn’t.  If it does, we could then stay with AT&T (unlikely, due to high prices, poor quality, and poor service) or leave for Sprint.   Or, we could get on contract on T-Mobile now, and be guaranteed our plans for 2 years regardless of the outcome of the merger.

There are several complicating factors.  T-Mobile had the cheapest family plans, by quite a bit;  and Janette just got a G2 several months ago, and loves it, and wants to keep it as long as possible.  I’ve been eyeing the new G2X (destined to be the next poster-phone for cyanogenmod), but have no real reason to upgrade my phone at this point (since it’s less than 1.5 years old).

All in all, I’ve been slightly leaning towards going on contract at T-Mobile.  This would allow us to lock in the good price we’ve been getting; it would allow Janette to keep her phone for 2 years, for sure;  and, it would reward T-Mobile for the years of good service we’ve gotten.  In addition, it would allow me to upgrade my phone prematurely.  Since the G2X comes out Friday, I was holding off deciding.

All that changed today.  Today, T-Mobile announced new data plans, and the family plans are much more expensive.  $30 a month more expensive for the cheapest one, and that’s with fewer minutes that we have now.  The T-Mobile family plans are now more expensive across the board than the Sprint family plans.  The only reason left to go on contract with T-Mobile is to get a few extra months out of Janette’s phone, and for $720 extra over the life of the contract, we could easily buy 2 new phones, so that’s out too.

So, my decision is made.  I’m going to wait out the deal, keeping my current plan as long as I can, and then move to Sprint when the deal is signed and AT&T jacks my rates and removes my unlimited data.  I can no longer recommend T-Mobile, since I can’t recommend off-contract (due to the merger), and the on-contract plans are no longer compelling.

It’s unfortunate, but certainly not an accident, that these plans were announced 4 days before the release of the G2X and the Sidekick 4G, two of the more compelling phones becoming available soon.  If T-Mobile had inaugurated these plans 4 days after the release of the G2X, they may have had a happy, on-contract customer.

Who needs voice minutes?

I was reading Techdirt today, and I ran across this post.  It crystallized to me what I dislike so much about talking on the phone, especially making unscheduled calls to other people.

I know that when I get an unsolicited phone call, it’s annoying and invasive.  It context switches me away from whatever I’m doing, and you cannot politely get rid of a caller in less that 30 seconds to a minute, no matter what.  This means that I’m interrupted for at least that long.  In addition, a phone call is invasive for everyone else around you.  Your phone rings (which everyone hears), and they all instinctively check to see if it’s their phone (context switching them briefly) and then you have to answer, and they have to listen to you talk, distracting everyone.

All this means that I severely dislike making phone calls, unless the call is scheduled or is calling someone whose job it is to answer the phone.  Which means I rarely call people; which means I don’t need cell minutes.  This month, I’ve use 77 minutes, 20 of which were calling my insurance company about a claim on my car.  Last month, I used 25 minutes.   So why am I spending $50/mo. on voice for my phone?

In a world where people become less and less likely to call other people (as opposed to businesses), do large, pre-paid voice plans make sense?  If not, how badly are we going to be gouged on our data plans in the future, when the phone companies can’t charge us huge amounts for unused voice minutes?

Readers Against DRM

Readers Against DRM

Bare git-svn repo I can commit from?

Dear lazyweb.

I’ve asked google, and I’m not sure I can do what I want to do, but maybe one of you knows how.

At work, we use subversion (ick) as our VCS.  I, of course, use git-svn.  However, this means that I have to have a multiple git-svn repos if I want to have multiple outstanding change-sets (uncommitted to local git) at a time.  I know, I’m supposed to commit early and often and rebase (and I do) but sometimes it’s horribly inconvenient to have to stop what I’m doing, commit, check out a new branch, make a small change, commit, and switch back.  In addition, I sometimes need stable checkouts for testing (some bugs can take days to reproduce, and rebuilding breaks debugging).   However, keeping track of all these git-svn repos is a pain, and getting new ones is very time-consuming, involving either a new ‘git svn clone’ or a copy of an existing repo.

What I’d like is a git to svn bridge.  That is, a bare git-svn repo with appropriate hooks that I can clone (using git), work from, pull from (the pull hook would git svn fetch), and push to (the push hook would git svn dcommit).  As nearly as I can tell, I can’t do this, because git-svn seems to need a checkout for some things (git svn rebase, for example; git svn fetch didn’t seem to pull the changes into the repo’s history), but cloning and pushing in git seems to need a bare repo.

So, oh lazy web, is it possible to do what I want?

So much for the Google Bookstore

I had high hopes for the Google bookstore.  It seemed so promising, even supporting my Sony Reader.  So I went and dropped $10 on an ebook, only to discover I couldn’t download an epub (or pdf) version of it.  WTF?  They said I should have previewed it before I bought it (I did), but I went looking and there no way to tell if a book can be downloaded! I don’t want to read the book on my computer, I have it in a paper version already!  I want it on my bloody Sony Reader!  Google: You lied to me, and now I have to jump through hoops to get my money back.

<sigh>  So much for the Google Bookstore.

Please don’t avoid being informed.

Seth says it better than I could have.   But I’ve been thinking basically this for a while.  Please: take at least some of your valuable TV watching time, and become better informed.

Pot rack and poker

I’m taking a beginning blacksmithing class at the Toledo Art Museum right now.  It’s a huge amount of fun.  There’s something enormously satisfying about banging on hot iron with a hammer, and shaping it into useful and beautiful (I hope) things.  Steel is usually such an unyielding material; so durable, so touch, so hard to modify.  But a little (okay, a lot) heat, and it becomes a joy to work with.

Anyway, on to what I’ve made.  Of course, the first thing we made, the blacksmithing equivalent of Hello World, is a fireplace poker:

From Ironwork

The point (ha!) of the poker is to learn to draw out a point, to flatten an end, to shape a loop, to flatten and twist.  Lots of basic hammer techniques, that are useful for most projects, and all of them that actually involve a hammer and anvil.

The poker was an assigned project.  The teacher provided the steel, and walked us through the whole thing.  The idea was, presumably, to give us something to do, to give us an idea of what’s possible, to ease our entry into the world of blacksmithing.  After the poker, however, we were more or less on our own.  We were supposed to come up with a project to do, buy the steel for it, design it, and make it.  The teacher would help us, of course, with all of the parts, but it’s ultimately up to us, and our interests.

I decided to make a pot rack for my kitchen, to replace the board-with-hooks I was using right now.  I wanted to do something other weld a hook, so I decided to twist two 1/8″ rods together, and bend them into hooks, and weld that to a 3/16″ x 1″ steel plate.

From Ironwork

This was a fun and useful intro project for me.  It only took me 1.5 sessions (and would have taken less than one, if the teacher had had time to show me the techniques I needed; but hey, there’s 8 other students…).   It resulted in something that is useful to me, and I think it came out quite good looking.  Plus, it allowed me to learn several new techniques, and practice my hot hammering.

First, I had to learn to twist the rods.  The basic idea is that you clamp the rods together with vise grips, heat the rods, clamp the other end in a vise, and twist by hand.  The variation here is in how you heat the rods.  The first set, I heated with an oxy-acetylene torch while it was already in the vise.  That’s fairly quick, but is expensive (not for me, of course, but for the shop), and requires either help or lots of coordination.  The second technique is to head the rods in the forge, then carry them over and clamp them in the vise and twist.  This is much more time consuming, since multiple heatings are necessary, but can be done easily by yourself.  I used both techniques; I admit, because the torch scares me a little.

Once the rods were twisted, I hot hammered them into hooks, and cut them with the saw.  Then, I got to try something else new: welding.  In this case, MIG welding.  This turns out to be surprisingly easy, and lots of fun.  After a brief tutorial, I welded the hooks onto the back plate.

From Ironwork

That’s it.  Several holes drilled with my drill press, and it’s done.

Quantum Bug

quantum bug: (noun)

A bug in your code that is in a superposition of triggering and not triggering.  Examining the state of said bug (via code inspection, accidental triggering, whatever) causes it to collapse into one of the two states permanently.  All future tests exercising the bug will hit either pass or fail, depending on the collapsed state.

Note: It may seem that all quantum bugs collapse to triggering, since they are only noticeable if they trigger.  In fact, the wave function for the code determines the probability of collapsing to triggering or not.

See also: heisenbug.

PI Units

We should totally adopt PI units.  Finally a unit of measure that actually makes sense