Sky’s mostly blue; still it’s raining. (at Solna, Sweden)

Photoset

wastholm.tumblr.com/post/147753694727/tree-stump, posted 21 Jul by peter

Tree stump.

Photoset

wastholm.tumblr.com/post/147698413327/vacation, posted 20 Jul by peter

Vacation.

Photoset

wastholm.tumblr.com/post/147542590127/currants, posted 17 Jul by peter

Currants.

Photoset

wastholm.tumblr.com/post/147408033297/sky, posted 14 Jul by peter

Sky.

Photoset

wastholm.tumblr.com/post/147394309587/summer, posted 14 Jul by peter

Summer.

@lastfm #RSS feeds return 404. Temporary problem? Permanently broken? Deliberately removed (but still linked to in API section of site)?

It may come as an even greater surprise that bushido once received more recognition abroad than in Japan. In 1900 writer Inazo Nitobe's published Bushido: The Soul of Japan in English, for the Western audience. Nitobe subverted fact for an idealized imagining of Japan's culture and past, infusing Japan's samurai class with Christian values in hopes of shaping Western interpretations of his country.

Though initially rejected in Japan, Nitobe's ideology would be embraced by a government driven war machine. Thanks to its empowering vision of the past, the extreme nationalist movement embraced bushido, exploiting The Soul of Japan to pave Japan's way to fascism in the buildup to World War II.

This article outlines the scale of that codebase and details Google's custom-built monolithic source repository and the reasons the model was chosen. Google uses a homegrown version-control system to host one large codebase visible to, and used by, most of the software developers in the company. This centralized system is the foundation of many of Google's developer workflows. Here, we provide background on the systems and workflows that make feasible managing and working productively with such a large repository. We explain Google's "trunk-based development" strategy and the support systems that structure workflow and keep Google's codebase healthy, including software for static analysis, code cleanup, and streamlined code review.

The descriptions of the signs mostly follow Gardiner's publications. However, an attempt was made to achieve a greater consistency.

1–10 (3209)   Next >   Last >|