Sunday, July 16, 2017

Modern fire management

We are now well into the 2017 fire season here in California, and there have definitely been a few scary fires already.

Meanwhile, in a completely different part of California, I'm keeping a watchful eye on the "Island Fire", which for now is being quite well-behaved:

The Island Fire is burning deep in the Marble Mountain Wilderness on the Klamath National Forest. It was ignited by lightning on Sunday June 25 and first reported on the afternoon of June 26. The fire is being suppressed under an alternative suppression approach to clean up hazardous fuels from a area that hasn't burned in a long time. There is no recorded large fire history for this portion of the Wilderness, although it is surrounded on the north, west and south by recent large fires.

Those "recent large fires" were horrific; it's amazing how soon those memories fade.

Gov. Jerry Brown declared a state of emergency for all of California in the wake of wildfires that killed one firefighter and drove hundreds of people from their homes.

California's record drought, now in its fourth year, has "turned much of the state into a tinderbox," he said.

The emergency declaration, which included the activation of the California National Guard, will speed up help for thousands of firefighters, Brown said Friday.

About 9,000 firefighters were battling 24 large wildfires in California on Saturday, Ken Pimlott, the chief of the California Department of Forestry and Fire said in an interview.

Dry thunderstorms were expected to threaten much of Northern California through much of the the weekend, Pimlott said. Thunder storms with gusty winds and lightning strikes have ignited fires, hitting Trinity and Humboldt counties the hardest, he said.

The smoke traveled hundreds of miles; it was an inferno of heat ablaze.

Wondrous rain has changed things, and now it's hard to remember what things were like, just two years ago.

This year, we shall let (certain) fires burn, for "there is no recorded large fire history for this portion of the Wilderness".

But I'm still watching; I'm keeping my eyes open.

Saturday, July 15, 2017

Up, up, and away

They've taken the construction cranes and elevators down from the Salesforce Tower, as construction is nearly complete.

Of course, those cranes go somewhere; they don't just disappear.

It turns out there's a company which pays a lot of attention to this, and issues periodic reports about where all the cranes are.

In the whole world!

Anyway, if you wanted to know, The Seattle Times digests the report for you: Seattle is again crane capital of America, but lead is shrinking

Seattle has again been named the crane capital of America, as the local construction boom shows little sign of slowing in 2017.

Seattle had 62 cranes dotting the skyline at the end of 2016, the most in the country, according to Rider Levett Bucknall, a firm that tracks cranes across the world. That’s up from 58 in the middle of last year.

The company releases tower crane counts twice a year. In the last update, Seattle had an 18-crane lead over second-place Los Angeles.

But this time, a surge in construction in Chicago has catapulted the Midwest city into second, with 56 cranes, just six shy of Seattle. Los Angeles has dropped to third on the list with 29.

So now you know: Seattle really is where it's happening.

If you're a construction crane.

If you're that other sort of crane, Bosque del Apache, New Mexico is where it's happening.

Thursday, July 13, 2017

Let's hear it for the old guys

It's an interesting, if tangential perhaps, aspect of American Jazz music that it is an art form that appears to particularly allow for an extremely extended career.

The list of Jazz musicians who did some of their very best work at advanced ages is a long list, and it's not hard to think of examples of Jazz musicians who have been very productive in their 80's and even in their 90's.

And lovers of Jazz are well aware of this, and there is a tremendous culture of respect for your elders in Jazz, which is quite interesting and refreshing given the attitudes that some other crafts seem to show to their craftspeople.

We had a nice reminder of this recently, when we got to hear Greg Adams and East Bay Soul.

Adams, who was a founding member of the pioneering West Coast Jazz group Tower of Power, has been performing for five decades; as his bio attests, he has appeared on an astonishing six hundred records.

And, he's still composing, and recording, and performing, with a great band containing a number of other Tower of Power veterans, including Lee Thornburg and Nick Milo.

I'm no spring chicken myself, so I'm pleased to see any evidence that the old guys can be just as productive and creative and influential and imaginative as they were when they were younger.

Thank you Greg and East Bay Soul, for such a stirring example.

Tuesday, July 11, 2017

That sinking feeling

I'm not really sure what to make of this: Millennium Odor Problem Could Point to Fire Risk, Experts Say

Unexplained odors inside the Millennium Tower units could be evidence of a potential fire safety risk to the 58-story sinking and tilting structure, experts tell NBC Bay Area's Investigative Unit.


Pretlow and several other residents report having long endured unexplained odors permeating their luxury units. Then, late last year, the building’s homeowner association commissioned consultants Allana, Buick and Bers to investigate Pretlow’s unit.

When the experts cut open several of her walls and set off smoke bombs from the unit below, they learned that smoke was getting in through gaps surrounding pipes and ducts running through holes in the concrete floors behind Pretlow’s walls.

It's a reputable publication, and the story does in some ways seem plausible.

On the other hand, the article also fills me with a certain amount of unease; it makes me feel as though the various parties to the various lawsuits are trying to have their conflicts aired in the media, rather than being settled by figuring out what is wrong with the building and how it can be repaired.

Meanwhile, I can't deny that I'm intrigued by the notion of diagnosing construction failures via odors.

In computer science, there is a reasonably-non-crackpot technique that goes by the awkward name of Code Smells.

It's an approach for developing an almost-instinctive feeling about where problems might lie in a code base, based on unpleasant attributes of the code which you can train yourself to recognize when you're reading the code.

It probably would be more accurately named "code disfigurements," but that doesn't have anywhere near the ring of Code Smells.

Maybe there is a textbook somewhere of Construction Smells.

Saturday, July 8, 2017

Naming rights and plaza arrangements

The cranes and exterior elevators have come down from the tower, and the trees are arriving; the long-awaited Transbay Transit Center is nearly ready!

Only, it's not actually going to be called the Transbay Transit Center.

Salesforce buys naming rights to Transbay Transit Center

Salesforce, a software company with its headquarters and 6,600 employees in the Bay Area, has agreed to a 25-year, $110 million sponsorship of the 2½-block-long facility set to open next spring at Fremont and Mission streets. The deal includes naming rights, which means that the complex would be known as the Salesforce Transit Center.

Similarly, the 5.4-acre rooftop open space will become Salesforce Park if the board of the Transbay Joint Powers Authority approves the contract Thursday at its monthly meeting.

The cloud-like Salesforce logo that adorns two towers near the transit center would not appear on the exterior of the new facility, however. Nor would Salesforce have veto authority on events held in the park, even those of rival corporations.

Mostly, I'm excited about the park, which (I hope) will be a delightful new space, to rival such world-renowed places as the High Line, or the Greenway ("a long lawn on top of a sewer").

Meanwhile, down at ground level, change is afoot there, too: Salesforce Tower redesign trims trees, sculpture out of plaza

As Salesforce Tower nears completion, the plaza that will accompany it has been shorn of two eye-catching features: a grove of redwood trees and a 40-foot-tall sculpture made from chunks of recycled concrete.

Instead, the half-acre space at Mission and Fremont streets will be handsomely paved but almost entirely open — a change instigated by Salesforce but agreed to by public officials. They welcome the idea of an uncluttered path to the new Transbay Transit Center, which should open next spring on the plaza’s south edge.

“In retrospect, 20 redwood trees are probably not the best thing to have” between Mission Street and what will be the transit center’s main entrance, said John Rahaim, San Francisco’s planning director. “This leaves a clear passage and sight lines at both ends.”

I'm trying to get my head around the gondola: what the heck?

But surely, this is progress. There was no way that 20 redwood trees were going to be feasible in that small space at the base of the tower. Open space, even though it's largely concrete open space atop a 5-level underground garage, is still open space.

Really, it's still very hard to imagine what it's all going to be like, but it has, I think, the potential to be tremendous. Yes, it's a lot of steel and glass and high-rises and urban canyons, but I'm keeping my fingers crossed. Being out and around on these streets during the day, the energy and activity is undeniable; hopefully that energy translates into a truly vibrant new downtown core.

The Girl on the Train: a very short review

As part of my summertime reading binge, I joined the millions who have enjoyed Paula Hawkins's The Girl on the Train.

Hawkins certainly knows how to craft a page-turner, and it's no surprise that her story was not only a runaway bestseller, but also became a successful movie. Entertainment, this is.

But our heroine is a severely mentally ill woman, self-destructive, with an extreme alcohol abuse problem.

And things go downhill from there: other major characters include inept and uncaring local police, a corrupt mental health professional, a lecherous and abusive colleague, etc.

