Friday, June 27, 2008

Network book cover is up


A total surprise for me. Cambridge still hasn't updated the book title on the page, but the proper book title is on the cover. I'm just delighted to see it coming out, and incidentally I like that the typeface and bars make it look a little similar to my other book's cover.

Here they are together, my two books, just hanging out.

Thursday, June 26, 2008

Microsoft to buy Powerset, or Yahoo Search, or something

People are all excited about the rumor that Microsoft will buy Powerset to beef up MS Live Search. Of course, this succeeds the rumor that MS is back in talks with Yahoo to buy it or its search business. My sense is that the Powerset deal is a possibility, but MS is floating it now to keep Yahoo's stock from rising on speculation.

I remember this pulp cover for 1984

Cory Doctorow just reposted an excited blog post about a pulp fiction-style cover for George Orwell's 1984.(Click through to see the lurid cover.) The blog's author enthuses: "Significant is the artwork and over-the-top copy on the back, which is quite different from almost every other edition of this novel that I've seen."

The funny thing is that this is the version of 1984 we had when I was growing up. I think I read this thing when I was ten, and I remember feeling a little let down that the material was less exciting than the cover.

Tuesday, June 24, 2008

Reading :: Agile Project Management

Agile Project Management: How to Succeed in the Face of Changing Project Requirements
By Gary Chin


I've reviewed several project management books lately, and so far this is the best-of-breed in terms of defining agile project management, describing its need, and setting out a list of concepts for understanding it. The book isn't a set of heuristics and principles, nor is it a methodology, but it provides a solid basis for those other sorts of books.

Starting in the Preface, Chin argues that highly innovative businesses, especially those that push the limits of current technology, face challenges in discovery and planning that have not been encountered before. Such projects have inherent uncertainty, and face multiple paths, decision points, and iterations. Classic project management, he argues, is simply not set up for that sort of problem (p.vii). He ties this issue to the advent of the knowledge-based economy and acknowledges that although project management could be a key advantage for smaller businesses in this economy, classic PM is not well suited for helping them (p.ix).

It's not that classic PM is broken, he argues in Chapter 1, but it's been overextended. Agile project management is seen not as yet another extension, but a new foundational element (pp.2-3). The focus of agile PM moves from planning to execution -- a necessary move because
Agile PM Environment = [Uncertainty + Unique Expertise] + Speed (p.3)
or, in other words, the agile PM environment involves specialized problem solving that has not been done before, at the edge of experience, with rapid development. It's for startups in particular. Think in terms of software development, but also other lightweight tech-heavy development such as search engine optimization, social networking, and social media marketing. Organizations functioning in this space have "gurus" rather than interchangeable resources, working on problems that change from day to day, opportunistically incorporating new technologies to accommodate a rapidly shifting environment with both internal and external uncertainties. In contrast, classic project management assumes familiar problems, interchangeable expertise, unchanging objectives, and minimized internal and external uncertainty -- all signs of more mature industries such as construction.

I've discussed emergent organizational structures such as networks, federations and coworking on this blog. Chin doesn't quite get there -- he is still envisioning single organizations, multiple organizations, and single companies within multiple organizations (pp.17-20). Yet he edges closer to a federation understanding in Chapter 3, when he argues that in smaller companies, projects are the business (p.22) -- that is, a single project might be the central activity of the startup. In such an environment, classic PM, with its emphasis on project boxes that cut across silos, is not wholly applicable (p.25). Naturally, a project-driven organization is better suited to agile project environments (p.33).

In agile spaces, Chin argues, teams need to be boundary-crossers in order to solve new, multidimensional problems (p.43). Agile decision-making must be decentralized as well, pushed down to the level of the local team when possible (p.46); it is rarely handled through formal authority, most frequently through personal credibility established during the project (p.69). "The agile project operates in an atmosphere of high interactivity, boundary crossing, and multiple simultaneous pathways," he adds (p.79), which is to say (in my terms) that agile PM is a result of splicing dissimilar activities. It's not surprising (to me) that he points to telecommuters as good candidates for agile projects (p.94).

Chin goes on to offer some heuristics and practical approaches to implementing agile PM. But the real value in this book is Chin's sharp eye for the connections between classic and agile PM, grounded in the differences among organizations, industries, uncertainty, speed, and expertise. It's a great book for getting an overview of agile PM rationale.

Reading :: Managing Agile Projects

Managing Agile Projects
By Sanjiv Augustine


