In this episode, Charles and I talk out of our butts about Language Oriented Programming. We weren’t really familer with the concept, so we do a lot of arm-chair, actin’ like we’re smarties jib-jabbin’.
(This episode edited by Coté.)
A team of 100+ developers will generally develop a system so complicated it could only have been developed by a team of 100+ developers. —Darren Hobbs
Thanks go out again to Zane for letting us host the MP3s on the Liquid Labs servers.
(This episode edited by Coté.)
Feel free to send feedback to the comments below, or email either audio recordings or comments.
Thanks to Zane Rockenbaugh of Liquid Labs for hosting the MP3s for us with his mega-pipe to the ‘net.
(This episode was edited by Charles.)
Baus’s latest post got me thinking (as seems to happen daily) about good enough/indie programming. One problem, of course is marketing your services/software. Blogs, of course, work wonderfully if you can catch the right eye (see Whichard’s Blogging Theory).
To that end, it got me thinking that I should experiment with putting ads in the podcast. In addition to my pure curiosity at how it’d work out, there’s also some altruistic feelings of helping people out by giving them a chance to self-market.
So, unless Charles completely rebels at the idea, I’d invite anyone who wants to record a short 10-30 second ad to send the MP3 along.
The ad can be for anything: software your making, your website, services you have to offer, something about the company you work at, or just purely ego thing where you say “I rule!”. Really, think of it as more a free-form audio submission than an ad: ads would just be a sub-set of the acceptable submissions. The intent is to get the podcat linked into the rest of my online life: there’s no “hard links” in audio, but ads can serve as a sort of connection between the podcast and other nodes in the network.
If we should actually get any submissions, here’s how it’ll go and some more info:
So, any takers?
In this episode, we spend some time figuring out how commercial software could benefit from applying open source software development process(es) (as we understand them) to commercial software development. Along the way, of course, we try to figure out why such software doesn’t already do it that way, and what might prevent them from changing.
This one is what you might call the “shootin’ the shit” episode. Nonetheless, it’s all the excitement you’ve come to expect. In particular, you’ll want to check out the last 2 minutes for a real hoot-a-nany.
In a sort of pre-announce, pre-announce, Schmidt said:
The business is growing very quickly. We’ve added all these new features. It makes sense now to just keep adding more Google to the Google-in-a-box. So a reasonable expectation is that more and more of what’s on Google will be available in the blue box. And that’ll keep them busy for years. Because when you do that inside of a company, you have a higher level of security and privacy and all that stuff. … Imagine the evolution of this product line. It gets very interesting. Without pre-announcing anything, it seems like a no-brainer. You have lots of these things sitting around inside all these guys’ networks. Just think of the strategic value of that to Google.
That’d be exciting.
Back in Jan. or Feb., thanks to an internal weblog post I made and an eager to help out VP at work, we got ourselves a Google mini at work. So far, it’s been fantastic. People send in emails all the time saying how much they like and use the search. Having search behind the firewall, real, works-out-of-the-box search is a sort of major event for an intranet.
In a company as large as mine, there’s 100,000’s of web pages on the intranet (and 100,000’s more that I filter out of the search). With that many documents, and so many people, it’s difficult for people to add lots of helpful structure to all those URLs. Sure, there are plenty of systems that are highly structured (like project pages), but anyone/team can start up a web server, and often do, to host any sort of document. Worse, once you setup a structured page, it’s care and feeding often go by the way side: internal documents are always a much lower priority than external releases, i.e., money-makers.
From this, we might derive Coté’s Theory of Intranet Content, which goes: “you’ll never be able to structure everything effectively, so you might as well not try…very hard.” Therefore, unless you have search to layer over all that, it’s impossible to find what you want as quickly as you want. Thus, you need search. Q.E.D.
The Google mini has been the answer to that. Indeed, as the theory hint at, it almost makes all the structured sites (and apps we use to create them) kind of gratuitous. Just like GMail, Bloomba, or LookOut: once you add a search box to your email, all those folders aren’t really needed. (At best, folders are just 1-1 tags…but, you want 1-many tag-as-folders, of course.) Once you don’t need folders — because you have search — you don’t really need structure.
Of course, some structure is required to simply make creating and hosting content as easy as possible. You need a light content management system. So far, in my opinion, the answer to that light-CMS has is to use wiki’s and optionally,
weblogs*. With a wiki, creating a document is as easy as clicking “Edit This Page.” And a weblog has an inherent stream of content that’s a natural fit for people’s desire to get streams of content about relevant topics/people. Once you add search to that mix, you just about solve all your Enterprise intranet problems:
A few of those points are a bit forced, but I think you get the idea.
(As I’ve posted before, my experience with weblogs behind the fire-wall hasn’t been a huge success quantity wise, but quality wise it’s been great: if it weren’t for the weblogs, we wouldn’t have gotten the Google mini. It’s taken several years for the wiki to really become a core part of the groups I work in, and I suspect the same will be true for weblogs.)
Of course, what’s even more exciting about the above quote is the promise of having more Google apps available behind the firewall.
First off, we’d want GMail. No one really likes Outlook/Exchange, but everyone uses it (probably because everyone has those big Microsoft site licenses). As many people have noted, if you just throw in Calendaring that works as well as Outlook/Exchange, you’d have the full Email/Calendaring package that you need. And if the Google story continues to be the same, it’ll be both cheaper and more simple than Outlook/Exchange.
Google Groups would be another nice thing to have. There are tons of email lists behind the firewall, and if you use Outlook/Exchange, there’s really no good way to say, “put the archives of this lists on a web page so everyone can read/search them.” Not to mention the fact that once you reach those damn email storage quotas, you’re forced to start blowing away all those emails with all that important info in them that you’ve been trying to save.
And, of course, there’s Blogger.
Indeed, one could see that Google would simply create a “Collab Blue Box” that just loaded all those things together, with search. And, if they priced it as well as they do the Google mini, it’d sure be an intranet app killer. Even Outlook/Exchange if they could get a story that all the check-signers and IT guys believe in enough to make the switch.
As explained in this episode, we didn’t get together to record this week, so I put together several outtakes and (mostly) unused recordings we had. It’s all just funny-business, no real software this time. Thankfully for those who don’t too much doofusin’, it’s just under 14 minutes.
In addition to the DrunkAndRetired PodCast, we’re planning a whole new format and show with Zane, so look for that soon…along with next week’s DrunkAndRetired podcast episode, that’ll be zero seven (07).
This episode was edited by Coté.
In Episode 05 we talk about IDE’s, DSL’s, more code crap, and have plenty of refreshingly brillent banter. It’s what you’ve come to expect from the Coté & Charles DrunkAndRetired.com podcast.
Next week, we finally get back to discussing web applications with special (and future?) guest Zane.
This episode was edited by Mr. Charles Lowell.
But Coté is funny when writing so i figured i should check out Cote and Charles: He’s Burger, Web Apps Suck. Of course i didn’t listen to the first three episodes so who knows if they were any good. But episode 4 is spot on. Scatalogical humour always gets me right in the funny bone. Good work guys.
And, aparantly, we have a cliff-hanger to reveal what the ideal web app framework would be like. Jesus, the presure is killing me; you might spot me next in South Africa.
We always enjoy in-coming links here at DrunkAndRetired.com. They simply can’t be gin-ore’ed. So thanks to James. We’ll have to send you a shirt or something ;>
Here’s episode 04 of the Drunk & Retired podcast. As usual, it’s Charles (in Finland) and I (in Austin) talking about this and that.
The quality of this recording is much better as I finally figured out how to get Audio Hijack to record Skype without all that soundflower virtual cable crap. You just use a voice over effect, recording Skype, and you get not only Charle’s voice, but mine too. But, no one care about all that shit.
Have fun listenin’!
Stories like this are wonderful microcosm of any organization. A Los Alamos employee starts a public weblog, people start writing and sending in complaints, all the type A, “leaders” in congress get all upset and start saying things like, “this all a bunch of griping!” As always, little Ricky must be thinking, mom an dad just aren’t listening.
From this, we can draw a useful, tactical pattern for bottom up action in any organization: if you complain, those at the top will label you as a whiner, and use that as an ad hominem attack against all your efforts.
That is, when you’re trying to do hard bottom up change (as opposed to change coming down from the top, e.g., congress-people, CEOs, Popes, etc.), unless you’re supra-lucky, the people at the top will resist with any means possible. If you complain about things — even justifiably from your perspective — the people at the top will characterize you as a broody spaz, and thus, no one who deserves listening to.
In most cases, people at the top are smart, energetic, full-on type-A people. Their view, learned from being that way and being rewarded with the success of being at the top, is that if you want something — change — you just go and fucking do it, no holds barred, Ashley. You don’t sit there and whine that you can’t get what you want. If you can’t get it in your organization, you go and get a new job, God damn it.
Obviously, not all top-people are like this, but there certainly is more of this operational-think at the top than the bottom.
So, what’s a bottom-feeder to do: the fact that they’re at the bottom, the very fact that there is a bottom, is often endemic of the powerlessness they actually have. That said, faith in that powerless mind-set of the bottom is often such in organizations that they’re not actively defending against it. If the bottom-feeders suddenly get active, if they’re fast and loud enough, the top will get effected.
Now, of course, I’d much rather operate in organizations where getting shit done doesn’t have to be cast in fighting-metaphors. But that’s the way it is sometimes…as the top-folk would probably be happy to remind me with a smile
Here’s the 3rd episode of The Drunk & Retired Variety Show (aka “podcast”), featuring Mr. Charles Lowell and yours truely again.
The recording quality is piss-poor. But, whatever, you know you’ll still like it…despite all the little pops and pips…and dog barking.
I was searching for info on someone today, just doing a typical Google search of their name, and I didn’t really find anything except a few quotes from some trade rags and some obvious “false-positives.”
It re-occured to me that, when it comes to “experts” or other authority figures, I don’t really “trust” any of them if they don’t have a weblog…usually that shows up on the first page of a Google search for them.
If you’re going to make a living being an expert, it’s time to get a weblog. All you have to do it put up links to start with. That’ll be enough. For the full-blown, bust-out, check out old-school consultant/experto tompeters!, he seems to have really jumped in head first.
I’m always happy to see someone’s company-blogging light bulb off, especially in such detail.
Everyone knows that Brandon likes the weblogs, company-internal and otherwise. After having our internal blogs at BMC for awhile (1, 2), and getting some positive results from them, he came up with what I call Whichard’s Bloggin Theorem:
The number of people who read a weblog matters much less than who reads a weblog.
Put one way, in addition to all the benefits Marion points out, blogs are a supra-effective tool for internal marketing. And if you don’t think that’s important, you must work for the perfect company.
I’m an instant-evangelist for anything I like — booze, blogs, Apple products, etc. — so I tell everyone at work about our internal blogs: not just about them, but that they need to post to them. Many of them have the same reaction: “Yeah, I created an account. But only a couple people seem to post to them.”
There’s either one of two perceptions: (1.) it’s not worth it posting to the blogs, or, (2.) the blogs are just the toy of a select groups of people. But then, Whichard’s Blogging Theorem comes in, and all bets are off.
There’re several high-level people who read the blogs, all NewsGator’ed up to suck down the RSS feeds every 30-60 minutes. If an idea starts at the bottom, it can instantly get high up into the management stratosphere.
We call this effect “The Blackhole.” You know, there’s all those movies where you can leap countless light years in space by zipping through a blackhole or wormhole (the second would probably be better, but the first is what’s stuck).
But, back to internal marketing. In hooking up all these types of things at work — wiki, blog, Google mini powered search — I’ve found that the most effective way to advertise it’s presence is to somehow broadcast, essentially, ads into the traditional internal collab-space: email lists, the intranet site, etc.
That’s an obvious rule-of-thumb, but the take-away is that the early majority needs a bridge to new collab-applications. You can’t ask/expect all those people to jump a huge chasm between existing apps and new apps: you’ve gotta connect them together with a few links.
The problem with that, of course, is that different people often control the two ends of the bridge. The new stuff is usually all DIY: someone had a spare server, so they just install a wiki, a blog, or a build/development site. These folks don’t have access to dump links in all those traditional sites.
There seems to be a boot-strapping problem, as ever. Then again, if you’re in this sport, why not test the “theory of just asking,” and fire off an email or phone call?
There’s (above) the second episode for the old podcast. It’s the rest of Charles and I talking about Agile, software stuff, all girded by his time at ThoughtWorks. I think there’s some more StarControl sounds too…and dog barking.
You know you’ve been hittin’ reload on this page just waiting for this second episode!
I’ve finally put together the first Drunk and Retired podcast. This is part one of some back porch-chattin’ with my good friend, Charles Lowell about his time at ThoughtWorks, agile thinking, Star Control, and a few other things. It’s about 1/2 an hour, and you know you’ll love it!
I invited most everyone in my address book that I thought would be interested, but if I missed you, just send me an email or leave a comment.
You can see my Y! 360 page at http://360.yahoo.com/bushwald.
(No doubt, and as promised to Charlene, I’ll write-up more as I get a better feel for it.)