QZ qz thoughts
a blog from Eli the Bearded
Tag search results for blather Page 1 of 4

Earliest Viable Poop


There are two dogs in this household, with very different personalities. Dog walks highlight one of the biggest contrasts.

One dog boldly in the sidewalk, one trying to get back home.

In this end-of-dog-walk shot, I've leashed the dogs to a pillar while I put the garbage bins away. Willie stands in the center of the sidewalk, staring into the distance. Hazel is trying to get back into the house.

Willie is super skilled at mental maps. He probably cannot get himself lost (although he has been known to run off). When we traveled, in pre-covid times, Willie could always be counted on to know when we were back "home" even if it was at night, somewhere he's been inside of only once for a few minutes, and approaching from a different direction than he had visited it before.

Hazel, two years after adoption, now seems to almost never go up the neighbors stairs. Hazel likes a walk from time to time. She is always happy to go on the morning walk (okay, not happy on rainy days), although she sometimes needs some help to start moving towards the door. But come evening, she'll pointedly run away from the leashes.

Willie is usually — rainy days are an exception — happy to walk for as long as I'd like to walk, and I'm quite willing to walk a long time. Our evening walks are often around half a mile, and sometimes longer than a mile. Morning walks, such as in the above photo are just around the block.

Which brings me to "Earliest Viable Poop".

In corporate nomenclature, the "minimum viable product" is the least advanced version of something a company thinks they can get money for. Companies like Apple don't generally release the minimum, but you can be sure a lot of apps in the Apple App Store are minimum viable. The idea behind such is "release early and use the revenue to pay for the development of more features."

Hazel clearly prefers to poop outside, but if the outside is unavailable or too unpleasant, she'll just use that bathmat next to the toilet. (That's what that room is for, right?) That's the Earliest Viable Poop for Hazel, the poop before the walk even starts. If she was releasing smart phone apps, they'd do one thing, and just barely do it all.

Willie, he will make it clear when he wants to go out and when he needs to to out. And once out, if only at the "wants" stage, he uses his mental map to make a good guess about the walk length. Even if it's not a route he's walked before, he is good at sensing if it is now the return trip. When he guesses that it is past half-way (or on a route he knows well, more than three-quarters) then he starts to really pay attention to the good spots. Even in rain, where he has what we call "efficient" walks, the earliest viable poop is a half block away (which is also about the distance of the last viable poop on a regular return trip). He takes his time to find the right spot, and has standards about the whole business. His threshold for minimum product would not be solely based on the minimum a low discerning customer would accept, but the minimum someone with real choice would consider.

I like to think about these things on long meditative walks with Willie. I know there is a place for the barely complete solution, but remember it's on par with pooping on the bathroom floor. Technology and scat have more in common than people think. A bunch of stuff goes in, gets digested, and then a release is made to the world, sometimes with a lot of care about how it lands, sometimes not.

We Work?


In September 2017 I was hired by a company that used Wework for office space. On the day I started, they had a tiny glass fishbowl meant to hold three people, and four people there. By October we had moved to a larger space on a different floor, meant for five people. It was a much nicer spot, with two openenable windows. (To the outside. Not just the glass walls with sliding doors on the other spot.)

The building was (is) on 2nd St in San Francisco's Soma (South of Market) neighborhood. An older six story building with a single elevator, wood stairs in the single internal staircase, and an exterior fire escape reachable through the sash window in one of the offices. I don't know if the people in that office were required to not lock their door, it is something I thought about in my time there.

I don't recall exactly when, but somewhere around December 2017 to February 2018 that company shut the Wework office down and I was expected to work from home. For about a month before then, I was usually the only person in the office. The San Francisco branch manager, Andrew, had been laid off in early December 2017, leaving just three employees in SF. And absent the manager insisting otherwise, the other two preferred to work from home.

On day one with that company, I had showed up at the Wework office and as part of signing in to meet Andrew, I had to provide an email address. I used my resume email address, since I didn't yet know what my new work address would be. Wework added that address to their building mailing list, and I got weekly announcements about things happening in the building. Emails with a text/plain part that was wildly different from the text/html part.

