In other countries where you drive on the left, the rule is "say left except to pass" and this works. In the US (where we drive on the right) we don't do that. Cars are in all the lanes. There IS a system though.
The far-right lane (remember we drive on the right) is the "ramp lane." People are always slowing to get off the highway, or coming on slow and speeding up.
You'll be always accelerating/decelerating there, so don't drive this one. Go left.
Trucks ("semi tractor-trailers" or "lorries") have lower speed limits than automobiles. They usually take the second-to-the-rightmost lane except to pass. If you take that lane, you're subject to the 10mph lower speeds.
This leaves a few lanes open. The third from the right is the cruising lane. You can expect more patient people following more-or-less the speed limit there.
Sometimes trucks pass each other in this lane, slowing traffic, but it is usually at the posted auto speed limit.
Left of the cruising lane is the auto passing lane. Don't go there except to pass (go around a truck passing another truck), or you'll be an obstruction to others.
If there is one more lane to the left, that's the fast lane. People there want to go well beyond the posted speed limit. At least they're not behind you, right? Stay out of their way, don't be in their (inevitable) accident.
There are cheaters.
Sometimes highway vigilantes get in the fast lane and drive slowly to stop others from speeding (more fool they).
Some maniacs pass on the right, rather than left, and often cause serious multicar accidents. This is always ill-considered: DONT.
An then there are characters: they try to take the off-ramp from the far left lane. They're stupidly aggressive, or terrified and constantly tapping their breaks, don't notice the speed limits, never signal lane changes, text while driving, drift from lanes.
Beware!
But that's pretty much the system. I hope that's helpful for foreign visitors and rural drivers coming into the cities.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Readability is a relationship between an artifact and an audience, and we all know that. It's not just the artifact, but here is a funky example.
I got a great new overdrive pedal for Christmas. It looks like this:
The weird bit is that usually the bass/treble EQ controls are together, and the volume/gain controls are together.
This time they're not and that was confusing to me.
Why such a weird order?
so, OO, right?
What people are doing with Java typically is nothing like OO.
Imagine you're creating your own language specific to your problem domain and solution domain.
That's a beginning.
A language in which you can solve your problems in your domain and stack.
It doesn't exist, btw. Java, JS, Python, C#, Smalltalk -- they're not it. They're the language you build your language in. You don't implement the solution in Java. You implement your solution in the language you've built in Java.
The problem is that you have two locations in space, a bunch of roads, and you want to route a path from one place to the other.
Don't do that in ints, strings, functions, and doubles.
Do it in places, paths, and routes.
If I'm involved in a task and it's not completed yet, then people may want to talk to me about it or ask questions.
Eventually it's done, and there is less reason for people to need my attention on that topic.
So, the more work I have in progress and incomplete, the more reasons people have to talk to me.
When I have a lot of work in flight, and I'm trying to work on something else, then all those conversations will be felt as interruptions in the work I'm doing now.
So here's what I wanted to think on today: Continuous Improvement.
It has two features to consider:
* It's about making improvements
* It's continouous
Let's take the 'continuous' bit first:
* You're not in it for a burst or for a while, you're in for good.
* Nobody has completed their continuous improvement program. Ever.
* It's not "hopping from rock to rock" - improvements sustain and accumulate.
If you "improve" by expending greater physical effort and endurance, you can't do continuous improvement. Working harder isn't an improvement at all.
You have to sustain if you're to be continuous. Lower the level of effort necessary to succeed, don't brute force it.