Off the Top: Blogfodder Entries


July 7, 2018

The Sidebar is the New Back Bar

Back in the days when I had time to hangout with friends for drinks, many places had a “back bar” that was more quiet and private.

I haven’t been in the habit of posting here as much as I used to, but I still am putting things into Pinboard and somethings I flag with “linkfodder”, which is my relatively unique tag to pull out favorites. I use the API from Pinboard to pull the linkfodder tagged items into the sidebar here. Occasionally I annotate them and that is brought here as well. This sidebar mini blog feels sort of like the back bar, which is a little more quiet and calm and you can see some things of interest to me (if that is of interest to you) and track them down.



July 15, 2016

Breaking Radio Silence Again

It has been a while since I’ve posted here. I’m thinking I may go back to a daily update for a stretch to keep the blogging muscle limber and trained.

Personal InfoCloud Backlog too

Over on other blog, [http://www.personalinfocloud.com](Personal InfoCloud) I have had a few more recent posts, but I have a very long backlog of content for that space as well. I need to rewrite the intro to the latest post there, [http://www.personalinfocloud.com/blog/2016/6/20/team-roles-needed-for-social-software-projects](Team Roles Needed for Social Software Projects).

I also have a series there called [http://www.personalinfocloud.com/?category=Shift+Happened](Shift Happened) that I have at least 12 most posts that need to get written (edited, or more likely rewritten). The next two in the Shift Happened series are related to UX in enterprise software and services and the subject of Adaption. Both of these subjects could likely have more than one post each. The UX in enterprise needs a grounding / framing piece as many still think of UX as visual design and not things being designed for use (nor all the various roles and domains that make up successful UX design). The Adaption pieces need the framing of complexity and complex adaptive systems to get set as a footing, but also needs to frame how adaption works and enables being comfortable in an ever changing environment that we live in today. As well a focus on Adaptive Road Maps is needed as how one plans in an ever shifting and complex environment is needed when today’s road maps for the next 2 to 5 years are shot to pieces after a quarter or two. Having and maintaining a long focus on where a company or product is headed is really helpful, particularly when needing to understand foundation priorities needed for a long haul in a world were agile practices drive the day-to-day, but those agile practices are incredibly nearsighted and often discourage the long view (I’ve had a lot of work related discussions about this in the last 6 months or so as it is a common deep pain point for many).

Health

A common question is about health after the eColi issue in 2014 to early 2015. My health seems to be good. Getting through last winter’s holiday season had me on edge as I was partially expecting to fall ill again. Thankfully, I stayed healthy.



January 1, 2016

Happy New Year - 2016 Edition

Happy New Year!

I’m believing that 2016 will be a good year, possibly a quite good year. After 7 years of bumpy and 2015 off to a rough start on the health front it stayed rather calm.

I don’t make resolutions for the new year. It is a practice that always delayed good timing of starting new habits and efforts when they were better fits. The, “oh, I start doing this on on New Years” always seemed a bit odd when the moment something strikes you is a perfectly good moment to start down the path to improvement or something new.

This blog has been quiet for a while, far too long in fact. Last year when I was sick it disrupted a good stretch of posting on a nearly daily basis. I really would like to get back to that. I was planning to start back writing over the past couple weeks, but the schedule was a bit filled and chaotic.

Digging Through Digital History

This past year I did a long stretch working as expert witness on a social software case. The case was booted right before trial and decided for the defense (the side I was working with). In doing this I spent a lot of time digging back through the last 5 to 10 years of social software, web, enterprise information management, tagging / folksonomy, and communication. Having this blog at my disposal and my Personal InfoCloud blog were a great help as my practice of knocking out ideas, no matter how rough, proved a great asset. But, it also proved a bit problematic, as a lot of things I liked to were gone from the web. Great ideas of others that sparked something in me were toast. They were not even in the Ineternet Archive’s Wayback Machine. Fortunately, I have a personal archive of things in my DevonThink Pro repository on my laptop that I’ve been tucking thing of potential future interest into since 2005. I have over 50,000 objects tucked away in it and it takes up between 20GB to 30GB on my hard drive.

I have a much larger post brewing on this, which I need to write and I’ve promised quite a few others I would write. The big problem in all of this is there is a lot of good, if not great, thinking gone from the web. It is gone because domains names were not kept, a site changed and dropped old content, blogging platforms disappeared (or weren’t kept up), or people lost interest and just let everything go. The great thinking from the 90s that the web was going to be a repository for all human thinking with great search and archival properties, is pretty much B.S. The web is fragile and not so great at archiving for long stretches. I found HTML is good for capturing content, but PDF proved the best long term (10 years = long term) digital archive for search in DevonThink. The worst has been site with a lot of JavaScript not saved into PDF, but saved as a website. JavaScript is an utter disaster for archiving (I have a quite a few things I tucked away as recently as 18 months ago that are unreadable thanks to JavaScript (older practices and modifications which may be deemed security issues or other changes of mind have functional JavaScript stop working). The practice of putting everything on the web, which can mean putting application front ends and other contrivances up only are making the web far more fragile.

The best is still straight up HMTL and CSS and enhancing from there with JavaScript. The other recent disaster, which is JavaScript related, is infinite scroll and breaking distinct URLs and pages. Infinite scroll is great for its intended use, which is stringing crappy content in one long string so advertisers see many page views. It is manufacturing a false understanding that the content is valued and read. Infinite scroll has little value to a the person reading, other than if the rare case good content is strung together (most sites using infinite scroll do it because the content is rather poor and need to have some means of telling advertisers that they have good readership). For archival purposes most often capturing just the one page you care about gets 2 to 5 others along with it. Linking back to the content you care about many times will not get you back to the distinct article or page because that page doesn’t actually live anywhere. I can’t wait for this dim witted practice to end. The past 3 years or so of thinking I had an article / page of good content I could point to cleanly and archive cleanly was a fallacy if I was trying to archive in the playland of infinite scroll cruft.

Back to Writing Out Loud

This past year of trying to dig out the relatively recent past of 5 to 10 years with some attempts to go back farther reinforced the good (that may be putting it lightly) practice of writing out loud. In the past few years I have been writing a lot still. But, much of this writing has been in notes on my local machines, my own shared repositories that are available to my other devices, or in the past couple years Slack teams. I don’t tend to write short tight pieces as I tend to fill in the traces back to foundations for what I’m thinking and why. A few of the Slack teams (what Slack calls the top level cluster of people in their service) get some of these dumps. I may drop in a thousand or three words in a day across one to four teams, as I am either conveying information or working through an idea or explanation and writing my way through it (writing is more helpful than talking my way through it as I know somebody is taking notes I can refer back to).

A lot of the things I have dropped in not so public channels, nor easily findable again for my self (Slack is brilliantly searchable in a team, but not across teams). When I am thinking about it I will pull these brain dumps into my own notes system that is searchable. If they are well formed I mark them as blogfodder (with a tag as such or in a large outline of other like material) to do something with later. This “do something with later” hasn’t quite materialized as of yet.

Posting these writing out loud efforts in my blogs, and likely also into my Medium area as it has more constant eyes on it than my blogs these days. I tend to syndicate out finished pieces into LinkedIn as well, but LinkedIn isn’t quite the space for thinking out loud as it isn’t the thinking space that Medium or blogs have been and it doesn’t seem to be shifting that way.

Not only have my own resources been really helpful, but in digging through expert witness work I was finding blogs to be great sources for really good thinking (that is where really good thinking was done, this isn’t exactly the case now, unless you consider adding an infinitely redundant cat photo to a blog being really good thinking). A lot of things I find valuable still today are on blogs and people thinking out loud. I really enjoy David Weinberger, Jeremy Keith, and the return of Matt Webb to blogging. There are many others I read regularly (see my links page for more).



March 18, 2015

Blogfodder and Linkfodder

Not only do I have a blogfodder tag I use on my local drive and cross device idea repositories and writing spaces, but I have a linkfodder marker as well.

Blogfodder

Blogfodder are those things that are seeds of ideas for writing or are fleshed out, but not quite postable / publishable. As I wrote in Refinement can be a Hinderance I am trying to get back to my old pattern of writing regularly as a brain dump, which can drift to stream of consciousness (but, I find most of the things that inspire me to good thoughts and exploration are other’s expressions shared in a stream of consciousness manner). The heavy edit and reviews get in the way of thought and sharing, which often lead to interactions with others around those ideas. I am deeply missing that and have been for a few years, although I have had some great interactions the last 6 months or so.

I also use blogfodder as a tag for ideas and writing to easily search and aggregate the items, which I also keep track of in an outline in OmniOutliner. But, as soon as I have posted these I remove the blogfodder tag and use a “posted” tag and change the status in OmniOutliner to posted and place a link to the post.

Linkfodder

Linkfodder is a term I am using in bookmarking in Pinboard and other local applications. These started with the aim of being links I really want to share and bring back into the sidebar of this blog at vanderwal.net. I have also hoped to capture and write quick annotations for a week ending links of note post. That has yet to happen as I want to bring in all the months of prior linkfoddering.

I have been looking at Zeef to capture the feed from my Pinboard linkfodder page and use a Zeef widget in my blog sidebar. I have that running well on a test sight and may implement it soon here (it is a 5 minute task to do, but it is the “is it how I want to do it” question holding me back). In the past I used Delicious javascript, which the newest owners of Delicious gloriously broke in their great unknowing.

The Wrap

Both of these are helping filter and keep fleeting things more organized. And hopefully execution of these follows.


Previous Month

This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike License.