In my ongoing quest to read about project management and its permutations, I picked up Augustine's Managing Agile Projects. This book is focused on software development projects, as much of the agile literature is, but provides principles that could be more broadly abstracted. Like other books along these lines, this one takes pains to separate its brand of project management from more traditional, PMBOK-based project management.

The author draws heavily from agile programming and its variants (eXtreme Programming, Scrum, FD). But he also draws from a broad set of other concepts and frameworks, and the result is sometimes a grab bag of theories and concepts: complexity theory, memes (as cultural DNA), game theory, mental models, and communities of practice all make a showing without much to tie them together. But this book really isn't a theory book -- it's more about a set of organizing principles put forth as a compact or a constitution for governing team interactions. Augustine introduces this notion from the beginning with a clarifying "fable" based on an actual shift from traditional to agile project management (Ch.1).

Essentially, agile project management as it is described here consists of the following principles:
  • foster alignment and cooperation
  • encourage emergence and self-organization
  • institute learning and adaptation (p.25).
Complementing these are the following practices:
  • organic teams (small, flexible, composed of generalizing specialists)
  • guiding vision (keeping the team aligned with the same "mental model" or "commander's intent")
  • simple rules (generative process rules that can result in emergent organized behavior)
  • open information (vs. information kept in silos)
  • light touch (fostering emergent control rather than heavy-handed rules)
  • adaptive leadership (continuously monitoring, learning, and adapting) (pp.26-29)
The author lists certain core values for agile project managers:
  • trust
  • collaboration
  • learning
  • courage (pp.38-39)
The rest of the book elaborates these principles, practices, and values and supplies heuristics for implementing them. Overall, these are well done, with clear guidelines and relationships. But, I hasten to add, the approach really does assume strong management backing to push through this compact, even though the end result is to get everyone else on board. Also, the approach is meant for larger organizations working on large software projects, and may not be appropriate for other industries -- too variable for longer-term manufacturing projects, too heavy-handed for smaller, lighter organizations with short engagements.

Monday, June 23, 2008

Plurk has third-party updating available via HelloTxt

... along with several other services. Have not tried it yet, but this was one big obstacle to using Plurk. Perhaps I will set up an account and double-update for a bit.

HelloTxt - Help SMS Gateway

Friday, June 20, 2008

How are people reaching this blog?

The answer, according to Google Analytics, is surprising to me. The top referring site is Google Images, probably because I have a couple of images such as one of John Paul Jones playing a many-necked mandolin. But the next few referring sites are:

2. twitter.com
3. apps.facebook.com
4. google.com
5. friendfeed.com
6. locus.cwrl.utexas.edu (my homepage)
7. stc-austin.org (The Austin chapter of the Society for Technical Communication)

5-7 are tied. 2, 3, and 5 are different aspects of my lifestream; people are seeing the same information refracted through different services.

Reading :: The Rise of the Project Workforce

The Rise of the Project Workforce
By Rudolf Melik


I've begun trying to push past traditional project management literature to look at what is typically called "agile project management": project management for less hierarchical, flatter, typically smaller structures. In particular, I want to see what's out there for networked organizations that are distributed geospatially and temporally as well as organized in networks rather than silos or hierarchies.

Rudolf Melik's The Rise of the Project Workforce is in some ways a good place to start. Although the book is a bit too focused on a particular methodology for my purposes, its opening chapters frame the issue well and provide some good concepts and thoughts on the distinction.

Malik is deeply influenced by Thomas Friedman's The World is Flat (which I haven't read). Based on Friedman's description of a hierarchically "flat world," Melik says, "Today's business systems are simply not designed to plan, schedule, manage, audit, and optimize work that gets done in a flat world. ... More modern versions of business optimization tools such as enterprise resource planning (ERP), customer relationship management (CRM), and project management software want to impose a certain rigidity within business processes, and fail to address the dynamic interplay and constantly shifting relationship between projects and people, which occurs naturally in the flat world that characterizes today's businesses" (p.5). Malik's book attempts to move toward a project management footing that addresses these characteristics.

This footing is called "project workforce management," a solution that combines human capital management, project management, business process management, and cost/revenue accounting (p.9). Such a system aims to integrate components such as time and expense tracking, cost and revenue accounting, workforce planning, project planning, project process management, and analytics (p.13). The idea is to produce a system that provides "a common vantage point for all decision makers"; "real-time views of projects, resource groups, actual progress, and issues"; and "more accurate decision-making" (p.14).

