I have it pretty much for the no limit two day shipping feature. It'd be great to have a "shipping only" version at a lower price.

Back in those days I wrote my own assembler for the C64 (and later the C128). Probably my single greatest moment of joy as a programmer was when it successfully assembled its own source code.

Basic rule of the road: if you haven't made eye contact with someone, you should assume they haven't seen you and don't know you're there.

I mean, they could improve the intersection by making it a full stop, but educating bicyclists not to ride out in front of somebody who will hit you if they don't slow down seems like a good step too.

The article describes that the cyclists don't see the car either because it is coming up on them from behind (at a 94 degree angle, with higher speed).

You can't know you haven't made eye contact if you don't know they are there.

I'm not sure if I would describe a 94 degree angle as "behind them", but I would also observe it's a good idea to exercise caution in navigating a blind intersection whether you're on a bike or in a car.

No the basic rule is ALWAYS have enough safety marginals so you can handle the unsuspected.

What you are saying is just a round about way to tell bicyclists to always yield for cars. It also has no support if you look at statistics, around here the overwheliming majority of accidents between drivers and bicylists are caused by car/bus/van/truck drivers (70%-85% depending on the situation).

In other words: the innocent victims of bad driving should just be more careful...

Your comment does bring up something interesting. These days, due to sharply sloped front windows (aerodynamic efficiency) and smoked glass rear windows (where allowed) it is almost impossible to even see a driver of an approaching car, much less make eye contact with them. A unintended consequence of what might seem to be two unrelated things.

I wondered if I would be accused of victim blaming.

I'm just suggesting better education is probably a useful avenue to improve the situation.

Of drivers? Sure! :)

Another interesting issue is that it is hard to do effective cyclist/pedestrian education in a hardcore car culture. In such an environment it is not really possible to include information about common driver errors such as right and left hooks. I remember the particuarly unhelpful things I learned in school. It came down to looking both ways before crossing the street and riding in a straight line. That is pretty wrongheaded in an environment where 80% of the collisions are caused by driver error.

In the described cases, neither of the road users has seen the other, in which case your rule does not work.

You may assume that most bicyclists do not want to get killed; of course bicyclists will slow down if they see a car on a collision course, even if they have priority; your suggestion borders on the insulting.

That is indeed the most valuable advice you can give any cyclist. You are very vulnerable and surrounded by fast traveling boxes of death. Don't assume anyone cares about you.

Perhaps OP was referring to the pre-cooked chicken available at the deli counter? That's typically a lot more expensive than buying it raw.

Here's a bookmarklet I keep handy. I call it "Sane Margins":

  javascript:var style=document.getElementsByTagName('body')[0].style;style.marginLeft=style.marginRight='1in';style.maxWidth='7in';void(0)

Ninja update: oops, reply fail :-(

If you also find little or no use for .bash_history, you can do this:

  rm ~/.bash_history
  ln -s ~/.bash_history /dev/null

(There's probably some .bashrc setting that turns off history, but I'm making it a goal in my life to know as little about bash configuration as I possibly can.)

    $ unset HISTFILE

The manpage for bash has many hidden gems

One other cool thing: if your command starts with a space, it will not be logged to bash_history. For example:

  $ echo 'this is logged'
  $  echo 'this is not logged'

> the Tucson experience of insane heat for about five months of the year.

I've got to object to this. Yeah, June and July (and to a lesser extent August) are pretty intense, but I'd hardly characterize the rest of the summer heat as "insane".

> I still a) went running most days,

I suppose this could be an issue. Especially during the summer rainy season (usually July-early September) it's still pretty hot and the humidity means it doesn't much cool off at night, which makes strenuous outdoor activity harder even if you do it at the coolest part of the day.

>I've got to object to this.

Maybe four months of insane heat: mid-May to Mid-September are ridiculous. I can't even ride a bike without sweating like a mule after a mile.

I took the Web Development course at Udacity too. It was probably more work than some were expecting (especially for a 2xx-level course), but Steve's knowledge and enthusiasm made for a great, challenging course.

Somewhat of a side-topic, but I just finished the Coursera compilers class. It didn't seem watered down to me, covering regular expression (including NFA and DFA representations), parsing theory and various top-down and bottom-up parsing algorithms, semantics checking (including a formal semantics notation), code generation (with formal operational notation), local and global optimization, register allocation and garbage collection.

I guess it was partially watered down in that the programming part of the class was optional.

Since this is already a post about language and writing:

> Point 3 peaked my interest

The homonym you want here is pique[1]

[1] http://dictionary.reference.com/browse/pique definition 3