It's a hard thing to finish a 400 page book without finding a single sympathetic character. I wanted the worst for all of them; I simply wanted the book to be over so I could move on.

But, I couldn't put it down.

If you like your entertainment gritty and fast-paced, this is it.

But it sure ain't a very pleasant time on the roller-coaster.

Thursday, July 6, 2017

Alphabet is for Antitrust?

There's a certain amount of attention being paid to Alphabet right now, such as the huge EU outcome, and all the attention that Yelp have brought to the discussion.

And, a lot of that is, I think, quite justified.

Meanwhile, I must admit that I lost about 3 hours the other day to a bit of Alphabet frustration of a different sort.

Google Docs, when it works (and it usually does work quite well), is an amazing piece of software. Collaborative document editing in the cloud! What's not to love?

But there I was, just beating my head into a bloody pulp.

I was trying to combine 3 semi-related presentations into a single new presentation.

I started the new presentation, and wrote some introductory slides.

Then I began grabbing content from the other presentations.

I opened up several browser tabs, and picked a slide from this presentation, and copied-and-pasted it into my new presentation.

Lather, rinse, repeat.

Simple, right?

Unfortunately, it wasn't working.

Normally, whenever you change a Google Docs document, it automatically initiates a background save. The message "Saving..." appears, followed after 30 seconds or so by the message "All changes saved in Google Drive."

But, not this time.

After I would paste in a slide, "Saving..." would display, and display, and display.

Until, after about 2 minutes, some completely bizarre error message would show up, and Google Docs would simply throw away all the changes I'd made to my presentation since the first "paste" action.

Sometimes the message would be something about permissions.

Sometimes it would be more generic, and would say "Google has encountered an unexpected error saving your document".

I refreshed tabs, logged back out and back in, over and over.

Made that single great presentation multiple times, only to have Google throw it away on the floor.

Searching for similar problems brought nothing.

But then, while stomping around near my desk, complaining bitterly to the air, it occurred to me: I was using Mozilla Firefox.

I went back to my computer, brought up Google Chrome, and re-performed the exact same sequence of operations.


Which is a shame, because Mozilla Firefox is really the platinum standard of browsers nowadays, and it's rare that it lets me down.

Now, in all fairness, Google Docs is an extraordinarily complex piece of software, implemented as a MASSIVE amount of Javascript, running in the browser. And Javascript is notoriously non-standardized, with many disparate and varying implementations, not the least of which is Google's own proprietary V8 engine.

So it makes a lot of sense that my problem was due to a client-side Javascript portability problem, and switching browsers fixed it.

That is, what should make me think that running Google's tools should work on any browser other than Google's own browser?

Silly me.

But, I am (becoming) an old man.

And, I'm old enough to remember when a dominant computing company had their own suite of office software which worked best (or, in some cases, only worked at all) with their own internet browser.

And, I'm also old enough to remember what happened next.

Sometimes it seems like we go though the same motions, over and over.

For the time being, I unfortunately have work that I have to get done.

So, I'm sorry, Mozilla, but I'll be using Chrome for the next few days, at least until I finish this particular project.

Saturday, July 1, 2017

Corporate goddesses

I've developed a habit of taking long walks around downtown San Francisco at lunchtime. I don't have a particular set route; often I just let my feet take me where they will.

There's always a lot to see when walking around downtown San Francisco. I haven't yet had the opportunity to see flying cars, but I suspect that's not long away.

Often, when I'm walking along, I find I'm mostly looking down at the street or around me at the various shop windows and displays, or out at the vistas over the Bay.

But, sometimes, I happen to look up, as I did the other day while walking back from North Beach.

I had no idea what I was looking at, but later I remembered to track it down, and it turned out that I had seen the famous corporate goddesses of 580 California.

If you have ever wondered about the sculptures on top of this building, the sculptures were created by Muriel Castanis, an American sculptor best known for her public art installments involving fluidly draped figures. Muriel described the 12 statue on top of this building as Corporate Goddesses. In 1983, Philip Johnson commissioned her to create sculpture for the top story of 580 California. Three different heroic-size figures are repeated on each side of the building.

It's hard to describe just how peculiar these statues are, but one wonderful essay about them is JW Ocker's Grim Roofers: Muriel Castanis’s Corporate Goddesses:

There are three individual wraiths, each one 12 feet tall, and the pattern of three is repeated on each side of the building for a total of twelve wraiths. One lifts an arm like she’s a Fate and her sash is a life-string to be cut. The second has her arms thrown back like she’s about to jump into oblivion. The third is holding her sash in front of her like one of those airport car drivers looking for his passenger. That’s the most terrifying one if you think about it.

The artist who created them was Muriel Castanis, who made a career out of empty robed figures before dying in 2006. She designed them by covering models in epoxy-soaked cloths. The models then wriggled out as the clothes hardened, and Castanis used those forms as a basis for the 12-foot-tall skyscraper specters San Francisco has today.

For some more pictures, including a few which give a better feel for what it's like to see these sculptures from ground level, try this short photo-essay on SFGate.

Apparently the phrase "Corporate Goddesses" may have come from Castanis herself, at least according to this old article on SFGate:

Price is gazing out over the city as an eerie sight emerges across the way, on the rooftop of 580 California. Ghostly, faceless figures surround the building's crown, spooky women in hooded white robes. From street level, the 12-foot-tall statues are all but unseen.

They're the creation of New York artist Muriel Castanis, who was specially commissioned to create the figures for the 23-story building. She has described her work as "corporate goddesses."

"The view is best from here," Price says, gazing down on the statues. "They used to put Santa Claus hats on them at Christmastime. They don't do it anymore."

I think it's just fine to leave the Santa Claus hats off; still, the statues do apparently need some attention from time to time. A few years back, a specialty art restoration company gave the statues a much-needed freshening up:

The figure was cleaned with detergents, biocides, and denatured alcohol to remove dirt, debris, and biological growth. Deteriorated paint was removed and cracks, losses, and impact sites were repaired with Paraloid B-72 and glass fiber bulked resins. Caulk was removed from the base of the figure and pedestal. Corrosion was removed from the aluminum-clad pedestal, and the metal prepared for repainting. Embedded iron was removed from the leg of a second figure, and the material replaced with fiberglass patching material. All of the treated materials were repainted with a color-matched, industrial paint system.

I hadn't heard of Castanis before, but I have to say, I find the sculptures pretty nice, overall. I have no idea what they mean, but I think it's nice that the building included this artwork, even if it's rather unusual.

Who knows, maybe one day I'll make it up to the rooftop garden at 343 Sansome and see how the Goddesses look from that perspective.

But one thing's for sure: as I walk around the streets of the city, I'll remind myself to make more frequent glances skyward.

Tuesday, June 27, 2017

Aviatrix: a very short review

My daughter returned from a writer's convention having met Mary Bush Shipko, and having bought her book: AVIATRIX: First Woman Pilot for Hughes Airwest, as a gift for me.

I classify Aviatrix as a memoir, by which I mean it broadly follows this recipe:

  • The author tells various stories, of the author's choosing, and in his or her own words, about events that seemed particularly important in the author's life
  • The author explains a bit about why he or she chose these stories, and what sort of lessons you might learn from considering the author's experiences
  • The author hopes you will enjoy learning about "what it was like," which is a valuable goal, as things change so quickly nowadays.

Aviatrix certainly covers a lot of this ground.

The early years of aviation in America, starting soon after World War II ended, and developing rapidly through the 1950's and 1960's, were a very interesting time in the development of the country, and it's hard not to find this history compelling.

Shipko had a fascinating early adulthood, living in southern Florida, learning to be a pilot at a young age, flying all sorts of fascinating trips around Florida and the Caribbean. Some of these stories were delightful, such as making cargo runs to the Bahamas to pick up crates of cucumber and zucchini, or having to make a very careful landing at the airport on the Abacos Islands because there was a building on fire at the far end of the runway.

But the later part of the book, while still telling the story of Shipko's aviation history, takes a dramatic turn.

Once she mastered the cargo planes and short-hop delivery routes of south Florida, she moved on to become a jet pilot and was, as she notes, the First Woman Pilot for Hughes Airwest, a remarkable achievement.

Sadly, though, the toll it took on her was immense. Plagued by bitter co-workers and a severely polarized and caustic work environment, she endured nearly a decade of hostility and harassment until she eventually was forced out of her chosen career, simply because she was "a woman doing a man's job."

The second half of the book is not easy to read. Some of the anger she faced was searing, and it clearly still burns, 40 years later.