The rest of the book describes such a system in nuts-and-bolts terms. Melik has obviously given these parts a lot of thought, and I don't have the expertise to evaluate them, but the described system is fairly intricate and appears to be aimed at larger organizations with cross-functional projects. That is, Melik appears to be supporting project management for global enterprises which are going through "flattening"; I'm more interested in smaller, more agile organizations.

Nevertheless, the book was helpful for me to conceptualize some of the issues I've been investigating, and should provide a good blueprint for those working in larger organizations.

No cameras, no big deal

House Rep. John Culberson (R, Tx) has been Twittering from the House floor in the name of transparency. It's pretty interesting, but this post really caught my eye:

"@maslowbeer We (Rs) had TV cameras in the Rules Comm hearing room - Pelosi took all the cameras out - I will start Qikking these meetings"

Qik is a service that allows you to stream video from your mobile phone in real time. It's been used extensively by tech industry folks such as Robert Scoble. But seeing it mentioned in this context is arresting because it highlights the ability for someone with a pocket-sized device to easily replace much larger chunks of infrastructure such as larger cameras plus multiperson camera crews.

I don't take a position on whether transparency is a good thing in this particular case. As a general principle, I think transparency is a good thing, but in practice it may make people reluctant to do the sort of sausage-grinding necessary to generate compromises. My sense is that the House will need to establish firm protocol to deal with acceptable mobile device use, and soon.

Twitter / johnculberson: @maslowbeer We (Rs) had TV ...

Thursday, June 19, 2008

Opera Mobile usage report is out

Who's browsing the mobile web? Mostly males 18-27. I'm among the mere 4.4% of users 38-47 years old. Some interesting variation by country too.

Mobile Browsing Report

Monday, June 16, 2008

GDocs torpedoes Yep

Well, that's one possible implication. Yep is OSX software billed by some as "iTunes for your PDFs." It scans your hard drive, finds PDFs, and puts them in one searchable, tagged interface. I used it for a while, but was unimpressed with the tagging and search functions, so I just use Quicksilver now.

But today GDocs announced PDF support. As in, you can upload PDFs. I just tried it and it works very well. You can't edit the PDFs -- yet. But you can upload and search them, another differentiator with MS Office.

Google Docs Get PDF Support
Blogged with the Flock Browser

Reading :: A Guide to the Project Management Body of Knowledge

A Guide to the Project Management Body of Knowledge
by William R. Duncan


A Guide to the Project Management Body of Knowledge, also known as the PMBOK Guide, is the frequently cited guide developed by the Project Management Institute Standards Committee. This edition was published in 1996 and supersedes PMI's Project Management Body of Knowledge (PMBOK); the third edition, which I believe is the most current one, was published in 2004.

The PMBOK guide aims to set out the principles of project management so that this young field can establish standards. To that purpose, it is divided into the following sections:
I. The Project Management Framework
II. The Project Management Knowledge Areas
III. Appendices (which contain information on processes, additional sources, and a summary among other things)
IV. Glossary and Index
In other words, the PMBOK guide is definitely on the reference side, giving an overview of the basics of project management, an overview that should be supplemented with other texts as well as specialization in one's own content area and organizational structure. It's a 50,000 foot view. And as such, it's quite valuable for anyone who wants that overview. But it also introduces challenges for anyone who needs a closer view.

So, for instance, the PMBOK guide is especially valuable when defining project management as "the application of knowledge, skills, tools, and techniques to project activities in order to meet or exceed stakeholder needs and expectations from a project" (p.6), and when explaining basic concepts such as the difference between projects and operations (p.4). It also diagrams the knowledge areas and processes of project management (p.7) and explains what stakeholders might be involved in the project (p.15).

In one really valuable part of the PMBOK guide, the different types of organizational structures are described:
  • Functional: hierarchies in which staff are organized by specialty and have distinct superiors (p.18).
  • Projectized: focused almost entirely on projects, with relatively independent project managers drawing on resources across the organization rather than siloed into functional areas (p.20).
  • Matrix: a blend of the functional and projectized organizational structures (p.20).
The PMBOK guide is geared toward supporting projects across the two extremes of functional and projectized organizational structures. However, as I've discussed elsewhere, the projectized organizational structure is not an extreme: we are starting to see much looser and more distributed organizational structures such as federations and coworking as well as (arguably) agile organizations. The PMBOK guide, with its emphasis on processes and structures, is not well positioned to be extended to these looser organizations. More thoughts on this point as I continue to read the project management literature.