Those weekly newsletters stopped, without my intervention, when the company stopped the Wework lease. Until today. Some circa eighteen to twenty months later, I got one this morning. Still wildly different plain text and html parts, but also this time, a crazy From line. This from header is an address for a NYC (Hudson Yards) Wework office. Not exactly close to San Francisco.

From: WeWork Community team at 368 9th Ave <WE-US-58829@wework.com>

text/plain part:

What's happening at WeWork 156 2nd St this week?

(then three placeholder events all dated "June 28" with no year, eg

Exclusive 1 Title

Sunday, June 28 | 3:00 pm - 5:00pm | 19A

Enter the descriptive text for the exclusive item here. Please try to keep all descriptions 3 lines or shorter. If you don't need to include a link, you can delete the link below, but be careful, once deleted you can't undo it.

)

text/html part:

What's happening at WeWork 156 2nd St this week?

(then one event on August 13th and one on June 28th, both with actual details, but nothing happening in the week of August 3rd to 9th, 2020.)

I used the "list unsubscribe" link in the message headers (and got a confirmation of unsubscription just using lynx; always nice to see that websites work in text browsers).

But it prompted me to think about this company that had such a spectacular failure to IPO last year. An at-the-time description: 2019/9/23 Wework mess explained.

About a month after that story, Wework laid off 2,400 employees of 12,500 (according to SEC filings in June 2019). The news broke on Thanksgiving day: 2019/11/21 Wework lays off 2400.

Searching Reuters today, the most recent news story about Wework is almost a month old: Wework expects positive cash flow in 2021.

WeWork Executive Chairman Marcelo Claure said the office-sharing company was on course to have positive cash flow in 2021, a year earlier than a target the company set in February, the Financial Times reported on Sunday.

Claure, in an interview with the newspaper, said WeWork has seen strong demand for its office spaces since the start of the coronavirus outbreak.

The SoftBank-controlled company has also reduced its workforce by more than 8,000 people, renegotiated leases and sold off assets to reduce its cash burn and shed costs, FT said.

Eight thousand people is 64% of 12,500, assuming the lay-off count is from height of employment, and not some more recent smaller number. I'm a bit surprised that even with those third paragraph changes Wework still has hope. I'm also a bit surprised by the "strong demand" mentioned. In the face of massive work-from-home pushes, people want to work in glass cells?

