.comment-link {margin-left:.6em;} Searching for the Moon
My original blog - I have moved to http://shannonclark.wordpress.com so this remains only as an archive.
 
Archives
<< current
 

Searching for the Moon
by Shannon Clark
 

Friday, January 28, 2005


Thomas P.M. Barnett :: Weblog: Weekend Reading: Rule-Set Reset
Thomas P.M. Barnett :: Weblog: Weekend Reading: Rule-Set Reset

Thomas P.M. Barnett is one of the most important thinkers and now consultants worldwide on setting a new framework and way of thinking about the world. He, along with others, has just launched a monthly electronic newsletter to supplement his extensive and impressive blog, other writings, bestselling book and later this year a follow-up book. I first became aware of Dr. Barnett with his first article for Esquire article.

I hope, though it may be difficult, to get Dr. Barnett as a participant at MeshForum - his thinkings are very much influenced via looking at the world as a network, and he explictedly looks at the impact of "connectedness" vs. "disconectedness" and maps his Core to connected countries, and his Gap to disconnected ones.

1/28/2005 07:04:00 PM 0 comments
Live from Iraq?.Its the elections in High Definition on HDNet - Blog Maverick - www.blogmaverick.com
Live from Iraq?.Its the elections in High Definition on HDNet - Blog Maverick - www.blogmaverick.com

Mark Cuban's HDNet is experimenting with HD news feeds this weekend and is covering the Iraqi election.

I've left him a long comment with some suggestions about how he might expand on this experiment - by making the feed available online and/or via HD DVD's - and then encouraging (and supporting) people to edit it - in a variety of manners. I hope he at least responds to my suggestion - we'll see what happens next.

1/28/2005 04:01:00 PM 0 comments
Singing in the rain - remixed
This type of thing has beenlong predicted in Science Fiction but to see it for real... very very cool.

1/28/2005 02:35:00 PM 0 comments
ZackExley.com
ZackExley.com