None of this will be much of a surprise to anyone who paid even the slightest bit of attention to events such as the Tailhook Scandal, and it won't be much of a spoiler to reveal that things still haven't much changed.

I admire Shipko for speaking up, for writing her book, for telling her story. Although it certainly doesn't qualify as "light summer reading," it was undeniably fascinating.

Silicon Valley title sequence

Here's a very nice detailed breakdown of all the inside-the-Valley references, barbs, cultural references, and other easy-to-miss aspects of the title sequence of HBO's Silicon Valley TV series.

Monday, June 26, 2017

Those were the days ...

A dear colleague of mine tracked down this wonderful picture of me with one of my favorite engineering teams:

How wonderful it was to have such brilliant co-workers to learn from!

If, in some magical way, 56-year-old Bryan could go back 23 years and talk to 33-year-old Bryan, what would I say?

Maybe something like:

Pay attention, keep listening, and work hard: you've still got a LOT left to learn.

Of course, that's just as true now.

Hmmm, maybe I just got some words of wisdom from 79-year-old Bryan, far off in the future?

As for the picture, as I recall, we were looking for a theme for a team picture, and Nat and Brian both happened to be wearing their leather coats that day, and so somebody (Rich? Ken?) suggested we all get our coats and sunglasses and "look tough". So we did...

Tuesday, June 20, 2017

All Over the Place: a very short review

Is it possible that I am the first person to tell you about Geraldine DeRuiter's new book: All Over the Place: Adventures in Travel, True Love, and Petty Theft?

If I am, then yay!

For this is a simply wonderful book, and I hope everybody finds out about it.

As anyone who has read the book (or has read her blog) knows, DeRuiter can be just screamingly funny. More than once I found myself causing a distraction on the bus, as my fellow riders wondered what was causing me to laugh out loud. Many books are described as "laugh out loud funny," but DeRuiter's book truly is.

Much better, though, are the parts of her book that aren't the funny parts, for it is here where her writing skills truly shine.

DeRuiter is sensitive, perceptive, honest, and caring. Best of all, however, is that she is able to write about affairs of the heart in a way that is warm and generous, never cloying or cringe-worthy.

So yes: you'll laugh, you'll cry, you'll look at the world with fresh new eyes. What more could you want from a book?

All Over the Place is all of that.

Monday, June 19, 2017

Ghost Ship report released

The Oakland Fire Department has released their official report on last December's Ghost Ship Fire: Origin and Cause Report: Incident # 2016-085231.

The report is long, detailed, thorough, and terribly, terribly sad.

It is vividly illustrated with many pictures, which are simultaneously fascinating and heart-breaking.

In the end, the report accepts the limits of what is known:

No witnesses to the incipient stage of the fire were located. Based on witness statements and analysis of fire patterns, an area of origin was identified in the northwest area of the ground floor of the warehouse. In support of this hypothesis, fire patterns and fire behavior were considered, including ventilation effects of door openings, and the fuel load, consisting of large amounts of non-traditional building materials. This analysis was challenged with alternate hypotheses of fire origins, away from, or communicating to an area remote from, the immediate area of fire origin. Several potential ignition sources were considered. No conclusive determination of the initial heat source or the first materials ignited was made. The fire classification is UNDETERMINED.

In their Pulitzer Prize-winning coverage of the fire, At least nine dead, many missing in Oakland warehouse fire ,the East Bay Times highlighted the eccentricities of the collective's building, details which are thoroughly corroborated by the OFD's detailed report.

Alemany had advertised on Facebook and Craigslist looking for renters seeking "immediate change and loving revolution," who enjoyed "poetics, dramatics, film, tantric kitten juggling and nude traffic directing." He described it as 10,000 square feet of vintage redwood and antique steel "styled beyond compare."

His 1951 purple Plymouth remained parked Saturday in front of the building that burned so hot, the “Ghost Ship” letters painted across the front had all but melted away.

"They are ex-Burning Man people and had their kids in the place -- three kids running around with no shoes," said DeL Lee, 34, who lived there for three months two years ago. "It was nuts."

He described the place as a filthy firetrap, with frequent power outages, overloaded outlets, sparks and the smell of burning wire. A camping stove with butane tanks served as the kitchen, and a hole had been chiseled through the concrete wall to access the bathroom at the adjoining automotive repair shop next door.

The staircase, which had two switchbacks to get to the second floor, was built of pallets, plywood and footholds -- like a ship’s gangplank -- and was like "climbing a fort" to get up and down, say people who had visited the building.

Pianos and old couches doubled as room dividers. Pallets covered with shingles and elaborate trim formed sculptural walls. Often, Lee said, the place was filled with the sounds of sawing and hammering as Alemany continued to build.

And the OFD report confirms that chaos:

The front staircase was located along the east wall at the front of the structure. It was constructed of various wooden planks and wooden studs, as well as portions of wooden pallets at its top where it accessed the second floor. One of two bathrooms was elevated slightly off ground level where the lower staircase landing was located. The orientation of the staircase was such that it first led eastward where it bordered the east wall, then turned north (rearward), where it then turned slightly west at the very top of the staircase at the second floor.

As the Mercury News observes, releasing the report is a milestone but it's not the last we'll hear of this; the next steps will involve the courts:

Almena and the collective’s creative director, Max Harris, are charged with 36 counts of involuntary manslaughter in Alameda County Superior Court. Prosecutors charge the men knowingly created a fire trap and invited the public inside. Lawyers for the two men say their clients are being used as scapegoats and say the building owner Chor Ng should be facing criminal charges.

Ng, Almena, PG&E, are named in a wrongful death lawsuit that is in its early stages. The City of Oakland is expected to be named in the suit as soon as this week.

“Of course, we’d like to have them say what the cause of the fire is but we also have our experts and they are not done with their analysis. I don’t think it’s the end of the story,” said Mary Alexander, the lead attorney for the victim’s families.

Meanwhile, as Rick Paulas writes at The Awl, the media attention has already brought many changes to the "artist collective" aspect of the Bay Area and beyond: How The Media Mishandled The Ghost Ship Fire

“It was a tragedy, then it became a tragedy on an entirely different spectrum,” said Friday. “The original was the loss of such vibrant, wonderful people. And that was forgotten and it just became about housing ordinances, and this witch hunt of warehouses.”

The hunt continues, not just in Oakland, but around the country. City governments — rather than focusing efforts on bringing warehouses up to code, of empathizing with tenants forced to live in unsafe conditions due to increasing rents and lower wages, hell, even pragmatically understanding the added value these fringe residents add to a city’s cultural cachet — are simply closing down venues, then moving on to close down the next. Two days after Ghost Ship, the tenants of Baltimore’s iconic Bell Foundry were evicted. A week after that, the punk venue Burnt Ramen in Richmond, CA was shut down. On April 27th, eight people living in an artist collective in San Francisco were evicted.

The cities say they don’t want another Ghost Ship, implying they mean another massive loss of life. But the speed at which they’re performing these evictions — and the lack of solutions they’re offering to those displaced — suggests that what they really don’t want is another Ghost Ship media event: vultures descending, camera lights illuminating the dark corners of their own institutional failures.

It's important that we not forget the Ghost Ship tragedy, but it's a hard story to (re-)read and (re-)consider, with plenty of sadness to go around.

Friday, June 16, 2017

Nice article on the Ethereum hack

Earlier this week, Bloomberg journalist Matthew Leising's in-depth article about the Ethereum smart contracts incident was published on the Bloomberg site: Ether Thief Remains Mystery Year After $55 Million Digital Heist

It's an interesting article; it's as much about social organizations as it is about computer organizations.

Once Van de Sande got in touch with Green in Germany, along with two or three others, the foundation was laid for what would become known as the Robin Hood group—white hat hackers who’d devise a bold good-guy plan to drain the remaining DAO. To save the DAO, they’d have to steal the remaining ether, then give it back to its rightful owners.

And yet as they scrambled that Friday, qualms emerged within the group. “What does it even mean to hack something?” Van de Sande asks. No one knew if what they were about to do was legal. Also, wouldn’t their hack look just as bad as the theft they were trying to stop? Then there were the practical issues. “Who pushes the button?” he remembers wondering. Doing so would initiate their counterattack and alert the community. “Someone has to push the button.”

The blockchain concepts are absolutely fascinating to me, although I became obsessed with learning about the blockchain in a rather odd way; I arrived there by studying how git compared to Perforce.

The basic notion of the blockchain is also the under-pinning of the most important versioning software in the world, git. There are many ways in which the two algorithms are similar. The most important way in which they differ is that git is designed for use by people who desire and intend to collaborate; the blockchain is designed for use by people who don't. Danno Ferrin does a much better job of explaining this here.