T-Mobile Plans to Release Android Phones in July? - Google Android Mobile Phone

Thanks to the good people at Filtrbox, I've been keeping up with interesting Google Android news. Today's unconfirmed rumor is that T-Mobile will bring an Android phone to market as soon as next month.

T-Mobile Plans to Release Android Phones in July? - Google Android Mobile Phone
Blogged with the Flock Browser

Thursday, June 12, 2008

LiquidPlanner - fuzzy project manager

Like other project management systems such as Basecamp, but built to deal with uncertainty and contingencies.  

LiquidPlanner: Project Management That Deals With Uncertainty
Blogged with the Flock Browser

Microsoft Develops Workstreaming

Although that's not the term they use:
The system is said to resemble Facebook, but with a slightly less entertaining intention. Its goal is to let employees stay up-to-date with industry news as well as their own colleagues’ work and progress. It even has a feature that can let you see when someone has created or updated a document — something that may give bosses an added way to monitor progress.
But also a way for loose teams to collaboratively check status, something that is currently done using IM, Twitter, project blogs, RescueTime, and various other services in different work contexts.
Microsoft Develops Corporate Social Networking Tool
Blogged with the Flock Browser

iPhone 3G: The view from Singapore

Unimpressed.

iPhone is Next-Gen? You got to be kidding me! at Weikiat.NET
Blogged with the Flock Browser

The Austin Coworking Scene, Part 2: Conjunctured

As mentioned in a previous post, I have been thinking in terms of attenuated work organization for a while, ever since reading Zuboff and Maxmin's The Support Economy. That book led me to read a lot on the information economy as well as related subjects. Some of them obviously related, such as new economy rhetoric, management theory, and communication technologies. Others were not so obviously related, such as asymmetric warfare, education theory, and lots of postmodernist and amodernist theory.

What I've been reading has led me to believe that the information economy is pushing work organization away from hierarchies and toward recombinant networks in which individuals reach across trade, field, discipline, and organizational boundaries to accomplish specific projects. This change is abetted by newly ubiquitous information technologies and is happening even in established organizations, as I've discussed in the upcoming book Network and in my recent TCQ special issue on distributed work. But it's happening even more quickly in smaller, lighter sectors such as small business-to-business services: think graphic design, web design, advertising campaigns, and consulting. In these sectors, since engagements are quite limited in time and in focus, it's possible for Zuboff and Maxmin's "federations" of contractors and subcontractors to coalesce, accomplish a project, and disperse at the end of the project. Such an organizational structure is quite networked, involving attenuated ties and constant boundary-crossing across fields, trades, disciplines and organizations. The falling costs of portable computers, broadband, and mobile telecommunications have meant that such federations can operate on very low overhead.

Some of the more interesting developments in communication-oriented software have come from these emerging federations. For instance, Basecamp was developed to help 37Signals manage their projects in consultation with clients. Google Docs, as I have argued elsewhere, is ideally suited for this sort of collaboration as well.

So it's not terribly surprising for me to see these federations coalescing and dispersing. What did surprise me when I ran across it a few months ago, and again as I revisited it recently, was Conjunctured. The company didn't appear to be a federation -- too stable -- but it certainly wasn't a hierarchical organization either. Was it something entirely new? A hybrid?

After a while, I did the most obvious thing. I asked. That is, I met separately with two members of Conjunctured to informally talk about the organization.

A caveat here: These meetings were not research, were not conducted via a research methodology, were not passed by a human subjects committee, and should be regarded as citizen journalism rather than research.

May 28: Cesar Torres
Cesar Torres was gracious enough to meet me at the coffee shop for an interview. An energetic 24-year-old, Cesar explained that he had recently graduated from UT with a marketing degree, although he was let in as a computer science major. Throughout college, he freelanced (over Craigslist) as well as interning at Apple. When he graduated, he faced the prospect of working at Apple or at a conventional advertising firm.

But he preferred creative control. He had interned at advertising agencies, and he thinks of them as a "big government" model: lots of overhead, layers between creative worker and customer. But technology replaces a lot of the overhead and infrastructure of the agency model: all the creative needs is a laptop and a mobile phone. So he decided to "flip the model."

Flipping a model as established as the agency model is hard. Conjunctured, he explained, is a moving target. The description on the website right now is a February statement, already a bit out of date. Currently, Conjunctured has two sides:

Agency. Conjunctured started in August 2007 with three others. They had begun working together in Jelly meetings and at Social Media Club. Together, they worked on a model of individual work + collaboration on projects that leverage their unique skills. And whereas a conventional agency takes too big a cut due to infrastructure, Conjunctured allows them to get freelancer wages.

Not only do they supply their own infrastructure (laptops, mobile phones) at low cost, they use free tools. Cesar describes this approach as learning to intertwine, learning to be efficient early adopters. The agency is an exercise in figuring out the value in social media and social connections.

Coworking space. Cesar went to SXSWi to talk to people about this model. Their advice was to get space. In fact, he met Julie Gomoll of LaunchpadCoworking.com, who is starting a coworking cafe with conference rooms. Gomoll's enterprise is high-end, catering to telecommuters at large companies. Space there goes for $15/hr.

Conjunctured decided to take this model and apply it to a more downscale market:
  • Walk-in: $15/day
  • Part-time: 3-4 days/wk $150-200
  • Full-time: 24/7 access, $250-400
So the space theoretically will pay for itself. This aspect of Conjunctured is not-for-profit. At the time of the interview, Conjunctured had made an offer for space 5 blocks east of I-35. They envisioned the coworking space as functioning as
  • incubator
  • recurring revenue
  • but 80%: network, be in environment with other creatives
Ideally, the space functions as an incubator. Cesar envisions a recurring 7-minute period in which everyone focuses on one project to improve it. Once a company outgrows the incubator, they buy a space next door. And the property is strategically placed near light rail. The space is a house, with the mentality being that of a family rather than a corporation.

Currently the agency model is on the back burner. They had a chicken and egg problem:
  • How do you run an agency without space?
  • How do you obtain space without revenue?
So the coworking space is the main focus right now; once it's nailed down, the agency model can take hold.

How do you handle long-term planning, I asked. He feels it will work itself out. Designers and developers naturally go into the coworking model, But he believes that it will also draw project managers. Meanwhile, Conjunctured's founders will work on that level too.

How does Conjunctured bill work, since it is not a company in the traditional sense? Currently, when one of Conjunctured's members is hired, it's as an individual. That individual hires others as consultants and sends them 1099s. That is, they hire each other as subcontractors and they can write each other off as a business expense. Which is to say that in this sense, Conjunctured closely resembles a federation, but more stable in that the relationships are tighter and meant to outlast the projects.

Conjunctured currently has a DBA and is in talks with a lawyer about becoming a LLC. They are not incorporating in near future.

Cesar was also nice enough to give me pointers to the Austin coworking scene, which is more extensive than I had realized.

About a week later, another Conjunctured member, John Erik Metcalfe, sent me a direct message on Twitter, suggesting we meet as well.

June 6: John Erik Metcalfe
It was raining on the morning of June 6, and as I rode the bus toward my appointment with John (in the same coffee shop), he direct-messaged me on Twitter, letting me know he would be a little late -- he had to go back and get his umbrella. That was fine with me, since I was engrossed in a project management text. I settled in the coffee shop, and soon John appeared.

He explained that he saw the Conjunctured model as white blood cells in the bloodstream. When a hostile organism appeared, white blood cells swarm it. Similarly, Conjunctured's coworkers swarm a project. (This, of course, reminds me of the swarming concept applied in asymmetric warfare.)

John's particular focus is the Startup District, the anticipated cluster of companies that will grow from the Conjunctured incubator. And networking -- not on a money level, he explained, but on the level of human engagement.

Conjunctured's processes, he explained, are based on scrum/agile programming. They're incremental. Dusty Reagan (also of Conjunctured and a software developer) brought this orientation to projects.

John was excited because Conjunctured was signing on space that day. The four founders would sign. And although individual people would be working in the coworking space, Conjunctured as a brand/agency would bring in work.

So here's how that works. Coworking people can work on Conjunctured projects up to 20 hours per week. John used the same metaphor that Cesar had used: Conjunctured is "small government," with low overhead and freelance wages that meant workers would be "making what they should." The rest of their time would be spent on their own projects.

The part of an agency that many contractors find uninteresting, he explained, "is client service." Conjunctured handles that part by obtaining clients, chunking out projects, and distributing the chunks to a flat structure of people.

Here's the project management process John described, based on scrum.

1) Conjunctured talks to the client and asks, "What is the project?" They get an explanation, then promise to "put it into our system." Each project is an opt-in project.

