So far I generally find myself in a middle ground of sorts.

Diaspora* makes for a social environment that works pretty well, although I think a touch behind what G+ became. But to be fair most of the things I miss about G+, other than the people, were things that took time for the platform to develop.

Where I find myself most frustrated tends to be the software.

You see: most of my time on such things is centered around my Android tablet. Dandelion is about as much as any Diaspora client could be but I find the performance lacking, as a consequence of it being forced to function as a web based app instead of a native client.

Such that I am almost better off going back to keeping my journal on a blogger platform and automating sharing posts to Pluspora, where there is more social life. This my recent experiments doing RSS -> D*.

But of course that leaves another open loop. Before moving to G+, I had used Blogger. Before that I used Live Journal. But in the years since moving from Blogger to Google Plus not much as changed. Rather Blogger has mostly remained fixed in time and others like WordPress have marched on. Creating a sort of software want redux.

Difference is that it is easier to pull a journal migration or write a custom bot bridge than it is to pull a better Diaspora client out of my wazoo.

Test 2

Using a different client app that sucks less.

Also want to see how the formatting comes through my RSS feed and into the post bots conversion.

Here’s a link to Captain’s Log Supplemental as it stood before G+.

Some bold, italic, underline, and strike through formatting.

  • Bullet
  • List

And

  1. Numbered
  2. List

Plus

A block quote.

And a little

Horizontal bar for good measure.

Hmm, I wonder. There are just so many possiblities of what can be done, and my brain can baloon with ideas fed off that. In the mean time, I know it’s most important to scratch the itches with the most value, first.

Off my operating environment, the more pressing lack is notes taking. Simplenote works but via Android, I seem to be in need of writing my own client (been a while since I’ve hit that part of my GitHub). One thing that might be of interest is some client side integration, of being able to mate Simplenote, Blogger, and G+ and apply a little meta-search magic.

Hmmm.

You know, this page isn’t as slow as I thought it would be on my tablet. I’m not sure I’d prefer it over a native client option though, that does better than Google’s own offering.

At some point, I think I need to bust out AIDE :-).

So my mother calls me at work for something “Important” that probably fits in the 3/10 or 5/10 buckets, which is a blocking I/O event when you’re trying to debug code, eh? This is something anyone out of grade school should understand by now:

  1. Walking in
    • In addition to calling (see below), blocks visual input if face is turned to look at you.
  2. Calling (E.g. phones, Skype calls, etc).
    • Blocks other tasks requiring conversational or non-automated mental function.
    • Suitable for urgent matters that demand a response time under five seconds.
    • Signal and local state issues may get you ignored to /dev/voicemail.
  3. Rolling conversations (E.g. from a desk away, over TeamSpeak, etc).
    1. Blocks either tasks requiring conversational output (responding) and reading comprehension (listening).
    2. Suitable for when a response time under 15 seconds is okay and you can repeat something.
  4. Messaging (E.g. instant message, text/SMS message).
    1. Suitable for when response time under 5 minutes is ideal but not urgent.
    2. Temporarily blocks text output ON writing a response.
  5. Electronic post (E.g. e-mail, forum PM, etc).
    1. Suitable for when response time of 2-5 hours is okay.
    2. Minimal obstruction when response is uneeded and notification can wait.
  6. Snail Mail
    1. When it involves something you can’t digitize.
    2. Risk of being ignored is acceptable.
In most cases, “Response time” in the above can be replaced with time of notification as well, should you be conveying news. Case for 1: the building is on fire! Case for 5: you need to do ${task} tomorrow.
This is what it is like to deal with someone exercising grey matter. Programmers, copy readers, writers, etc.

It is a bit slow IMHO, but after a months of actually using the search key in Android, I can’t help but think this should be integrated into PC’s as well.

Or at least, I find it rather useful when mated with Android apps that can make their data searchable 🙂

Tales from the debugging session: I hate you

This week, I finally wrapped up an annoying bug that basically is a heisenbug at heart, that pretty much lead me to use shotgun debugging to trap the problem, and once I found it’s control flow, I stimulated it with something like this:



try {

    // block of code under test

} catch(ugh) {

    alert("I hate you!");

}

And gradually reduced the block size until I found where the code was, fixed it to not make Firefox 9.0.1 croak at the old code. Then I committed it and marked the bug accordingly in our tracker.

Then when I was shutting down to leave work, my team leader IM’s me….oopsie, it turns out that I forgot to remove my “Affection” for Mozilla before commiting! I’m really glad that my boss has a sense of humour, and I think I was laughing for at least 45 minutes……lol.

Now that I’ve got a dock for my ASUS Transformer Prime, and have had my tablet for a good while, I think I might do a review, perhaps even against the original Transformer, which has served me so well….even while being battle damaged so to speak, lol.