Some of the best coverage of Ethereum and the DAO, I think, comes from Bloomberg's Matt Levine, who has been writing about this topic for several years, including this excellent article from a year ago: Blockchain Company Wants to Reinvent Companies.

As Levine has pointed out, and continues to point out, efforts like Ethereum and the DAO are full of algorithms and computers and science, but they are also inevitably inter-twined with the social interactions of the human beings that want to use these algorithms:

Smart contracts are cool! Companies are weird bundles of contractual relationships that have become stereotyped and calcified over time, and re-imagining those relationships for a new and more technology-enabled age is a good project. But companies aren't just networks of contracts; they aren't pure agreements negotiated freely between willing participants and no one else. They are also structures that are embedded in society, with rights and responsibilities that are regulated by background rules as well as by contracts. The blockchain-y reinvention of everything in the financial world -- money, contracts, companies -- is fascinating and impressive and, viewed from a certain angle, adorable. But sometimes it could stand to learn from what has gone before. After all, the elements of finance -- money, contracts, companies -- have already been invented. Perhaps their historical development might hold some lessons for their re-inventors.

Note that, when it comes to re-inventing, you'll see that many of the links from Levine's year-old article no longer work. Web sites get re-invented all the time, as people change their minds about what they think and what they want to say.

With git and Perforce, recognizing that software is not just pure science, but exists to serve the goals of the human beings who use it, lends depth and nuance to the analysis and comparison. Yes, it's cool that everything is a SHA; on the other hand, have you ever looked at two indirectly-related commit SHAs and tried to understand the underlying history that led those repositories to get to those states? Less-efficient systems may be much easier for humans to use.

Blockchain systems often suffer from similar chasms of (un-)usability, as Leising observes:

Who, exactly, were they at war with?

No one really knows, but there are some clues. One address the attacker used is 0xF35e2cC8E6523d683eD44870f5B7cC785051a77D. Got that? Like everything else in a blockchain, a user’s address is an anonymous string of characters. But every address leaves behind a history on the blockchain that’s open for examination. Not that it makes sense to 99.9 percent of humankind, but Green gets it.