2) Conjunctured creates a Google Doc with the project description. It's shared with everyone. Coworkers opt into the project by adding text on the GDoc. If not enough people opt in, Conjunctured declines the project. (It's all about opt-in.) But if there are enough yesses, the project is a go.

(John envisions a Digg-style list for projects: The most popular float to the top. This system would serve to aggregate interest and priority.)

3) Conjunctured then meets with the client, along with appropriate coworkers. They ask questions to create large chunks of the project. For instance, a branding project might be chunked into an identity system, website, etc.

4) Conjunctured then goes back to the group and presents the chunks: "Here's what needs to be done. Check in to do them." Members use the GDocs spreadsheet for tasks and time estimates. One column, "Dusty's gut," is used for developer Dusty Reagan's time estimate; others comment on the estimates to refine them and produce a firmer estimate. (Notice that this functions as a market-type system with free bidding inside the organization.)

5) Based on the breakout, the project lead calculates total length (which is to say, reads the total at the bottom of the spreadsheet). A line for client service is added, automatically estimated as a ratio of the project total.

6) If the client agrees with the estimate, Conjunctured asks the opt-in members to break their chunks into detailed tasks with time estimates. These tasks can be parceled out and managed recursively: the task's owner can manage the individual tasks and get more opt-ins, meaning that someone could work on as little as two hours of the project. Doing this means that parts of the project can be subcontracted and managed at a very low level of granularity; think of it as a federation with subfederations.

It's an intriguing process. However, John pointed out that Conjunctured has done few projects so far with this method. He expects that it will continue to evolve and refine.

What if someone doesn't meet their commitment? John points to the Conjunctured Manifesto, which states that "The community should call out members who aren’t pulling their weight"; members can call someone out at any time and judge them openly within Conjunctured. He also envisions a reputation system. They have implemented an initial version of this reputation system which allows them to give stars to coworkers; eventually, he envisions a thumbs-up or thumbs-down ranking on any project.

This process has some resemblance to project management, but also many differences. John says that Conjunctured expects to work out project management eventually, via a software solution that lets members look at
  • the availability and reputation of available coworkers (a la eBay)
  • the popularity of given projects (a la Digg)
He points to actionitem.com -- being developed by a fellow Austinite -- as one possible way to go.

What does it all mean?
It would be easy to characterize this young, rapidly developing model as a case of idealism overdose. Certainly it faces some key challenges in terms of project management, scaling, stability, and sustainability. However, I see some really interesting things going on here that resonate with the sorts of trends Beniger and Malone have talked about, among others. In certain project- and campaign-oriented, limited-engagement sectors, such as graphic design, advertising, and web development, freelancing and sole proprietorships have thrived; people have gotten used to flexible hours, to working on projects that interest them, to choosing people with whom they would like to collaborate, and to supplying or foraging infrastructure. At the same time, social software has begun to support opt-in collaboration on a broader scale. Federation-like structures such as Conjunctured are an attempt to scale up the freelancing model to preserve these desirable characteristics while providing enough stability and planning structure to support longer engagements.

The details are still being worked out, and I expect the model to evolve considerably over the next year or so as Conjunctured continues to coalesce as an organization. In particular, the freelancing/sole proprietorship model tends to focus on the tactical, reactive level, and Conjunctured will have to focus more on the strategic level as it evolves, in order to maintain a steady stream of clients and a stable identity. One way to handle that would be to shed the ideals and become a traditional agency, but another harder way would be to continue to evolve tools and practices in line with the Manifesto.

In any case, the emerging organization is really interesting, and I expect to keep in contact with them to see how things develop.

One more time: Security by obscurity doesn't work

A federal judge who was recently on the short list for Supreme Court nominations recently discovered this:
Before the site was taken down, visitors to http://alex.kozinski.com were greeted with the message: "Ain't nothin' here. Y'all best be movin' on, compadre."

Only those who knew to type in the name of a subdirectory could see the content on the site, which also included some of Kozinski's essays and legal writings as well as music files and personal photos.
The music files were copyrighted. The photos included porn.

Alex Kozinski, 9th Circuit chief judge, posted sexually explicit matter on his website - Los Angeles Times
Blogged with the Flock Browser

Houston Congressman twitters from House floor

Just amazing. I wonder how many direct messages he'll get as the result of this post?  

techPresident – CrackBerry Addicts vs Twittering Sunlighters on the Floor of Congress
Blogged with the Flock Browser