California Enacts a Cell Phone Law

 

California Governor Arnold Schwarzenegger has signed legislation that prohibits the use of handheld mobile phones while driving in the state.

Effective July 1, 2008, the legislation prohibits drivers from using a wireless telephone while operating a motor vehicle unless the driver uses a hands-free device. Drivers who violate the law will face a base fine of $20 for a first offense and $50 for each subsequent offense.

I can’t talk on my cell phone while I’m driving?

What a dopey law!

Can I still eat a chili dog while I’m driving? Can I drink a beverage? Can I try to find my favorite song on the CD player? Can I perform any number of activities that require the use of at least one hand and are at least as distracting as a phone call?

Has anyone else noticed that we have too many laws? And that every new one takes away one more precious freedom or one more hard-earned dollar, usually for no good reason?

A Couple of Tips on Bad Parenting

 

1. Give your son a fashionable name like Tanner, Braden or Travis. You can handicap a child for life with a goofy name. You can give him a sorry start from which he’ll never recover. By the way, you know what’s a good name? Paul. Paul is a name that’s stood the test of time. It dates back to the Bible . . .

Tanner is not even a name. Braden is not a name. Travis is a name, but it’s a hillbilly name, like Zeke. If you’re tempted to name your boy Travis, go ahead and name him Zeke.

2. Use up your moral authority on things of no importance. I was in Subway this afternoon and heard a man telling his kids, “No soda. You’ve had too much soda lately.” It turns out by soda, he meant cola, because he let the kids fill up their drinks with a mixture of Sprite and Hi-C.

First of all, cola is not bad for kids, certainly no worse than Sprite or Hi-C. I drank about four colas a day as a kid — still do, although now I occasionally pour some rum or bourbon in them, which I don’t recommend for the kiddies. As for Hi-C, I’d rather drink water from the sewer.

Second point: it’s micromanagement. Nobody, including your own child — especially your own child — wants to listen to you tell them what to do every minute. They’re going to tune you out. So by the time you finish telling them what to drink, what to eat, what to wear, and get around to something important, nobody’s listening anymore . . .

The Agile Elevator Speech

 

You begin by stating that agile is basically three things: a set of engineering best practices that allow for rapid delivery of high-quality software, a project management process that encourages frequent inspection and adaptation, and a leadership philosophy that encourages team work and accountability.

You go on to say that success in today’s economy requires us to respond quickly to changing market conditions. Agile processes allow our teams to meet the changing demands of their customers while creating environments where top developers want to work.

Gathering Requirements

 

The most common verb associated with requirements is “gather.” Yet most requirements that end up fulfilled in a system aren’t gathered. Yes, I know, there are always a few requirements that are so obvious in a new system that you can “gather” them from stakeholders, but gathering implies that the requirements are already out there, fully formed and fully understood, and ready for harvest. It just doesn’t work that way. No stakeholder ever says to an analyst, “Requirements? Why, yes, I have eleven requirements. Eight are functional, one is a usability requirement, and the other two are operational requirements. Are you collecting constraints now, as well? I have three of those. Please sit down, and I will elucidate perfectly clearly on each and every one in turn.” Most requirements are discovered–or invented. Many are transformed or compromised along the way.

Most stakeholders don’t consider the underlying requirements of their work; they do their work. They are not in the business of reinventing the work. The arrival of a new project is the point in time when the ideas for new possible ways of doing work force us to consider the underlying requirements. If you go to an experienced front-desk hotel employee and ask what requirements there are for the check-in process, you are most likely to hear in excruciating detail exactly how the check-in procedure works today. Indeed, you will probably hear more than just about check-in; you will hear about the reservation procedure and how it impacts the check-in procedure. It never crossed the mind of that employee to consider what information and material goods the hotel needs in order for a guest to do self check-in with a new automated system. And the idea of the guest selecting a room from all those available is a shock. It’s not done that way!

This is why we have folks with “analyst” in their titles. Analysis is never simply about recording requirements from clients and other stakeholders. Analysts are not waiters who take orders without comment. Analysts need to learn how to tease out the basic rules–the policies–of the system and liberate all stakeholders from thinking that the new system should be based on current procedures. It is invention that is at the heart of analysis, not gathering.

Honor Roll

 

My son made the honor roll his first semester in high school. I’m very proud of him. He’s in a competitive (translation: high percentage of Asian kids) high school and he’s taking honors classes, where every kid thinks they should get an A but there aren’t enough A’s to go around.

An email went out to parents listing the Honor Roll kids. There are a lot of kids on the Honor Roll at this school.

They should send out a list of the kids who didn’t make the Honor Roll. It wouldn’t be much longer and it would teach the kids a good lesson: Work hard or be humiliated.

Another idea: Only kids taking honors classes would be eligible for the Honor Roll. All other kids would be eligible for the “Honor” (insert finger-quotes here) Roll.

EppsNet Labs: Glider

 

Here’s a really simple gliding tabs demo using glider.js, which is downloadable here.

As you can see from the really simple code below, you could do something pretty nice with this without too much extra effort.

Glider is dependent on the Prototype and Scriptaculous libraries, both of which are included in the glider download, as is the required stylesheet.


<script src="javascripts/prototype.js"></script>
 
<script src="javascripts/effects.js"></script> 

<script src="javascripts/glider.js"></script>
<div id="glider">
<div class="controls"><a href="#tab1">Tab 1</a> |
<a href="#tab2">Tab 2</a> |
<a href="#tab3">Tab 3</a> |
<a href="#tab4">Tab 4</a></div>
<div class="scroller">
<div class="content">
<div id="tab1" class="section">Tab 1</div>
<div id="tab2" class="section">Tab 2</div>
<div id="tab3" class="section">Tab 3</div>
<div id="tab4" class="section">Tab 4</div>
</div>
</div>
</div>

<script type="text/javascript">// <!&#91;CDATA&#91;
    new Glider( 'glider', { duration:0.5 } );
// &#93;&#93;></script>

Early Shift at Starbucks

 
Starbucks cup

I walked into Starbucks at 5:30 this morning, ordered a drink . . . the Starbucks guy asked my name and wrote it on the cup, despite the fact that I was the only customer in the store.

Whether that would be considered a training success or failure depends on whether Starbucks trains its people to always ask for the customer’s name, or to use situational judgment.

I was hoping the barista would call my name when the drink was ready so I could do a comical “who, me?” take, but she just set it on the counter . . .

Once is Not Enough

 

According to a billboard I saw today, a child is diagnosed with autism every 20 minutes!

That goes to show how little I know about it. I would have thought that once would be enough.

Is he still autistic, doctor?

I’m afraid so, but I’ll check him again in 20 minutes . . .

Guarantees vs. Commitments

 

A thought exercise: “How long will it take you to get to work tomorrow? Can you guarantee it? To give us a guarantee, you’d probably put a buffer on your answer first. I guarantee a team working to put together software for the next two weeks is engaged in something a lot less well understood than a daily commute. We can put in a buffer – promise less – to give you a guarantee, or we can work from our estimates and do our best.”

Career Advice for the Deluded

 

If you don’t have something that is overwhelmingly important to do, then you probably don’t have anything that you’d absolutely rather be doing than getting up and going to work every day. So just start doing that. In any field. And stop deluding yourself that you have so many interests that you can’t choose. Really what you have is no clear interest and only a bunch of things you would consider if you had nothing to do.