As of today, there's vacancy for five people on the sixth floor of 156 2nd St, judging by the floor plan I think it's the same one I was in (looking at room 611; I don't remember the office numbers, just the floors). They want $5,250 a month for that. And there is a third floor vacancy for three people, for $2,710. It's not the one I was in, but adjacent.

Overall, I'm not sure 156 2nd St is showing "strong demand" based on the available units I can find. Maybe SF is not representative of that demand?

I really thought they'd be a goner when "quarantine" hit. Whatever the rental demand, whoever is doing their email newsletters seems surplus to requirements.

Podcasts


This is just one of those things I can't get into. I continually find that people want to have me listen to podcasts. I see blogs like Popehat essentially die with a podcast replacement, and people I read on Usenet and elsewhere say "listen to this podcast to find out about X or Y".

Such entreaties to move from reading to listening do not sit well with me. I don't mind listening to the radio while in the car or in my shed workshop. And sometimes what I'm listening to is a podcast on the radio, such as the excellent 99 Percent Invisible which I used to hear on KALW sometimes during driving-kids-to-school rides (but not in a long time now).

But listening to stuff when it is convenient and stopping what I am reading to go listen to stuff are two vastly different things. And it is pretty much never convenient to go download something and listen to it. I make an effort a couple of times a week to download and view videos I see people reference, but it is an effort and most youtube links will just get a glance at the title of the video, not a view.

My wife has listened to a few podcasts, some of them while I'm around, but she's not a big consumer of the format. I listened to an episode of Serial season one with her while we worked together in the kitchen. She finished the season, I didn't, she never continued with the later seasons.

It doesn't help that a lot of podcasts, like a lot of the content on youtube, seems to take a small amount of content and stretch it out over a long period of time. This is just the opposite of how I find most radio to be: longer stories tightly edited to fit in a shorter period of time. I suppose the appeal to some people is the more conversational nature of the content, but a conversation I can't participate in is not a strong draw for me.

With the written word, I can easily read slower or faster to pay closer attention to complicated bits or skim over filler. I can easily stop and reseach something mentioned to get more backstory or more details. In audio (or video) that is a lot more difficult. No exact spellings of things, for starters.

If something is only available in podcast form, it's basically content that will never, ever reach me. And no matter how much people say "you should listen to" I'm saddened by the choice of format.

So, Why Blosxom?


Although it was moderately popular when new, calling Blosxom a dead blog tool now is fairly accurate. No one is using it for new sites and many former power users — people dedicated and involved enough to write plugins &mhash; have abandoned the platform. So it probably bears answering "Why do I still want it?"

Here are some of the things Blosxom has going against it:

  1. No active development to lean on for community improvements.
  2. Somewhat simplistic hook model for plugins.
  3. Very rudimentary interpolation engine.
  4. Very easy to accidentally change posting time on posts.
  5. Without plugins, lacks many features considered standard now:
    • Comments
    • Post composer
    • Search
    • Search engine tools like sitemap support
    • Cookies for analytics, user preferences, and/or user logins

The main selling points Rael Dornfest had for Blosxom, as I remember it, where:

  1. Edit posts without a post composer.
  2. Import and export of posts is trivial since they are all just individual text files.
  3. Small code base with easy install on your own server.
  4. Simple to create plugins.

Most of those are not things I think people appreciate. GUI composers are very common these days, some more WYSIWYG then others, but having buttons for bolding, dialogs for links, etc, seems to be a thing people want. And maintaining code, installing things on an Internet server, that seems to to be things people don't want. You can get started in Tumblr in seconds after getting an email address and an Internet connection. Finding somewhere to install a Perl script, configure it to work with a web server, and then "how do you add images?" is too much.

So you've got deliberate features people don't care about, and drawbacks people will quickly notice. Blosxom is a hard sell these days.

But for me, it is what I have always done. My first forays into web page construction were done composed in vi, served by NCSA HTTPd, and viewed in Mosaic on university computers. From there, moved to a Unix shell account on an ISP by 1996. I had my own personal colocated server serving content on my own personal domain name by 1997, and was saturating a T1 at times by 1998. All of that original work was 100% my HTML and CGI coding. I wrote a CGI libary in 1999 that I still use for some personal projects.

For work, I've used blogging tools like Moveable Type and Wordpress. I've used content management systems like Plone and Drupal. I've stored content in Berkeley DB files, MySQL, and Postgres. I've worked with content accelerators like Varnish, Fastly (which is basically Varnish managed by someone else), and Akamai. I understand how and why to scale horizontally or vertically in Internet deployments.

I like coming back to the simplicity of knowing how every bit of the page gets transmitted from the first line of the HTTP request to the closing <BODY> tag in the HTML. That's what I get out of Blosxom. It is tiny and knowable. I have to do more work to enable things, but I know what that work is or how to find out. Until I did it for the sitemap tool last week, I had never actually built a sitemap, only parsed them for site scraping. It wasn't a hard task from deciding to do it and having it completed, even if it was a task that wouldn't be necessary with other tools..

Last month, May 2020, qaz.wtf moved 21,650,398,268 bytes in web content, that's without headers, an average of 8083 bytes per second all month long. Most of that (68.9%) was from the Unicode Toys which are configured to send compressed-on-the-fly 100% text html generated by CGI scripts I've 100% written. Second biggest top level item was /favicon.ico, sadly a binary file with a crappy name because Microsoft invented that concept. Third this blog (including images and CSS). If I were using Wordpress, I doubt the pages would be as small, and if I were using Medium the Javascript alone per page would be more than my blog HTML content put together.

I'm happy controlling it all and knowing where my byte budget goes.