My longish comment on Zackexley's new blog, which he opened with a very long letter to the new DNC chair has just be posted (he moderates his comments). My point is that the infrastructure stuff is all well and good, but without first a discussion about ideas - and a much simplier, easier to use one at that, all the technology in the world won't help the Democrats. (I'm an independent).

In looking at the other comments - I see my point supported - a lot of talk about "our values" and "mobilizing people" etc - but no very clear cut explanations as to what those values are. Just an assumption that they are well known - and in opposition to the enemy - Republicans. (leaving independants such as myself out of the discussion mostly).

I look forward to following the ongoing discussion and Zak's future posts - this recent one was noted as the first of 4.

1/28/2005 11:49:00 AM 0 comments

Thursday, January 27, 2005


Getting things done (my version)
Many of my friends swear by David Allen and indeed, one of these days I'll buy his book (and perhaps other products) and see the source for why they rave, but in the meantime, here's a report on what I've done this week as my own personal version of "getting things done".

To start, some raw numbers to get a handle of the scale I've been dealing with for the past few days.

  • Over 2.6 gigs of email (starting point was one file at 1.45 gb and one archive at about 1gb)
  • Over 8500 unread messages, just in the primary mail file and about 6000+ in the archives
  • Over 140 separate mail folders in the primary, starting with about 20 in the archive
  • just over 1300 messages in my inbox alone
  • 40+ rules applied to my mail folder
  • Nearly 900 messages flagged "Follow up"

Result (at the moment, still working on even further improvements and organization)

  • Three mail files down to 2.3gb. Primary - at 650mb, Archive - at 1.279gb, and Archive - sent mail - at 415mb (a few 100mb of mail deleted)
  • Primary mail folders - 71 folders under my inbox, 85 in the archives, 4 (2001-2004) in the sent mail archive
  • Unread mail in Primary down to 2475, in archives up to 8322 but still around 4000+ messages have been read and processed in the past few days.
  • nearly 15 new rules applied and older poorly implemented rules (which had been causing duplication of many messages sent to multiple mailing lists - via sending a copy of the message to each mailing list's folder) fixed
  • New saved searches (running Outlook 2003) created to manage MeshForum related correspondences that might be misfiled, as well as to better manage the files in the archive, modified important searches such as "Follow up" and "For your information" to display total messages, not unread messages.
  • Down to 304 messages flagged "follow up" - and this number keeps dropping as I do, in fact, follow up -have resolved literally hundreds of such emails in the past few days, some because the urgency has passed (past trip related emails etc), others by taking specific action(s).
  • Inbox down to 260 messages 30 messages - all less than 45 days old [updated 1/28 - down to 30 messages]

Some context here is important. I receive about 400 or more emails a day. Many (about 200-250 some days) are junk/spam and are correctly caught as such by Outlook. Of the rest, a portion are spams that go uncaught, but the majority are of interest to me.

I use rules to sort mailing list emails into folders specifically for that mailing list.

My primary view, most of the time, is the "Unread messages" search folder in Outlook 2003, which allows me to collapse all the unread messages from all folders in my inbox into one view, which I then sort so that the new messages are on the top of the screen. As I read a message, I file it or delete it - most of the time.

Besides my inbox which I try to keep for current pending matters as well as misc. items that don't have a specific home yet (which either get deleted or filed after I am finished with them - ideally at least) I use the following folders heavily:

Clients/Potentials - where I put correspondence about possible deals, partners or projects. Once a project is started I make a subfolder of Clients for that client and then file all emails about that project into that folder

MeshForum - where I file all messages about MeshForum (and where any emails to shannon at meshforum go, as well as where all messages to meshforum related mailing lists)

Personal - where I file most personal emails from friends and items such as registrations

Vendors - catchall bin for emails from somewhat random companies. Companies I have a relationship with (such as IBM) get their own subfolder of vendors

Articles - catch all where I put articles that are worth retaining for future searches, but are not likely to be specifically actionable or frequently referenced

Useful Articles - where I store the much rarer articles I get which I know I will read in detail, follow the links, forward, and refer back to. Springwise and Trendwatching are two of the very few subscriptions I receive that go into this folder every month - though only after I have read the latest writing in detail

Overall, the process, while painful and very time consuming, has also been very valuable and useful. When I finish, likely this weekend, I'll have caught up on 2004's messages, have much less "pending" items, and have a much more smoothly running mailbox.

Any suggestions? Any similar tales of inbox management? Any alternative systems you practice?


1/27/2005 07:49:00 PM 1 comments

Wednesday, January 26, 2005


IBM Receives Patent for Using Regular Expressions to Extract Information from Documents
IBM Receives Patent for Using Regular Expressions to Extract Information from Documents

An example of a patent that should be, I think, overturned. I suspect I may, myself, have prior art to invalidate it. And that I have read and used numerous examples of prior art from published papers that should also invalidate it.

1/26/2005 12:20:00 PM 0 comments
Joi Ito's Web: WEF meeting in Davos
Joi Ito's Web: WEF meeting in Davos

I extended an invite to Joi Ito via a comment on his blog for him to attend MeshForum May 1-3, 2005 here in Chicago. Hopefully he'll be able to make it. If you are interested in attending, follow the link. Email me for a special discount (or leave a comment).

1/26/2005 02:18:00 AM 0 comments
IETF Standard for URI
Published just this month was the IETF standard for URI.

This is very important. Very, very few "standards" make it all the way to IETF standard status. The URI standard is a crucial and compelling one for the Internet as a whole. Having worked in the past on an IETF standard (actually multiple draft standards around calendaring) I have an inkling of how difficult and time consuming the process towards full standard is. Not sure when I'll have time to read the full document, but I am actually looking forward to doing so.

1/26/2005 12:36:00 AM 0 comments
McGee on Consulting
Jim McGee on Consulting is an article I need to read carefully and follow the links and read them carefully. After I put out a few fires, the rest of this month and next will be spent in sales mode - for MeshForum and for JigZaw as I do that, I'll have to watch that I do indeed get my expertise used, and used well.

1/26/2005 12:24:00 AM 0 comments

Monday, January 24, 2005


Readings - January 15-21, 2005
Last week I read, but not at a very heavy pace. Here's my notes from the week. Also note that I read the first quarter of Dispossessed, will probably finish it later this week.

Books and Magazines:
Sunday 1/16/2005 Finished Esquire February 2005 issue
Started New Yorker 1/17/2005 issue

Monday 1/17/2005
Finished New Yorker 1/17 issue
Started Wired Magazine, January 2005 issue

Tuesday 1/18/2005
Finished Wired Magazine, January 2005 issue. Lots of great articles and ideas sparked from this, including one about Amazon.com and assorted other great ideas.

Wednesday 1/19/2005
New Yorker - January 24 & 31, 2005. Just arrived today but had heard about some of the articles already, finished with about half of it.

Also received the newest issue of Granta 88: Mothers (am about 3 issues of Granta behind at the moment, have to decide if I will renew my subscription or not as this is my last issue)

Listened to many podcasts from IT Conversations - speeches by SAP's futurist, by the author of The Medici Effect and many others - very useful and inspiring discussions.

1/24/2005 08:24:00 PM 0 comments
Response to Auren Hoffman's commentors
In a recent post by Auren Hoffman on his personal Blog, Summation a commentor (using the handle 'Auren Hoffman is a prick' so take it with a large grain of salt) discussed a (mis)quote of Auren in the local SF paper.

If I understand the gist of Auren's misquoted quote correctly, I would have to agree with him (though he and I have somewhat different political affiliations - independent in my case leaning heavily liberal on social issues, Republican in Auren's case).

Auren's point is (I think) that instead of helping people get very low end, low opportunity jobs (at a very high cost for fairly minimal impact in terms of the results from various "training" programs), the city were to concentrate on helping minimize the restrictions on starting microbusinesses (which can and do grow into larger businesses). In most cities in the US it is a very complex and relatively costly process to establish a legal small businesses - especially if that business involves selling on the street (for example).

Here in Chicago, for example, to speak to cases I know about from long observation, the city has made it very difficult to legally perform music on the streets of Chicago and especially in the subways and Elevated trains of Chicago. As a result what had historically been a wonderful aspect of Chicago's streetscape is now mostly gone, limited to a handful of "official" spots in mostly high tourist traffic areas - and highly regulated by the city at that.

Likewise countless other small, low barriet to entry businesses throughout the city have been hit with more and heavier regulation. From food carts and street peddlers hit with many, complex regulations, to used CD shops being nearly driven out of businesses, to ethnic, historic groceries and butcher's shops also being heavily targeted by regulations and restrictions (no displaying of meats or sausages in the window or even mostly in the store out in the open - to take just one very silly IMHO case but one which has meant a severe drop in business for at least one historic butcher here in Chicago who smokes and makes his own very high quality meats and sausages).

Further examples are easy to find - the near impossibility of running an under-21 club in Chicago (whether or not drinking is allowed, the licensing for "public performances" are very expensive and complex, and trying to have mixed ages audiances a near impossibility). In short it is challenging here in Chicago for someone with even a small amount of resources, let alone next to no resources, to get started in business.

Yet at the same time it is that very process of supporting and harnessing entrepreneurial instints, the ability to find ways to eek out a profit, reinvest it, compound it, and build up businesses to perhaps any level desired which has historically been how people got out of poverty, and historically how one generation of imigrants raised the next generation of college students and taxpayers.

Consider the impact of the government of a city offering low-income residents an opportunity to take risks and try businesses that they come up with, without fear of, at least initially, needing to pay $1000's for a peddler's license etc. Personally I think the city as a whole would be a more vibrant and richer city.

Government strikes this bargain all the time - waiving some red tape and paperwork for small businesses and/or young businesses (OSHA requirements, Family Leave, etc).

1/24/2005 04:28:00 AM 0 comments

Sunday, January 23, 2005


Unbound Spiral: Skype + Bluetooth = Cordless
Stuart and I met for the first time at PopTech last fall. Then we remet here in Chicago Friday night for the Blogwalk dinner and Saturday for the BlogWalk itself.

Stuart was a very vocal proponant of Skype throughout Blogwalk. After exchanging emails with him earlier today, I looked over his blog and found the following post on one of the exact ideas I have had - getting a Bluetooth compatible headset, not for my cell phone (which doesn't currently have bluetooth, need to fix that someday) but for my laptop. Ideally stereo to listen to music and podcasts on, but with full Skype functionality for when I want to use Skype and/or have an incoming Skype call.

Unbound Spiral: Skype + Bluetooth = Cordless

Looks like it is not just possible, but well documented throughout the web. I know what I'll be adding to my toolkit in the very near future...

1/23/2005 02:49:00 AM 0 comments
Shannon on Flickr - Photo Sharing!#comment788748
Shannon on Flickr - Photo Sharing!#comment788748

A photo of me at Blogwalk 6.0 in Chicago.

1/23/2005 12:25:00 AM 0 comments
Flickr: Photos tagged with blogwalkchicago
Flickr: Photos tagged with blogwalkchicago

More on the Blogwalk tomorrow - but first, a link to the photos others (didn't bring my camera alas) took.

Overall I greatly enjoyed the Blogwalk - while blogging is not the focus of my business or consulting, I do think about and care about blogging (and more generally future trends in technology and especially network implications). I hope my contributions were useful over the course of the day, I think we most definitely sparked a lot of questions and our discussions were, I thought, very enjoyable.

Lots of little takeaways but like any, in my mind, great conference or gathering, my best "takeaways" have to do with who I met and the chance to spend time intensely with them for a day (and for some a day and a dinner). Whether or not we spend similar periods of intensive time together in the future, I know that we have a greater level of trust and connectiveness as a result of the conference, and I hope that I'll keep in touch with the other blogwalkers - at a minimum I know I'll be reading many of their blogs in the future (and hopefully a few of them will be reading here).

1/23/2005 12:19:00 AM 0 comments

Friday, January 21, 2005


What Happened to Google's Ten-Word Query Limit? -- ResearchBuzz, January 19, 2005
What Happened to Google's Ten-Word Query Limit? -- ResearchBuzz, January 19, 2005

Very good news for those of us, like myself, who from time to time need to do very long, complex queries - up till now Google's 10 word limit has been a severe limitation when trying to get precision. Looking forward to trying some experiments to test this at or near the upper limit, for example trying to build a fairly accurate "ego" search that gets most of my assorted posts/contributions or reference to me, while missing references to other "Shannon Clarks" out there as well as other results such as ones for Claude Shannon or about the Lewis & Clark expedition etc.

1/21/2005 10:36:00 PM 0 comments

Thursday, January 20, 2005


Getting Back To Work: A Personal Productivity Toolkit || kuro5hin.org
Getting Back To Work: A Personal Productivity Toolkit || kuro5hin.org

An article worth reading carefully - for anyone like myself who spends perhaps too much time online (or perhaps not enough, hard to say some weeks). Also at the end of the article is a link to a cool yet simple web app with a simple screen of "Get back to work" but with the added feature of allowing you to put in what you have to do, then indicate when you have done it - tracking the time it took you to do it via cookies.

I'll try it out later this afternoon after I relocate to where I'll be working from this afternoon (I tend to work from my home office in the mornings, from cafes or client's sites in the afternoon, cafes in the evening)

1/20/2005 12:25:00 PM 0 comments
Ask E.T.: Graphic of the Day: Computer and Human Chess Masters
Ask E.T.: Graphic of the Day: Computer and Human Chess Masters

I just posted a long reply to this great discusssion by Edward Tufte on chess illustrations. Tufte is one of the most useful teachers I have ever encountered, and I only took his one day seminar, years ago while he passed through Chicago. Still recall and use what I learned over 6 years later.

1/20/2005 12:42:00 AM 0 comments

Wednesday, January 19, 2005


Updates to MeshForum
A bunch of updates to MeshForum including the official announcement of our prices, date (May 1-3, 2005), venue, first sponsors, updated staff and volunteer needs and much more. Went over most of the website and updated the about MeshForum page, the overall look and feel and many other changes small (and some large).

Overall, the biggest news is that MeshForum will be 2 full days, Monday May 2nd and Tuesday May 3rd. On Sunday May 1st we will have an opening reception. The venue for the conference (and probably though it is not confirmed yet the reception) will be HotHouse a fantastic local Chicago institution which supports world music, creative art and great jazz.

The venue can accommodate up to 300 people, we are cutting off registration for MeshForum at 250 paying attendees. Pre-registration is $900 until February 15th with a $250 discount available to academics (Professors, staff or full time students). Watch your email for further news from me and a special offer (if you act quickly).

All attendees will get great things from our sponsors and we're hoping to have a bunch of fantastic surprises for everyone as well. In short, we are putting together all of the pieces which are needed to pull off a fantastic conference. Hope you can make it.

1/19/2005 02:00:00 AM 0 comments

Saturday, January 15, 2005


Books - week 2, 2005
This week read mostly magazines and websites, here's the list:

Jan 7th:
New Yorker - Jan 10th issue, finished
Software Development - special extra magazine on Eclipse
Reader - Pure Fiction issue from Dec 31st

Jan 10:
Barons - Dec 2004 issues
Alfred Hitchcock's Mystery Magazine - March 2005 issue - finished, not as good as it once was.
Started:
Basic Chess Endings by Ruben Fine - note, not a book I'll probably "read" in the usual sense
New York Review of Books - January issue

Jan 14:
Finished New York Review of Books - January Issue. Great article on the new MoMa, some other interesting articles but in general a somewhat disappointing issue - lots of politics, less culture and few books mentioned that were interesting enough to add to my list of books to look for/buy.

Started: Esquire - February 2005 issue. Greatly looking forward to reading Thomas P. M. Barnett's article on what Bush should do next, along with the other related articles. Noted that they specifically mention the Cristo Gates as one of the top things to do in February. We're planning on trying to make it to NYC in February in time to see the gates. Probably will also try to see the new MoMa while we are there as well.

Overall a fairly light reading week, did a lot of writing for many of the mailing lists I am on and on MeshForum related topics. This upcomming week I plan on finishing a number of the books on my shelves that are partially started, and get further caught up on my stack of magazines.

1/15/2005 01:11:00 PM 0 comments

Thursday, January 13, 2005


Lead21 Blog: Advice to Bush from one Harvard MBA to another
Lead21 Blog: Advice to Bush from one Harvard MBA to another

I offered a non-MBA's comment on this post to Lead21. I enjoy engaging with the authors of Lead21, though we differ in our politics, they are smart and articulate defenders of their point of view (most of the time) and at times we agree on some points. That said, I do think it is important to take them to task from time to time even when I agree with them - for example here where I questioned one of the lessons they said that MBA's learn - to never admit mistakes. A lesson I think is very wrong, but may also explain much about MBA's in the "real" world.

1/13/2005 12:14:00 PM 0 comments

Tuesday, January 11, 2005


Battle Lessons by Dan Baum of the New Yorker
Battle Lessons by Dan Baum

Read this. All of it. Shows both how the Army is using the web and technology to supplement/enhance training (via websites officers set up on their own but which have now been absorbed by the Pentagon officially) and a lot about the state of the war in Iraq.

Professionally I find the alteration of a very hierarchical organization such as the US Army by both a new generation of soldiers, the Internet, and modern communications to be a fascinating case study in the transformative power of connections. In the "old" Army connections were mostly formal and structured, with only occasional opportunities for across hierarchy interaction (and very limited while in battle - more while stationed at bases and/or during training). The Internet means that anyone with access (even retired or injured people etc) could, in theory, be in communication and offer support remotely to soldiers in the field. I especially found the story of the woman who had been promoted as it were "in the field" to a role she had not been trained for being able to within 30 minutes get emails from around the globe offering specific, actionable and useful help very encouraging.

As a researcher into AI I have long argued that though computers are and can be good - little can replace the power of the right people being engaged in a simple, potent manner - clearly these online communities are at least minimally serving a very real need.

1/11/2005 05:19:00 PM 0 comments
Blog Business Summit - Scoble vs. PR firms
Blog Business Summit

I added a comment to this discussion comparing Robert Scoble to the top 10 PR firms - my point being that while interesting the comparison is very flawed as the PR firm's business is not self-promotion but the promotion of their clients. That said, I did note that Edelman appears to be using the web very well - noting that they show up 4th in a google search on public relations

1/11/2005 08:39:00 AM 0 comments

Monday, January 10, 2005


Network analysis of a corporation
I am seeking a corporation (or multiple) to perform the following analysis. As this is a trial run, my rate would be competitive, all data would be cleansed and shared prior to any publication, other details negotiable (no rights to my research or work, but a right to have access, perhaps to use for internal purposes, external purposes negotiable).

The research would do the following analysis:

Look at the corporation's business and finances from a "pure" network perspective.

That is all parties and counterparties (vendors, partners, employees, governments, shareholders, etc) as nodes within a multi-dimensional, temporally bound network. The modeling would seek to model ALL transactions against time in terms of network transactions - mapping duration of link, value of link, and ALL parties impacted via the transaction(s).

From this initial set of data - which likely requires historic data from accounting systems as well as very likely other systems - I would then also extrapolate data and trends in terms of logical time units - based on the data, not preconcieved breakdowns. Additional analysis on the basis of more traditional timeframes such as quarters and the fiscal year would also be analyzed.

The main aspects of this would be to try to isolate and highlight the short and long term trends around - for example - specific lines of business, particular units/sales channels etc.

My thesis going into the research is that this type of analysis will very likely highlight opportunities, as well as anomolies. It may also help in mapping how complex organizations and partners are tied together.

My past research, into contracts for example, indicates that it is not uncommon at all for the actual transactions a corporation engages in to differ from how they are "supposed" to happen - payment/recievables do not occur in a timely manner, penalties are incurred (or conversely penalties that should be enforced whether on suppliers for mistakes/delays or on customers are not enforced etc.). All of these and more have a very real impact on the bottom line.

Further, many corporations - airlines perhaps being a prime example - while claiming to have a firm understanding of pricing - clearly do not at present manage to sell their services for more than they have costs (i.e. they are not currently profitable - or at least claim not to be). A better understanding of the timeline as well as inputs/outputs of the network around, say, a particular flight - over time - could be highly valuable and informative.

My thesis is that this study could help isolate and in a generalizeable manner explain the value a company such as Dell manages to achieve, but many other firms do not manage.

On one level it may appear an exercise in cash accounting - but I think there are key and vital differences in the approach, the process and the goals. My goal is not to provide an auditable set of accounts. Rather, my goal is to map out and highlight the network process via which the company opperates - placing it inside of a greater network of other firms, individuals, organizations and governments.

To start I would like to work with a small to midsized firm, or a very isolatable division of a large firm. As the details are worked out, especially around how the data will be manipulated and especially visualized, I would hope to work up to being capable of providing a rich analysis of a large firm, organization, or even government agency.

The process would be somewhat untraditional - this is not a "simple" case of spreadsheet modeling, yet it is also not a case of pure custom software development. rather it is a research and analysis process, as well as a test of the process of large scale data warehousing. I am envisioning a graphics process that would involve scaled data and which likely would involve animation to depict the passage of time - i.e. to show slices of data over time. Ideally the tools might allow for the tracing of a specific transaction and its effects over time across the nodes of the network being shown. (limited by the data and effects from transactions within the bounds of the dataset - effects from other external sources would initially not be modeled.)

To explain this - consider an employee's salary from the corporation. On the 15th of the month she receives a direct deposit of her salary. From a network perspective a few days prior to the 15th money from the corporation will have been transferred from one source of funds, probably a bank to another bank from which payroll would happen. From this account funds would then be transferred to the employee's bank, as well as into some holding accounts (perhaps) earmarked for various insurance providers and related taxes, as well as perhaps deposits into flexible spending accounts, HSA accounts, 401k accounts etc.

Each of these accounts while earmarked on the employee's paystub as occurring on the 15th might, from the perspective of the corporation be settled on a very different schedule - end of the month, quarterly, even yearly.

So, just one employee's salary could represent a web of connections and linkages being exercised on behalf of the corporation.

The employee, however, from the perspective of the corporation could also very easily incur a wealth of other costs (and hopefully in many cases generate income as well). These could include monthly licensing costs for tools and software used, expenses that are specifically expensed, obligations that are acrued (vacation, training dollars, education reimbursement, stock options, stock grants, bonuses etc.). Most employees occupy space in a facility somewhere owned by the corporation and at that facility use equipment and supplies, etc. In short understanding what a new employee represents to the corporation can be a complex task - I posit that by analyzing the corporation from a network perspective, this web can be made sense of and new relationships, anonomlies and interdependancies can be highlighted (and thus potentially acted upon).

Clearly this could be a big project.

If you are interested in discussing it further with me and/or have a firm whom you think would be interested in this type of analysis and consulting, I welcome your comments and/or emails.

1/10/2005 10:30:00 PM 0 comments

Friday, January 07, 2005


Many-to-Many: folksonomies + controlled vocabularies
Many-to-Many: folksonomies + controlled vocabularies

I posted a long comment to Clay's point about folksonomies and controlled vocabularies, mostly agreeing with his comments.

1/07/2005 11:18:00 PM 0 comments
Books - week 1, 2005
During 2005, I am going to try an experiment, not sure how successfully, to record every book and magazine I read during the year - from the whimsical to the serious and in between. I may from time to time also note articles or webpostings - generally when they are lengthy and significent enough that I print them out and/or file them for future reference.

At present I have a number of books I am working on, but for the year there are a few that I have recently finished and thus start this list with one of the first books I completed this year. (There may be one or two others, will check my shelves when I am home and may add a few to this list as a result - can't remember if I finished them this year or last...)

Books

1. Why Things Bite Back: Technology and the Revenge of Unintended Consequences by Edward Tenner

This book had been recommended to me by many people so I finally picked up a copy, after which it then sat on my shelf for quite a while. I started it in December of last year, though I did not bring it with me to India. I just finished it last night. While not without flaws and elements that are dated, Tenner's perspective on the unintended consequences of nearly all types of technology - from agriculture to software offers a challenging and fairly unique perspective, one that will inform my own work for years to come. This is, perhaps, the highest praise I can give a book - that it has changed and thus influenced my own perspective. While I have often thought about the unintended consequences of much of technology, having now read Tenner's book, I have new tools, perspectives and examples to reference and refer to in the future.

Magazines

This past week I read the following magazines and newspapers:

New Yorker (double fiction issue from last weeks of Dec and the Jan 3rd issue)
Software Development - last issue in Dec 2004, first of Jan 2005 - skimmed for articles on trends in development/technology of interest
Chicago Reader - Jan 6th issue
Red Eye - Jan 7th issue (local daily paper from the Chicago Tribune)
Barrons - first issue of 2005


Currently Reading

New Yorker - Jan 10th issue (mostly finished)
Critical Mass: How One Thing Leads to Another by Phillip Ball - started this in Nov of 2004, hope to finish it this weekend
Wired - January 2005 issue
CIO - Dec 15/Jan 1 issue
Esquire - January Issue (will purchase this weekend to read Thomas P. M. Barnett's article
The New York Review of Books - Jan 13th issue

I also have about 120 some books on my shelves waiting to be read and over 20 magazines from 2004 piling up (nearly a year's worth of Baselines, Queue, and CIO, a few Wired issues I didn't finish, and assort misc. others including two issues of Granta).

For a book club I will also be reading The Dispossessed by Ursala LeGuin which I am greatly looking forward to as though I own two copies (one which was signed to me by Ursala LeGuin) I haven't actually read it yet.

1/07/2005 09:29:00 PM 0 comments

Tuesday, January 04, 2005


The Red Couch: Competition...
The Red Couch: Competition...

I added a long comment to this post by Shel and Scoble.

1/04/2005 11:29:00 AM 0 comments

Monday, January 03, 2005


Projects for the New Year
Blogging my thoughts and ideas for new projects this year, these are rough outlines and rough ideas - they may be worth my time, they may not be, at the moment I am just trying to capture my thoughts and an outline of some ideas.

First, a series of articles/papers which I would like to write (co-authors, publishers, clients for test cases please contact me or comment here).

1. Summary of the processes I used to create Pieces - what I term the technology behind JigZaw's automatic data extraction technology (a demonstration is available, link will follow but it is embedded inside of a more complex calendaring application we wrote a few years ago). This combined techniques from about 100 different sources - including a few PhD and master theses and other published sources (and a few unpublished but available online sources). What the technology does is twofold. First, "chunk" semi-structured sources into their logical components and then based on a particular ontology (what we termed a defined set of definitions and rules about knowledge in a particular domain) extract data from the chunks that were identified and make it available in a machine parseable format (XML perhaps but also other formal data structures). The Chunking process could be driven in part by the particular data to be extracted (i.e. via a process that used the presense/absense of data in chunks to help determine how to select between alternative means of chunking a particular set of data. Advanced features which were planned but not yet developed would include machine learning to refine some particulars of the process and further data source manipulation to enhance the value and detail of the data we extracted - as well as improve the handling of some "edge" cases (specifically the first or last data present "chunk" in a source that held multiple examples of data to be extracted - at times these edge cases could cause a problem for our algorithms.

2. Write up my consulting process - specifically including two different processes which I follow. [UPDATED later in the evening on 1/3/2004 - forgot to include the second process 2b]

2a - Project scoping/specing process. Unlike many technical consultants, JigZaw approaches consulting projects without a pre-concieved packaged solution or specific vendor we prefer to work with and sell. Rather, our goal is to understand our client's business needs and then assist them in identifying the appropriate and deliverable solution to those needs. Towards this end we have a specific process we follow when specing out a project.

This process is to work with the client to create a set of requirements for the project - however we sort these requirements into three special categories. First - drop dead requirements - these are the requirements that make or break the success of the project - completion of all of these requirements defines a deliverable project, failure to deliver them means the project is incomplete. Second - what would be "nice to have" features/aspects of the project. These are features or aspects that while valuable, are not required for a deliverable project - generally this is a large category where a significent percentage of the "requirements" of a given project fall. And finally, third - fantasy requirements. Frequently these are overlooked and unmentioned in formal requirements gathering processes. These are what the client would dream that the project could do - here is where, as an outside consultant, we get to glimpse at long term impacts, at future goals, and the driving forces behind the project. Knowing these features more often than not allows the project to specified and developed in a way that often allows for the delivery of one or more of the "fantasy" elements with the initial delivery of the project. And in almost all cases, knowing them allows for the built into the project capacity and plan to achieve the long term, "fantasy" features.

Very often, these fantasy features are features that the client thinks are impossible, very difficult or very expensive to achieve. Very often the client is wrong in more than one way about these features - not uncommonly they may actually be cheaper and relatively easy to achieve.

Having all three categories defined prior to the start of a project, JigZaw is then able to work with the client on usually a fixed-fee and time basis. That is, we agree with the client to a quote for a particular time of delivery as well as on a specific fee and payment schedule. This timeline promises the delivery of the requirements (along with many, though not all of the "nice-to-haves" and if possible some or all of the "fantasy" elements). Often the schedule will include specific additional requirements from the client above and beyond payment - generally access to personal, data, systems as well as periodic participation in reviews, testing and eventually implementation. The quoted fee will usually include specific expenses as well as JigZaw's time investment (i.e. hardware purchases, software licenses, etc).

JigZaw usually retains ownership of the code we develop, though we provide a full and perpetual license to the client who pays for the development - alterntive payments/fees can be quoted if full, exclusive ownership of IP both code and/or patents is desired by the client.

This is not always, indeed usually, a simple or very quick process. Completing it requires a deep level of understanding on the part of the client and JigZaw, it also requires an investment of time and effort in the development of the requirements - depending on the time and scope this may be a for-fee service by JigZaw.

That said, it results is significently better software (or other deliverables - not unique to software development) than most other processes. When putting together JigZaw's quote JigZaw will take into account what we expect to require in terms of staff, outside resources and time - however we prefer to work on a fixed fee basis as this aligns our incentives directly with those of our client. If we complete the application early, we have time to add additional features or do further iterations of testing and enhancement. Within this framework we can then also enter into very clear discourses with the client as change occurs. Specifically testing of deliverables as well as changing business environments often result in changing requirements in the typical project. In the JigZaw framework, this then becomes a discussion of what has to give to meet the promised deadline - i.e. are other "must haves" now "nice to haves?" or can more money be spent on the project? (i.e. more time).

We work to make sure that it is an informed discussion with our client about the tradeoffs of adding new features/requirements to the project. Not uncommonly our project plans have built into them expectations of some aspects being determined during the course of the development process - but we still work to confine these in known ways that will not result in higher costs for either JigZaw or our client.

At the end of the day, our goal is to deliver very high business value to our clients - in a way that is profitable to JigZaw and which will allow us to continue to support and serve our clients in the future.

2b [updated evening 1/3/2004] JigZaw research/analysis/troublshooting process - aka "Smokejumping"

One of my personal favorite type of consulting engagements is to do what one client referred to as "smokejumping". That is, jump into what is often a failed application or project, quickly research and analyze it, identify what could be the problem and then set up a course of action to test, further analyze (if needed) and repair the problem. One project involved an application which had gone live on a Friday and failed and needed to be working by Monday. Friday evening I spent going over the source code, met with the developers on Saturday and worked through the code with them to identify the fault, had a solution by Sunday and the application was working on Monday.

For these engagements, whether a weekend or 6 months, I follow the same general process. First as much research as I can (and have time) - reading source code where available, seeing the application(s) in action, meeting with users, meeting with developers, reading over project documentation (if any). All with the goal of understanding three things: what the problem(s) are; what the application should be doing; what and how it was developed and designed (rarely matching what it should be doing).

With those three items understood, then I seek to understand what the constraints are in both the troubleshooting and resolution process - how time critical the issue is (generally if I have been brought it, there is a high degree of time criticality); what restrictions there are around any solution I propose - windows to make changes, usage requirements, hardware/software capacity/licensing; what the budget is as well as what the cost impact of the problem is (not always easy to determine but critical in helping evaluate and recommend the best course of action beyond hiring me to investigate the problem(s).

In troubleshooting what I typically do is seek to understand the baseline - how the application was working/being used or more often what was intended. Then I look for potential points of failure - in the process or system as a whole, in the data, in the use case(s), sometimes in the programming logic itself. Often I encounter situations with insufficient information or logs - sometimes it is possible to begin to generate those logs and use them for further analysis (though other times there is insufficient resources/time/capacity to do so. Not uncommonly a problem appears to be semi-random, however frequently by observing the users and talking with them before, during and after a problem occurs I am able to begin to significently narrow down the scope of the search for the cause - i.e. what parts of the application were being used, in what order, what should have been happening - which can then be contrasted with the logs of what did happen to the extent that they exist.

One of my somewhat random skills is often to pick out the disonate aspect within a pattern of data - a small comment from a user, an odd entry in an error log, a bit of source code that has flaws, etc. In smokejumping this skill is key - as important as anything is looking for potential causes to a problem.

3. Explore "network economics". This is likely more accurately explored in a book or perhaps in a series of long form studies/lengthy essays. In short, it is my theory of a new way of fundementally thinking about economics - not in terms of assets and money but in network terms of connections and links between nodes. Importantly this means modeling "value" in a very fundementally different way. It also requires a new way of looking at both macro and micro economics - whether analyzing the economics of a business or global finance. To explore this in detail likely requires me to write a series of detailed studies - arising from my fundemental observations are many further reexplorations of both classic and new economic issues. I strongly suspect that this new perspective does not render invalid or useless economics as a whole, though it likely results in some new avenues of analysis as well as new solutions to some old problems. It also very likely results in a very different set of math in the study of economics as the study of networks is a study of chaotic systems.

My thesis is that economics is networks - that everything can be understood in terms of networks, in terms of connections between nodes - from people to other people to nodes that are corporations, organizations or governments. Money itself can be modeled as a network link - from the holder of the note to the central government.

In this set of studies I will consider networks as being composed of "nodes" and links. Links are unidirectional from one node to another. A link can be modeled to include a measure - that is once a unit of some form is defined multiples can be modeled as a link of a particular "strength". Links also have a duration in time - most being short-lived, but others perhaps being of longer duration. Importantly if given a link from A to B. Node A knows of the link to B, while B may not - that is, a link can be anonymous (i.e. if the holder of doller bill has a link of unit 1 to the US Treasury, the US Treasury does not "know" of the holder - but the holder of that dollar does "know" of the link to the Treasury.

It then is the case that in "solving" a complex economic problem - the modeling involves networks over time with some links existing for long durations, while others exist only for a short while (generally during a transaction of some form). Using this form of modeling there is a theoretical difference between cash and credit transactions for example - especially if the "credit" involves third-parties.

Much more to explore, and I hope to do so in 2005.

4. Applying network models to AI and other challenges that I know. This is a bit less well formed, but it appears to me intuiatively that my interests in AI (specifically data extraction) and in Networks (generally as well as specifically in respect to economics) share related traits around the modeling of complex and very large data sets - and that the same techniques used in AI to avoid the non-full-set problem (that is how you handle clustering results into logical groups when you do not have the full set of all known data - i.e. most real world systems where new data sources are being created as fast or faster than the system can analyze them - and where you need to be able to avoid having to reanlyze all previous data in light of each new set of data that appears - otherwise the process of analyzing say 1000 documents and then each new document could easily become exponentially difficult as new documents are added.

5. My critique of the Semantic Web. While I am interested in the potential of some aspects of the Semantic Web, I also find that it is flawed in a fundemental way. This flaw is also all to common within the computer science world and even inside of the corporate development world. The flaw is the assumption that it is possible to know in the present what data (and specifically what metadata) will be needed to be known in the future. This may seem obviously impossible - but still most developers attempt it and it is inherent in many ways to the goals of the Semantic web. This impossibility I argue is philosophical in orgin - the future is inherently and literally unknowable.

In response I would argue for an alternative and perhaps simplier approach to data and especially to metadata. One that results in changes to how software is specified and developed and one that challenges many existing software development and standards initiatives. Howeve,r I also think that this simplier approach can and does result in deliverable applications, designed for growth and utility into the future, and designed in ways that build inherently into the applications an understanding of the users of the application in the present as well as into the future. Users being both humans and other applications and systems.

6. Ongoing reporting on and observations on the technology industry. Where I think things are, where things are going. Here I hope to build on my now over a decade of being an active and "power" user of the Internet (managing my own servers online since 1991). I strongly feel that lessons learned back in the "early" days of the Internet are being revisited and relearned, though on a growing scale, with each new "advancement" of the technology of the Internet. Muds and Mucks led to modern multiplayer games. Usenet and Gopher space to the web, Usenet and BBS communities as well as IRC channels to many of the aspects of online communities currently on the web and in mailing lists (where they have been for many years if not decades now).

I am a third-generation computer/technology person. My grandfather programmed some of the earliest computers while he was at Douglas, Rand Corporation and Aerospace corporation designing aircrafts and space components. My mother has been a programmer since the late 1960's - writing early systems to run railroads and universities (including an early experiment in ecommerce in the 1970's connecting student records to a university bookstore). I grew up reading flowcharts and taking programming classes since the third grade. For me, as for many more people into the future, technology and computers have been a core aspect of my world.

Besides these potential topics, I want to expand my consulting to start building up case studies for these and other studies. I want to help companies (and/or organizations) who can afford to hire me (and JigZaw) to apply and use technology in a value-added manner. I strongly feel that many, perhaps most, organizations do not use technology as effectively as they could. But that this is not, at its root, a case of technology not being capable - but rather it is a combination of often poor analysis and understanding of the underlying business needs and environment and poor implementation of the technology that is chosen - whether custom development, configuration/customization of packaged software or mostly "pure" packaged applications.

Most businesses can "solve" or address their business requirements and needs via an almost countless set of potential approaches. What is chosen is frequently determined by historical circumstances, inherited capacities and not in frequently less than skilled implementors and/or users.

What I can offer is an outside perspective on both business problems and the systems that have been implemented to address them (and/or I hope the systems that are being considered to address them). Working on a fixed fee basis (often, I hope and think would work well on a retainer basis) I can assist clients in evaluating what is currently in place as well as in addressing future requirements and needs.

1/03/2005 05:24:00 PM 0 comments

Sunday, January 02, 2005


On the starting of the new year
So, continueing my theme of a few posts back, here are some of the items I will be working on in the upcomming month and throughout 2005.

For January I have a number of goals.

1. Continue work for current clients, finishing one small project and hopefully continuing a larger project (as well as resolving current outstanding invoices from the last quarter of the year that remain unpaid at the moment).

2. Finalize details for MeshForum and ensure that it will happen in 2005, hopefully in April (in some form, probably around 100-150 people here in Chicago for at least one full and likely two days).

3. Send out Year End/Year Beginning email to my mailing list (about 700-800 business contacts). In this update, include upfront information registering for MeshForum and/or sponsoring it; information on JigZaw's retained services; and other opportunities.

4. In January and every other month of 2005 create a number of written pieces, at least one major piece a month. These will be published on one (or more) of the websites I manage and/or sold or published elsewhere - perhaps even in print. The goals here are both to get down in a formal form ideas and thoughts I have been having as well as to expand my exposure and that of MeshForum and JigZaw - hopefully leading to paying work.

5. Update ChiCon7, Hope Street Group and other websites which I manage on a volunteer basis.

6. Update JigZaw.com website (goal to have this done by the end of the first week in January). This is one of my highest priorities at the moment and will be my initial focus until paying work is available (and has to be updated prior to sending out my update email, likely towards the end of this week or next weekend)

7. Update my profile on ALL online networks where I am at least nominally active (LinkedIn, Ryze, Ecademy, Spoke, and a few others). Along with updating my profile, I should probably invest time on an ongoing basis to enhancing and maintaining my relationships with people on these forums.

8. Clean out 2004 from my mailbox - sending many messages to the archives. Goal is to have ZERO unread (i.e. undealt with in some manner) messages in my mailbox by the end of the month (currently have about 8000 messages that have not been read somewhere in my mailbox, with even more in the archives). As well I will be looking at what mailing lists I am on and unsubscribing from a number where I have not read them in over 6 months.

9. Likewise, by the end of the month and then on a regular at least once a month basis organize and clean up the piles throughout my house. This means going through the files and piles from 2004 - sorting and filing them and otherwise putting them into some semblance of order. Many bags of garbage are likley to result, a smaller bag of stuff to be shredded, some piles of things to be sold (goal also being to have them sold or donated by the end of January). It also means moving where many items are currently filed - making room for my business and personal files in file drawers, storing "stuff" in boxes which are more sensible for that purpose. I know this will make Julia very happy - and it will help clear cobwebs in my mind as well. Ideally this will be extended to my kitchen and other rooms to incorporate non-papers piles and clutter.

10. After going through my belongings - of all forms - replace (or at least get rid of) all that are outdated, broken, full of holes, and/or unused for more than a few years. Whether shoes, shirts, socks etc. An exception, perhaps, being made for many of my books - though not all.

11. Take care of my health. For January this means: Trip(s) to the dentist, a doctor's checkup post-India trip, continueing to lose weight in part via walking miles each week/eating less, getting a set of replacement glasses as India showed me the importance and potentially critical nature of my current lack of backup glasses.

12. After settling my finances from the recent India trip (and other trips in 2004) make a few further investments in our home and/or my lifestyle. These include: a CTA pass or at least auto-filled card; an iPod (probably 40gig or larger, perhaps an alternative player than the iPod, though it is very nice); more memory for my laptop; a flat screen monitor for home.

13. Start making 2005 conference and travel plans. Known events I (or we) may try to attend: WisCon in Madison Wis in May; MeshForum in Chicago in April (running this myself); Renaissance Weekend (perhaps again over Thanksgiving or alternitively in Monteray over Labor Day weekend); PopTech in Camden Maine Fall 2005?; PC Forum?; TED?; Aspen Institute? (July 4th weekend?); Gates exhibit in Central Park in NYC in February; possible trip to Brazil in mid-February; visiting family and friends in San Francisco (at least once, if my parents move there in 2005 - more than once); visiting Santa Barbara and my grandmother - also at least once in 2005; visiting NYC and my sister (probably at least in February, but likely other times as well; Washington DC - at least once this year to meet with many business and personal contacts; Seatle WA - have lots of contact there now, would be great to visit and network with them.

Along with this rather long list, I hope as well to attend a number of events and conferences here in Chicago. As well, if I can either get on the agenda and/or get compensation, I would like to attend other industry conferences such as DEMO.

This makes for a likely very busy January and rest of 2005. But as well I have a few additional goals for myself in 2005.

- find a way to finish my degree from the University of Chicago. This includes: paying all fines/fees; finishing (most likely) a BA thesis of some length - finding a professor to agree to read it and give it a grade.

- deciding professionally what my next steps are and what my goals are for the next 5 and 10 years. Will I remain running my own firm in some manner? (or firms?) Do I want to start other firms? Work for a large company? Work for an investment firm? what?

- deciding by the end of 2005 how much longer we will remain in Chicago. It is probable that by the end of Q1 2005 we will have a short term answer to whether or not we will be remaining in Chicago (i.e. what Julia's plans are and how my professional life is going). Given MeshForum, best case for us might be to move, if we do, sometime in late-Sprint (i.e. after April) but life rarely is ideal. This will also determine if and to what degree I make any investments into my home in 2005 (new closets, new appliances, new kitchen, new carpet, new flooring, new window treatments - etc)



1/02/2005 05:32:00 PM 0 comments
Summation: Is the Green Party anti-Semitic?
Summation: Is the Green Party anti-Semitic?

I posted the following long comment on this topic:

The other comments miss some troubling points - in looking at Green Party and
other alternative party activities and discourses, there is a very strong degree
of apparent anti-semitism, as well as a number of troubling associations. I base
this in large part on readings about anti-war protestors, of which the Green
Party was active.

For much more detailed and serious research into this
see:

http://www.tau.ac.il/Anti-Semitism/asw2003-4/france.htm (mostly
about France, but discusses the Green Party and other far-left parties more
broadly)

as well see:
http://www.tau.ac.il/Anti-Semitism/asw2003-4/general-analysis.htm for general
analysis

Also for a coherent discussion (amidst a not always coherent
one) on Antisemitism and the left see
http://listserv.utk.edu/cgi-bin/wa?A2=ind0311&L=rpa-list&T=0&F=&S=&P=18686
it is among the archives a mostly left leaning mailing list - found via google)

In essense there is an issue with antisemitism in the far left (and in
the far right). Not, to be sure, with everyone of the left, but a significent
number (and anecdotedly it seems to be increasing) of people on the left seem to
give higher priority to the Palistinian cause than to the right of Isreal to
exist.

I am ethnically if not religiously Jewish - so this is an issue
of some importance to me. The casual disregard for Israel that many on the left
seem to have, as well as the easy association with groups who are more virulent
in their support for the Palistian cause has the effect of turning me away from
the radical left (of course as a firm capitalist and political centrist, I'm not
exactly of the far left most of the time, though socially I tend to be in
agreement with the Left and even the "far" left)

Also, the line "no deep
truth has ever been found from statistical analysis" is hogwash. Quantum
mechanics - very much about the deep understanding of the universe is precisely
what happens when mechanical systems break down and statistical methods have to
be applied to understanding the universe. Quantum Mechanics has, in turn, lead
to the application of statistical methods and processes to many other fields -
offering the possibility of studying in the abstract systems that are impossible
to study mechanistically. Much of modern math and modern science is based on
statistics - it is how you deal with issus of probability, with issues of
unmeasurability, with complex, evolving, systems (and with the majority of
systems that attempts to measure also impact and change).

Further, if
you look at modern math and chaos theory it very much argues against the very
simple test that prediction of the future is the only measure of success of a
theory - many of the theories, in fact, argue that 100% "accurate", long term
predictions of the future are literally impossible. This does not mean that
understanding the future is impossible - but that since chance is involved as
well as lots of precurser states only approximate predictions can ever be made
(think weather forcasts, especially long range forcasts).


1/02/2005 05:06:00 PM 0 comments
 
This page is powered by Blogger.
Listed on BlogShares



Shannon John Clark (email me), b. 1974.

Male (to hold off the assumptions), currently in Chicago, IL.
I am active on many other forums and sites around the Internet. If I am online, feel free to Skype me.
You are also welcome to connect with me on Omidyar Networks on LinkedIn or Ryze.com and my blog on Ecademy or see more about me at MeshForum or my corporate site, JigZaw . I also maintain piecing IT together, as my corporate blog for JigZaw Inc.