It's just an algorithm, it's just code, and it is completely accurate to note that there is a complete "history on the blockchain that's open for examination." (It's just as true with git.)

But as Levine points out, the most interesting aspects of all of this are not really the technical ones, but the human ones:

"What does it even mean to hack something" seems to be the key philosophical question of the DAO episode, and I submit to you that you probably don't want to invest your life savings in projects that raise philosophical questions like that. If your bank ever said to you "well, what does it even mean to hack something," you would worry. You know what it means! It's just that, with the DAO, the code didn't know what it means, and the whole point of the DAO was to substitute the code's judgment for yours.

And here, then, is one of the crucial differences between using git, and using a blockchain system. With git, if somebody does something disruptive, like a merge instead of a rebase, or an unwanted force push, the community using that particular collection of repositories collaborates and cooperates to repair the damage.

But blockchains are intentionally intended for situations where the users explicitly do NOT collaborate and cooperate. And, in Ethereum, there is a challenge, because some people viewed the hack as damage, and wanted to undo it, where others did not, leading to the situation described by Leising:

Then something else unexpected happened. The original ethereum blockchain, the one with the DAO attack in it, kept growing. Imagine a hard fork is a branch of a tree that sprouts in a different direction at the end of the main limb. The end of that limb is supposed to wither after a hard fork, but here it continued to grow as a small group of users continued to process transactions on that version of the blockchain. Instead of dying, this became a second form of ethereum, quickly dubbed ethereum classic, complete with a digital currency that now had value. Even in the science fiction world of blockchain, this was an unprecedented turn of events.

Computers are fascinating. Algorithms and software are fascinating.

People are more fascinating still.

Tuesday, June 13, 2017

A Place of Greater Safety: a very short review

Somewhat with my recent trip to France in mind, I picked up Hilary Mantel's A Place of Greater Safety.

In the end, I lugged the book around Alsace, but ended up reading it both before and after the trip rather than while I was there, which was actually just fine.

Mantel is well-known to me: I adored her Wolf Hall and Bringing up the Bodies, which are more recent work by her. A Place of Greater Safety is just celebrating its 25th birthday. But it doesn't read like an early work; she was every bit the master writer even then.

I doubt I gave A Place of Greater Safety the time and attention it deserves. At 750 pages of rather dense prose, in which you are reluctant to miss even a single word, much less a phrase or paragraph, I pushed through it as fast as I could, but still it took 2 months.

In the end, what do I think I learned?

  • In a Revolution, almost by definition, nobody is in control of events, even, perhaps most especially, not those who THINK they are in control of events.

  • The French Revolution is, nowadays, remembered as a time and a place when wondrous progress was made in the world of ideas (The Declaration of the Rights of Man, "Liberte, Egalite, Fraternite", the Republic, feminism, secularism, etc.), but the actual story was much a story of people and what they said and did day-to-day. That is, nobody sat down one day and decreed the entire thing; events happened incrementally, in the heat of the moment, under pressures and in situations that it can be hard to envision.

  • People are, in the end, people. Nobody really set out to Have A Revolution, and even once it was underway, lots of other life went on at the same time: people got married, had children, had affairs, got sick, got divorced, moved house, got in arguments, all sorts of things. We might want to write A Clean Story Of The French Revolution Leaving Out All The Boring Humdrum Stuff, but that wouldn't be telling the story the way it really happened.

  • Mantel is a lovely writer, and it it is always a treat to read her books, even if one must thus read about awful events (not all the events she relates are awful; some are vividly inspirational, but there is plenty of misery to go around)

Friday, June 9, 2017

It's not just a game ...

... it's a landscape so detailed and realistic, landscape designers study it: We asked a landscape designer to analyse The Witcher 3, Mass Effect and Dishonored

The Witcher 3's recreation and representation of a range of Northern Hemisphere, European natural landscapes through their design is one of the game's finest accomplishments. Not only do the mountains look genuinely geologically convincing, the woods naturally dense, and the fields rolling, but everything down to the smallest details of the design give them an extra quality - they become believable landscapes and places. Our aesthetically-aimed eye will look at the game and instantly recognise that, of course, that mountain on the horizon looks mountainous in shape and that river bends absolutely naturally enough, but in each of the landscapes and environments created, there are elements of landscape design that would feature in the real world when re-creating a believable naturalistic look and feel.

For example, in all the wooded areas of the North, from the Skellige Isles through to Velen and White Orchard, we see a typical forest of Northern Europe represented with an accurate mix of pines and deciduous trees, underplanted faithfully with a grassy forest floor featuring low-growing, shade-tolerant plants such as ferns, and, where the light allows, more colourful herbaceous plants such as hellebores - a great example of one plant growing exactly where, and how, it should do.

Thursday, June 8, 2017

The Upper Rhine Valley: small towns

When I think back about our trip to France and Germany, there is no doubt that visiting the major cities of the region was a highlight. Strasbourg, Freiburg, Frankfurt, Basel: these are beautiful cities, all of them, with many fascinating things to see and do.

But just as strong in my memories are the wonderful experiences we had in the small towns we visited.

In the tiny hamlet of Hunspach, the town was closed up tight and silent on a peaceful Sunday morning. But the houses were beautiful and well-tended, and we had a most enjoyable walk up and down the quiet side streets.

In Betschdorf, we pulled into a tiny parking lot, attracted by a sign that said "Poterie". As we looked into the studio window, the craftsman himself came walking out of his house across the way, smiled at us, walked over, unlocked the studio door, and let us in. Although he spoke very little English, and we even less French, his little ceramic figurines were playful and they were instant hits with Donna, who bought several lovely pieces for her garden.

In Haslach im Kinzigtal, after a fairly long drive, we took a long leisurely walk through the beautiful town center, not in the slightest dismayed by the misting rain. To keep us fortified, we stopped at the gelato house, where I had the most delectable black-currant flavored gelato as I wandered the cobblestone lanes.

In Dambach la Ville, we somewhat surprised the young proprietor of Domaine Schaeffer-Woerly as he was repairing some household furniture in the back of his house-which-is-also-his-winery. Taken aback for only a minute, he recovered immediately and gave us a delightful tour of his winery, culminating in welcoming us into the family kitchen where his mother (!) poured us samples of the delicious wines they make.

In Kaysersberg, the birthplace of Albert Schweitzer, a steady rain had swollen the creek that runs through town, but that didn't stop me from getting out and poking my head around at the beautiful little town.

In Soufflenheim, we found we were hungry, and we stopped at the lovely Restaurant à la Couronne, where the food was delicious, the building was beautiful, and the people were as friendly as you could ever hope for.

In Rosheim, we discovered that a drizzly morning doesn't keep the regional merchants from setting up shop in the town center for the weekly market. The enthusiastic staff of the fishmarket stall were only too happy to tell us all about the different types of regional seafood that they specialize in.

In Mittelbergheim, we arrived at Domaine Alfred Wantz just as they were closing for the mid-day break, but the proprietress spotted us through the window and graciously opened back up, taking time to talk with us about the town, and the winery, and the wines, right on through her lunch break.

Oh, I could go on, and on, but I'm sure you get the idea.

It isn't just the mighty tourist spots (Chateau Haut Koenigsburg, Strasbourg Cathedral, the Freiburg Munster, ...); it's the little things that can be the most charming of all.

So if you ever get a chance to visit this part of the world, by all means visit the beautiful cities.

But try to go visit the small towns, too.

Monday, June 5, 2017

Alex Honnold pushes beyond the limits again

This is simply extraordinary: Alex Honnold Climbs Yosemite's El Capitan Without a Rope

Renowned rock climber Alex Honnold on Saturday became the first person to scale the iconic nearly 3,000-foot granite wall known as El Capitan without using ropes or other safety gear, completing what may be the greatest feat of pure rock climbing in the history of the sport.

He ascended the peak in 3 hours, 56 minutes, taking the final moderate pitch at a near run. At 9:28 a.m. PDT, under a blue sky and few wisps of cloud, he pulled his body over the rocky lip of the summit and stood on a sandy ledge the size of a child’s bedroom.

If you're having trouble coming to grips with this achievement, well, so are a lot of us: Alex Honnold casually climbed a rock higher than the world's tallest building. With no safety gear.

The feat is extraordinary without the athlete; the athlete regards it as logical and normal; by extension, the athlete is simply doing what they are there to do, and anyone watching now realizes that they are in the company of a legitimate mutant, someone whose achievements are only made normal by comparison with the extranormal person producing them. I’m out of ways to say this: Alex Honnold is human, and so are you, and that the definition includes both is proof that words are shoddy signifiers for the reality they are supposed to represent, because Alex Honnold climbed Freerider without a rope and it didn’t even seem like an unsafe, unwise thing for him to do.

Thursday, June 1, 2017

The East Cut

Ah yes:

What's Montague? it is nor hand, nor foot,
Nor arm, nor face, nor any other part
Belonging to a man. O, be some other name!
What's in a name? that which we call a rose
By any other name would smell as sweet;

Anyway, I learn today that the place where I work has a new name: New image for a slice of SF: The East Cut

History buffs will catch the reference to when Rincon Hill was bisected in 1869 to make Second Street a flat thoroughfare connecting downtown and the commercial waterfront. There’s a quest for cool as well: to identify this a place with “constant motion and evolution, serendipitous encounters, unanticipated inspiration,” according to the district website.

With the name comes a logo of three horizontal bars connected to form an abstract E. One represents Rincon Hill. Another represents what planners call the Transbay District. In the middle is Folsom Street, which the city plans to upgrade with wide sidewalks and landscaping to humanize the towers on either side.

It's not just me who works here, of course. Probably 100,000 people work inside this neighborhood, showing up every day at places like Linked In, Google, Splunk, DropBox, Mozilla, Salesforce, and on and on and on. It's an astonishingly vibrant neighborhood, with an energy and intensity and excitement that you just have to feel to believe.

Of course, it already had a name, sort of:

“I don’t know why they want to rebrand Rincon Hill, which is real and historic and accurate,” said Lauri Mashoian, who lives with her family on First Street in a restored industrial building.


“Nobody really knows where Rincon Hill is, or what it is,” Robinson suggested a bit sheepishly.

Which is, of course, just crazy. Everybody should know where Rincon Hill is, and what it is. Why, just go read about it: February, 1869 The laceration of Rincon Hill

According to the Annals of San Francisco, by 1853 Rincon Hill was dotted with “numerous elegant structures” — including the little gated community of South Park. By the 1860s, the Hill was covered with mansions in a riot of architectural styles, and had become the social epicenter of the young city.

For these parts, that's a long time ago; it's what passes for history. (South Park is just beautiful, still, by the way.)

Wandering around these streets nowadays, it's terribly hard to envision what it must have been like in the 1850's, just after the Gold Rush had begun, when San Francisco was the center of the nation, if not the world: everybody who could possibly arrange it was traveling to San Francisco to Start Over, to Make Their Fortune, to be Part Of Something Big, to Change The World.

Oh, wait.

Perhaps it's not so hard to imagine those days, after all, even if it's a different sort of Gold Rush nowadays.

Tuesday, May 30, 2017

Freshening up my (Linux) hat

I was getting ready to do some work on Derby, and since it was a fine weekend and I had some time to spare, I decided to take the opportunity to update my development environment.

I had been running Fedora 22 for quite some time, and it's become rather out of date.

So now I'm running Fedora 25, which is much more modern.

I still have the dickens of a time trying to get Linux guest machines to recognize my video hardware via VirtualBox, so all too often I just get a 1024 x 768 display, which ain't much.

The message

VBoxClient: the VirtualBox kernel service is not running. Exiting.
should win some sort of award for "error message most likely to give you bad and useless suggestions when you Google search for it."

Still, at least I've got a more up-to-date OS on my guest.

Sunday, May 28, 2017

GVFS status report from Microsoft

The largest Git repo on the planet:

Today, I want to share our results. ... we have largely completed the rollout of Git/GVFS to the Windows team at Microsoft ... we now have about 3,500 of the roughly 4,000 Windows engineers on Git ... We knew when we rolled out Git that lots of our performance work wasn’t done yet and we also learned some new things along the way. ... over time, engineers crawl across the code base and touch more and more stuff leading to a problem we call “over hydration”. Basically, you end up with a bunch of files that were touched at some point but aren’t really used any longer and certainly never modified. This leads to a gradual degradation in performance. ... another round of performance improvements we call “O(modified)” which changes the proportionality of many key commands to instead be proportional to the number of files I’ve modified (meaning I have current, uncommitted edits on) ... we invested in building a Git proxy solution for GVFS that allows us to cache Git data “at the edge” ... 70 seconds vs almost 25 minutes is an almost 95% improvement ... working to get all of those changes contributed back to the mainline

Also interesting: Git at Scale:

Saturday, May 27, 2017

The Upper Rhine Valley: chateaux

A co-worker asked me to sum up my visit to France in two words; on the spot, I chose "wineries" and "castles".

It's of course no surprise that a visit to France is rich with wineries, but when we were first thinking about traveling to Alsace I was not thinking about castles, which are more properly described as chateaux.

And for much of our time in France we were in towns and cities, and really didn't think much about either wineries or castles, but rather about cathedrals and cobblestone streets and canals and half-timbered houses and the like.

But then, one day, we went out for a drive in the country, and we stopped and had a picnic lunch.

And there we were, sitting at a picnic table next to a beautiful country winery, in a beautiful town in a part of the world where wine-making has been practiced for nearly two thousand years. And the weather was beautiful, and we were looking up at the Vosges mountains above town, and we saw, across the mountain ridges, castle after castle after castle.

Really, it's just like they promise on the chamber of commerce web site:

Anyway, this part of France is simply blanketed with these beautiful chateaux, as you can easily see for yourself by looking at the "Bas-Rhin" (lower Rhine valley) and "Haut-Rhin" (upper Rhine valley) sections of the List of castles in France page on Wikipedia. Bas-Rhin and Haut-Rhin, together, comprise the major part of the Alsace region, and just by skimming the Wikipedia page you can see that no other part of France is as full of castles as this.

Why is that? Well, apparently we have a father-son pair to thank: Frederick the first of Swabia, and his son Frederick ("the one-eyed"), founders of the mighty Hohenstaufen dynastic family of the Middle Ages, ruled over these parts in the 1100's and built literally dozens of castles along the ridges of the mountains on either side of the Upper Rhine Valley (the Vosges to the west, the Swabian Jura to the east).

One lovely local guidebook I read says that there is an Alsatian saying that "Frederick the One-Eyed placed chateaux around the Vosges as though he was flicking his horse's tail."

Even in ruined state, these castles are gorgeous, as you can see in this picture I took on our visit to Kastelberg, near Waldkirch, Germany:

But, really, it's very hard to understand the role of these castles in their ruined state.

You find yourself mystified: what were these places like? Why were they built? Why on the top of mountain ridges? Who lived here? What was it like to live here?

Questions like these are why Chateau Haut-Koenigsbourg is such a delight.

Although the castle is one of the Hohenstaufen constructions, and hence is almost 900 years old, and was completely destroyed during the Thirty Years War, it was beautifully and carefully restored about 130 years ago and has been carefully maintained ever since.

Taking the tour of this castle was definitely one of the highlights of my trip. The museum is superb, with lots of information displayed as you wander the massive, extensive castle from bottom to top and back down again.

We were lucky to visit on a glorious summer day, yet have the grounds mostly to ourselves (a major surprise, since the castle is said to be one of the top 10 most-visited destinations in all of France!).

We spent hours there.

In fact, I was so enthralled that I broke one of my unwritten "laws of traveling" and bought a lovely little souvenir booklet in the gift shop, which I very much enjoyed reading.

If we had a month to spend in Alsace, or better if we actually lived there, I'm sure I would go to visit as many of these beautiful chateaux as I could.

But since our time was sadly limited, I am wonderfully happy that we got to see the ones we did, and if you ever find yourself in Alsace I thoroughly recommend that you visit at least Chateau Haut-Koenigsburg, and perhaps several more as your time permits.

Thursday, May 25, 2017

It's not just a game ...

... it's a mini-series: The Witcher Is Getting A Netflix Series.

... and it's a story that stays with you, years later: Reading The Game: Witcher 3

It is the story of a man looking for his daughter. It is the story of a lot of people looking for a lot of missing things — friends, comrades, nations, history


It is rare for a big game to be so focused on the small things. Exceedingly rare for it to be made up, more or less, of a thousand trivial, funny, sad, often pointless stories which all, in their way, cut the path that the plot will ultimately follow.

Good games are epic. Great games are true. And Wild Hunt is that rarest of modern, digital myths: One that is both.

Tuesday, May 23, 2017

Updated list of my trips with Mike

I'm going to try to use the Blogger "pages" facility to keep track of this, because it works better than having a new summary post every year: My Backpacking Trips with Mike.

Sunday, May 21, 2017

The Upper Rhine Valley: prelude and overture

We took an altogether-too-short but thoroughly wonderful trip to the Upper Rhine Valley region of Europe. I'm not sure that "Upper Rhine Valley" is a recognized term for this region, so please forgive me if I've abused it; more technically, we visited:

  1. The Alsace region of France
  2. The Schwarzenwald region of Germany
  3. The neighboring areas of Frankfurt, Germany, and Basel, Switzerland.
But since we were at no point more than about 40 miles from the Rhine river, and since we were several hundred miles from the Rhine's mouth in the North Sea, it seems like a pretty good description to me.

Plus, it matches up quite nicely with this map.

So there you go.

Anyway, we spent 10 wonderful days there, which was hardly even close to enough, but it was what we had.

And I, in my inimitable fashion, packed about 30 days of sightseeing into those 10 days, completely exhausting my travel companions.

Once again, no surprise.

I'll have more to write about various aspects of the trip subsequently, but here let me try to crudely summarize the things that struck me about the trip.

  • Rivers are incredibly important in Europe, much more so than here in America. Rivers provide transportation, drinking water, sewage disposal, electric power, food (fish), and form the boundaries between regions and nations. They do some of these things in America, too, but we aren't nearly as attached to our rivers as they are in Central Europe, where some of the great rivers of the world arise.
  • For centuries, castles helped people keep an eye on their rivers, and make sure that their neighbors were behaving as they should in the river valleys.
  • Trains are how you go places in Europe. Yes, you can fly, or you can drive, but if you CAN take a train, you should. And, if you can take a first class ticket on TGV, you absolutely, absolutely should. I have never had a more civilized travel experience than taking the TGV from Frankfurt to Strasbourg. (Though full credit to Lufthansa for being a much-better-than-ordinary airline. If you get a chance to travel Lufthansa, do it.)
  • To a life-long inhabitant of the American West, Central Europe is odd for having almost no animals. People live in Central Europe, nowadays; animals do not. BUT: storks!
  • France, of course, is the country that perfected that most beautiful of beverages: wine. While most of the attention to wine in France goes to Southern France, don't under-rate Alsace, for they have absolutely delicious wines of many types, and have been making wine for (at least) 2,000 years. We Californians may think we know something about wine; we don't.
  • The visible history of the Upper Rhine Valley is deeply formed by the Franks. Don't try to understand the cathedrals, villages, cities, etc. without spending some time thinking about Charlemagne, etc. And, if you were like me and rather snored through this part of your schooling, prepare to have your eyes opened.
  • The other major history of the Upper Rhine Valley involves wars. My, but this part of the world has been fought over for a long time. Most recently, of course, we can distinguish these major events:
    1. The Franco-Prussian war, which unified Germany and resulted in Alsace being a German territory
    2. World War One
    3. World War Two
    Although the most recent of these events is now 75 years in the past, the centuries and centuries of conflict over who should rule these wonderful lands has left its mark, deeply.

    So often through my visit I thought to myself: "Am I in French Germany? Or perhaps is this German France?" Just trying to form and phrase these questions in my head, I realized how little I knew, and how much there is to learn, about how people form their bonds with their land, and their neighbors, and their thoughts. Language, food, customs, politics, literature: it's all complex and it's all one beautiful whole.

    This, after all, is the land where Johannes Gutenberg invented the printing press, where people like Johann Wolfgang von Goethe, Louis Pasteur, John Calvin, and Albert Schweitzer lived and did their greatest work.

I could, of course, have been much terser:

  1. The Upper Rhine Valley is one of the most beautiful places on the planet. The people who live there are very warm and welcoming, and it is a delightful place to take a vacation
  2. Early May is an absolutely superb time to go there.

I'll write more later, as I find time.

Back online

I took a break from computers.

I had a planned vacation, and so I did something that's a bit rare for me: I took an 11 day break from computers.

I didn't use any desktops or laptops. I didn't have my smartphone with me.

I went 11 days without checking my email, or signing on to various sites where I'm a regular, or opening my Feedly RSS read, or anything like that.

Now, I wasn't TOTALLY offline: there were newspapers and television broadcasts around, and I was traveling with other people who had computers.

But, overall, it was a wonderful experience to just "unplug" for a while.

I recommend it highly.

Sunday, April 30, 2017

Staying up to date

One thing about having several computers, and about never having quite enough time to work on them, is that whenever I turn on a particular computer, it's almost certain that I'll have updates to perform:

  • Windows updates
  • Java updates
  • nVidia driver updates
  • Steam updates
  • etc.

In fact, I'll usually have at least 2 or 3 updates that run whenever I switch one of my computers on.

At least the updates are mostly self-sufficient, though I can never really get the hang of which updates just run automatically, and which require me to baby-sit them at least to the point where they put up a confirmation prompt requesting me to authorize them to update their own software.


Meanwhile, in the world of updates, I'm trying to figure out if Windows Subsystem for Linux has matured to the point where I can run Java 8 on it.

As best I can understand from poking around on duh Netz, it seems that:

  • Oracle's Java 8 distribution has made a number of fixes, and now can be successfully installed and run on Windows Subsystem for Linux, at least according to this StackOverflow answer
  • But Java 8 in general really seems to prefer Ubuntu 16 over Ubuntu 14,
  • And Microsoft themselves suggest that both Java 8 and Ubuntu 16 are able to be used once I have upgraded to Windows 10 Creators Update (see this MSDN blog article)

So it seems like the bottom line is that for the time being, I should continue to do my Java work using either the vanilla Windows JDK, or using my full Linux installation on my VirtualBox instance(s).

But hopefully Windows 10 Creators Update will reach my machine soon (if I get really impatient, Microsoft says I can possibly hurry the process along using the Update Assistant).

And then I can start a whole new round of updates!

Thursday, April 27, 2017

An Alameda high rise?

Alameda Magazine, which frankly is simply a Chamber of Commerce flyer, nonetheless ran this breathless article: Alameda’s First High-Rise?

A developer is proposing to build a 14-story, 589-unit housing project on the waterfront at the long-dormant Encinal Terminals site. The project, which would be constructed directly across the estuary from Oakland’s 3,100-unit Brooklyn Basin housing development now under construction, would feature the Island’s tallest building.

“We are building a world-class waterfront” that will be “a centerpiece for the estuary,” said Mike O’Hara, a representative of developer Tim Lewis Communities, or TLC. TLC recently broke ground on another 380-unit housing project on the adjoining historic Del Monte warehouse property.

I certainly would like to see the estuary waterfront opened up and reclaimed. Currently it is a wasteland of abandoned warehouses, docks, and vacant lots, mostly fenced off and sitting idle. It could be some of the most beautiful space in the Bay Area, if it is done well.

As the article notes, however, this is far from a slam dunk:

the Encinal Terminals project faces a more complicated regulatory approval than most developments. The 32-acre site includes nine submerged acres, large dilapidated wharf structures, and six acres of state tidelands. Under state law, tidelands property cannot be used for housing, so the project would require the swapping of private acreage around the perimeter of the site for tidelands property in the interior—a plan that also would have to be approved by the state.

It just so happened that I had the chance today to wander down to a similarly-long-under-used section of the San Francisco waterfront, known as "Dogpatch", where an enormous gentrification project is underway, scheduled to run for at least another 15 years.

The cities are changing. The Bay Area is changing. It's good to remember the history, but it's also good to invest in the future.

On we go.

Bad Behavior: a very short review

I was rambling around on the Internet, leafing through some random person's "book recommendations" page, when I came across a recommendation for Mary Gaitskill's Bad Behavior: Stories, and decided to take a chance on it.

What an astonishing collection of stories this is!

Of course, at this point, 30 years have passed, and so this is old news to everyone, but still. I'm not sure I've ever read somebody whose writing seemed so vivid, so real, so true.

This. Is. How. People. Really. Think. And. Act. And. Talk.

However, what goes hand-in-hand with this is that her stories are not for the faint of heart. They are raw, fearless, clear-eyed views into the very abyss of our human souls; Gaitskill neither flinches nor turns away from the truth, no matter how horrid the vision she sees.

I'm tremendously glad I read these stories, but on the other hand they're not the sort of thing I'd feel comfortable recommending to anyone.

If they're the sort of thing you'd enjoy, you've probably already found them, somehow.

Of course, I hadn't, and so I'm glad I did.

Tuesday, April 25, 2017

GBooks, 15 years on

Three perspectives:

  • How Google Book Search Got Lost
    Two things happened to Google Books on the way from moonshot vision to mundane reality. Soon after launch, it quickly fell from the idealistic ether into a legal bog, as authors fought Google’s right to index copyrighted works and publishers maneuvered to protect their industry from being Napsterized. A decade-long legal battle followed — one that finally ended last year, when the US Supreme Court turned down an appeal by the Authors Guild and definitively lifted the legal cloud that had so long hovered over Google’s book-related ambitions.

    But in that time, another change had come over Google Books, one that’s not all that unusual for institutions and people who get caught up in decade-long legal battles: It lost its drive and ambition.


    But Google took away a lesson that helped it immeasurably as it grew and gained power: Engineering is great, but it’s not the answer to all problems. Sometimes you have to play politics, too — consult stakeholders, line up allies, compromise with rivals. As a result, Google assembled a crew of lobbyists and lawyers and approached other similar challenges — like navigating YouTube’s rights maze — with greater care and better results.

  • Torching the Modern-Day Library of Alexandria
    What happened was complicated but how it started was simple: Google did that thing where you ask for forgiveness rather than permission, and forgiveness was not forthcoming. Upon hearing that Google was taking millions of books out of libraries, scanning them, and returning them as if nothing had happened, authors and publishers filed suit against the company, alleging, as the authors put it simply in their initial complaint, “massive copyright infringement.”


    Amazon, for its part, worried that the settlement allowed Google to set up a bookstore that no one else could. Anyone else who wanted to sell out-of-print books, they argued, would have to clear rights on a book-by-book basis, which was as good as impossible, whereas the class action agreement gave Google a license to all of the books at once.

    This objection got the attention of the Justice Department, in particular the Antitrust division, who began investigating the settlement. In a statement filed with the court, the DOJ argued that the settlement would give Google a de facto monopoly on out-of-print books. That’s because for Google’s competitors to get the same rights to those books, they’d basically have to go through the exact same bizarre process: scan them en masse, get sued in a class action, and try to settle.


    It was strange to me, the idea that somewhere at Google there is a database containing 25-million books and nobody is allowed to read them. It’s like that scene at the end of the first Indiana Jones movie where they put the Ark of the Covenant back on a shelf somewhere, lost in the chaos of a vast warehouse. It’s there. The books are there. People have been trying to build a library like this for ages—to do so, they’ve said, would be to erect one of the great humanitarian artifacts of all time—and here we’ve done the work to make it real and we were about to give it to the world and now, instead, it’s 50 or 60 petabytes on disk, and the only people who can see it are half a dozen engineers on the project who happen to have access because they’re the ones responsible for locking it up.

  • Why Google Books Deserves Better Than These Obituaries
    Unfortunately, the copyright case over Google Books morphed into something larger. It became a vehicle for anxieties over how the digital era has undermined authors on a financial and cultural level. Those concerns are legitimate, but scapegoating Google Books for these fears was misguided.

    Meanwhile, groups like the Authors Guild continue to celebrate the collapse of the settlement even though no other options have emerged to replicate its potential benefits. Those benefits would have included a new market for digital copies of old books, and a solution to the problem of "orphan works"—books whose authors cannot be located that are out-of-print but still under copyright protection. Instead, there is stasis.


    But if Google is to dispel the recent mutterings about the project's decline, it must do more to raise the profile of Google Books, and offer some assurances about how it will ensure the collection—which, recall, is nothing less than the history of human knowledge—will survive. Ideally, the company should create a trust or foundation to manage it so as to ensure it endures no matter what corporate changes come at Google.

    Meanwhile, it's time for Google Books opponents to acknowledge the astonishing thing Google has built. Critics like the former head of Harvard libraries, Robert Darnton, have long suggested some university or public consortium can replicate the project. But today it's clearer than ever this is just a pipeline, and no one will muster the money, energy, and technology to do what Google did also over again.

Saturday, April 22, 2017



So it turns out that the horrible bombing attack on the Borussia Dortmund football team was in fact NOT Islamic terrorists at all.

Rather, it was something much more banal: One man’s greed behind Dortmund attack, after all

Not many -if any- had seen this coming… Something more than a week after the triple bomb attack that targeted Borussia Dortmund and led to their Champions League game against Monaco being delayed by 24 hours, police have announced that the motive behind the whole incident was pure financial greed.
The accused bought 15,000 put-options regarding the shares of Borussia Dortmund on April 11. Those options were running until June 17, 2017 and were bought with the ID of the hotel L’Arrivee (Dortmund’s team hotel)
a prosecutor made known, through a written statement, after the police arrested a 28-year-old man

The Beeb has (a bit) more: Borussia Dortmund bombs: 'Speculator' charged with bus attack

Rather than having links to radical Islamism, he was a market trader hoping to make money if the price of shares in the team fell, prosecutors say.

The suspect has been charged with attempted murder, triggering explosions and causing serious physical injury.

He has been identified only as Sergej W, and was staying in the team's hotel overlooking the scene of the attack.

There was, I should think, more than just greed involved, as clearly the man was quite mentally ill:

He was staying at the team's L'Arrivée hotel in Dortmund on the day of the attack and had moved to a room on the top floor, overlooking the street where it took place, prosecutors say.

The suspect placed the bet on 11 April using an IP address traced to the hotel, after taking out a loan for the money.

That's somewhere bordering on stalker-level obsession, I'd say.

Very sad.

But I'm glad the German police were level-headed and careful and thorough and dug down to the underlying facts of the matter.

And SHAME on all those trashy publications that threw horrid terror speculations out there.

Yes, I'm looking at you, The Sun, and The Express, and The NY Post, and Fox News and The Star, and ...

You know who you were. Shame on you all.

Three Junes: a very short review.

Julia Glass's Three Junes tells the story of an (extended) Scottish family across multiple generations, mostly set during the later decades of the 20 century.

It is beautifully written and quite emotional at times.

Wednesday, April 19, 2017

A break in the rain

It was a beautiful day in the city, so I wandered over to the border between Chinatown and North Beach and hooked up with some old friends for a wonderful lunch.

Thanks, all!

Cop stories

I'll read almost everything; I'm pretty voracious that way.

But certainly a good police procedural is always right up my alley.

So, two recommendations, one old, and one new:

  • The Fairy Gunmother

    Pennac's novel is set in a post-imperial Paris of the mid-1980's, rich with the complexities that entails, and benefits from a truly superb translation by Ian Monk. The result is laugh-out-loud funny while still being atmospheric and compelling.

  • Leviathan Wakes

    Although you'll find this on your Science Fiction shelves at the local bookstore (hah! is there such a thing?), it's really a police procedural set in the future, in space, as more-than-haggard Detective Miller is trying to unravel why a simple missing persons case appears to be much, much deeper than it first seemed.

Each of these is "Book 1 of a series".

And I'll be reading more of each series, straightaway.

Sunday, April 16, 2017

Blue Apron

We're entering our third month as regular Blue Apron customers.

If you have no idea what Blue Apron is, here's a nice introduction which takes a business perspective but covers the overall service quite well: Inside Blue Apron’s Meal Kit Machine

Each month, Blue Apron delivers about 8 million meal kits to Americans who like to cook but would rather not waste time shopping or searching for recipes. Blue Apron boxes include cooking instructions for meals and suggested wine parings—shiitake mushroom burgers with a Santa Barbara Highlands Vineyard Grenache, for example. The raw ingredients, which include such exotica as romanesco cauliflower and fairy tale eggplants, are sourced from family farms and artisans. Then they're sorted, chopped and packaged in giant fulfillment centers and delivered to homes around the country.

It's still early days for us as Blue Apron consumers, but here are some of my impressions:

  • The ingredients are high-quality, and fresh.

    This was our primary concern, since we're both rather picky shoppers. But in every meal to date, the meat has been very high quality, the produce has been equally good (and quite fresh), and we've not once been disappointed in the ingredients.

  • The service is reliable and accurate.

    The weekly carton arrives on time, with the meals as promised, precisely. Everything is clearly marked; everything is present. The little individual packages of ingredients are right-sized, even if the amount of packaging does bum me out a bit.

  • The proportions and quanties are right.

    We take the "meal for two" service. We never have too much overall, and we never have too little overall. And the individual ingredient amounts are appropriate, too. We don't find ourselves saying "there weren't enough carrots," or whatever.

  • The recipes are clear, accurate, easy to follow, and acceptably quick.

    If the meal says: "prep time 10 minutes, overall time 35 minutes," it turns out to be quite close to that. We haven't yet found ourselves confused, halfway through a recipe, by a missing step. The recipes are printed on stiff paper which stands up nicely in front of you while you're chopping and mixing. The recipes have nice pictures which illustrate the important steps.

    And, as an pleasant touch, they almost always end with a little bit of elegance, showing you how to "plate your dish" for visual appeal, and encouraging you to "enjoy!"

  • The recipes have just enough variety to be entertaining.

    We've been introduced to some ingredients we don't typically use (freekeh, farro, za'atar, labneh, etc.), and some techniques we had never even considered. For a "chicken under a brick" recipe, Blue Apron walked us through how to cook a half-chicken with a large pot of water balanced on TOP of the chicken, pressing down on it as it cooked. It worked startlingly well.

  • The recipes are fun to follow.

    At the end of a long day, you can be tired, and cranky, and not in the mood for failure. These recipes are straightforward, yet they often contain just enough new-ness, whether that be a different ingredient that you haven't used before, or a different technique, or whatever, to make the whole experience fun. Put on a nice album on the stereo, crack open the Blue Apron recipe, unwind, and make dinner together. That's pretty great.

My one complaint, so far, is that the recipes are a bit too liberal with "season with salt and pepper to taste." It's become a bit of a running joke in our house as we prepare a meal, noting that nearly every step in the instructions contains that phrase. Oh, what a nit-picker I am.

And, overall, they aren't the super-fanciest of recipes. You end up making chicken and carrots and potatoes a lot, although dressed up nicely so there's pleasant variety. But you don't end up making something you'd find at a two-star Michelin restaurant. How could you, in just 30 minutes, after all? I guess what I'm saying is that I doubt that people who deliberately set out to entertain would think to themselves to choose one of these recipes. But that's not what they're for.

My wife loves to cook, and typically prefers to cook meals from scratch, so at first she was rather uncertain how she'd feel about this service. But I'd say, overall, she's as happy with it as I am.

I guess I'm not certain if it will actually survive, however; I have this feeling that it is doing well in these relatively prosperous times, with unemployment low and people feeling relatively optimistic and willing to spend on the convenience factor.

The real trick will be, if the economy should take a downturn, whether Blue Apron can endure.

But for now, we're quite pleased.

Saturday, April 15, 2017

News "flash"

Sadly, the folks who tend the Jacquie Lawson website haven't yet heard about how old technology is, eventually, abandoned.

Hopefully, they will update their site before too long, because it IS a really nice site.

Thursday, April 13, 2017

A tree grows in the city

This might be the best opening line of a news article that I've read in years:

The trees are trucked to the Transbay Transit Center in the dead of night.

It's from this fascinating piece in the S.F. Chronicle: Transbay Transit Center rooftop turning into 5.4-acre City Park.

I can look down from the window in the kitchen area of my office and see (some of) the trees; specifically, I can see the area marked on the map as "Palm Garden".

I love the variety:

There are Chinese elms from Rainbow in northern San Diego County, and olive trees from Farmington in San Joaquin County. From Gilroy come island oaks, while Escondido was the source for five or six cork oaks. A Columnar Hornbeam came from a nursery outside Portland, while a rare torpedo-shaped Chilean wine palm was tracked down near San Diego.

I was particularly interested in the fact that the trees have been staged at the Valley Crest nursery in Sunol, because I know that nursery well: we drive past it on our way to Sunol Regional Wilderness, one of our favorite East Bay Regional Parks.

And, it's no doubt, the last few times we went out to the park, we were both astonished at the number and the size of the trees in the nursery.

Well, it turns out it's not just the Transbay Center that's been making use of the nursery to prep their trees: A look at Apple’s insanely ambitious tree-planting plans for its new spaceship campus.

In a cluster of East Bay nurseries, Apple has been growing more than 4,600 trees, which are nestled in large, wooden boxes. Some time later this year, Apple’s team of arborists will start shipping these trees two or three at time to Cupertino, where they will be painstakingly planted as part of the broader landscaping plan.


“Today, about 20 percent of the space is landscaping, most of it is big asphalt parking lots,” cofounder Steve Jobs said when first presenting the plans to the Cupertino City Council. “We want to completely change this and make 80 percent of it landscaping. And the way we’re going to do this – we’re going to put most of the parking underground. And you can see what we have in mind. Today there are 3,700 trees on the property, we’d like to almost double that.”

For Jobs, who grew up in the region, it was a chance to recapture the lost feel of an area that was once mostly open spaces and fruit orchards before it gave way to low-slung, drab office buildings.

“The landscape design of meadows and woodlands will create an ecologically rich oak savanna reminiscent of the early Santa Clara Valley,” Apple said in its proposal. “It will incorporate both young and mature trees, and native and drought tolerant plants that will thrive in Santa Clara County with minimal water consumption. The increase in permeable surfaces will promote natural drainage and improve water quality in Calabazas Creek. The thoughtful and extensive landscaping will recall Cupertino’s pre-agricultural and agricultural past.”

I don't know when I'll make it down to the Apple campus; it's a LONG way from my house, probably a 2.5 hour drive (each way) during a normal weekday.

But hopefully I'll get the chance, one day.

And, in the meantime, I can't wait to walk through the "mini botanical garden right downtown" when the Transbay Center opens later this summer.

Wednesday, April 12, 2017

Bye bye, Boing Boing

For more than a decade, I avidly followed the website

Boing Boing was an early "group blog", with a core team of a half dozen or so writers, who contributed smart, savvy, well-thought pieces about all sorts of interesting subjects.

But something happened, 9 months or a year ago, and since then the site has utterly collapsed.

Nowadays it's nearly indistinguishable from the common rot you find all over the Internet. It's loaded with advertising, not just the overt kind that all sites sport, but also the more insidious sort of testimonial advertising that has become popular, similar to the way that radio stations think that having the regular DJ read the advertising blurb somehow lends it more respect and legitimacy. When, in fact, the opposite is true.

And even the non-advertising content seems to be selected to appeal to a less-discerning sort of reader, tending more and more to the sort of rubbish you find on places like BuzzFeed.

And the comments section? Horrific, with trolls as bad as any you'll find anywhere on the net.

It's a shame, to see how rapidly what was once one of the shining lights of the Internet is now become some sort of "E! Channel" of web sites.

Oh, well, it's not worth shedding too many tears over its demise, I suppose, even though it makes me sad.

It does make you wonder, though: if BoingBoing has fallen, can the other great independent sites of the net be far behind?

I hope not; I hope the net still somehow finds a way to be a provider of quality independent voices.

But I fear that time is soon to be gone.