OraTweet Ready for Flight

I mentioned a few weeks ago that OraTweet, Noel’s mirco-blogging package built in APEX, would soon be released to the public after he made some tweaks to get it production-ready.

Today, he unveiled it. You can download OraTweet here.

It’s provided free of charge, as-is, and requires Oracle 10g or 11g and APEX 3.1.x or higher. Oracle XE has not been tested, but Noel says it should work. Matt has confirmed that XE does work, with the addition of a script to load the images into the db.

What do you get?

OraTweet provides you with everything you need to start micro-blogging inside the firewall (or anywhere really). The web front-end is built in APEX, and you can plug in IM/SMS integration. The API allows you to build native and RIA clients (think Adobe AIR) as well. It’s all in there, pretty much everything you’d expect, including the ability to post to Twitter.

Noel also built server-side groups into OraTweet. So, you can create an OraTweet group and anyone following the group will see tweets @ that particular group. We have an @AppsLab group that we all follow, so tweets @AppsLab appear in my timeline. No need to tweet @ each of us individually, which would eat a lot of characters.

This type of grouping is useful if you have a team or a project with many members. Groups are lightweight, easy to create, follow and delete, which helps when you have an ad-hoc project or a unit of work to complete as a team.

Client-side grouping can be built using the API, similar to how clients like TweetDeck allow you to group your tweets.

OraTweet also keeps micro-blogging public. There are no privacy settings to protect your updates. This is by design, since OraTweet grew up as a way to communicate outside email and IM, both of which support peer-to-peer privacy. Noel also didn’t build in direct messaging because it seemed like overkill, since we all have inboxes already.

I’m excited for Noel. His little side-project, started about a year ago, has seen heavy viral adoption inside the firewall. People are uncovering new uses for OraTweet every day.

So, head over to oratweet.com, give a test drive, let us know what you think in comments, including your use cases.

The Enterprise Implications of Google Wave

Five minutes after I posted my Google Wave analysis, I ran into Dion Hinchcliffe’s excellent analysis of Google Wave.  A must read for Enterprise 2.0 folks.

enterprise_waves

This is exactly what I’m envisioning happening with Google Wave in the enterprise.  It will become the “glue code” for the user experience.  It won’t replace existing back-end apps, but provide a much cleaner, nicer, and more productive interface for interacting with them.  The biggest problem most enterprise apps pose is the lack of focus on the user experience.  Google Wave provides a framework for improving that experience.

Google Wave: The Killer Enterprise Apps Platform?

wavelogoLast week’s Google I/O left me feeling very optimistic for what’s to come in the world of web apps.  I don’t have a whole lot to add to the coverage of Google Wave and the other cool things disclosed at I/O.  However, after seeing the demo of Google Wave, I couldn’t help but think of the possibilities of the platform as it relates to the Enterprise world.  Today, Jake and I were just discussing how Google Wave is actually a huge enterprise play for Google.  I haven’t seen much coverage about this but if you think about it, Google has been creeping into the Enterprise for the last several years.  Google Wave is most likely the platform it will use to expand that strategy.

Google Wave as it stands is a collaboration app.  It ties together all forms of communication and collaboration in a nice browser based app.  The biggest features of Google Wave are those that haven’t been built yet.  Google Wave’s underlying platform was built for extensibility — for features that haven’t yet been thought up.  Most of the features that were demonstrated are cool techie-whizzbang features that web devs and web aficionados appreciate — features like live concurrent editing.  However, for average consumers, I’d argue that live concurrent editing isn’t that big a deal.  Think about it… most people are so accustomed to delayed communication patterns (email and snail mail) rather than the real-time, instant feedback style of communication that we get when using instant messaging or sms.  I suspect that’s not going to change for most consumers.  Regardless, I love the live concurrent editing feature, but I think the Enterprise is where a feature like that will be very useful.  Collaborating on documents in real-time is a great feature and one we’ve used in the past with Google Docs.  Since Google Wave will allow developers to build on top of this technology, think of what type of apps you can build that utilize live concurrent editing.  What if you can build a Bespin type of app inside Google Wave and make writing code a collaborative task.  Those of us who practice agile development and TDD do this already, but what if we could do it in one application that allows us to easily mashup other commonly related tasks — like automatically creating bug reports and user stories in external apps, etc?

Google Wave’s extensions consist of robots and gadgets.  Robots are basically participants that you can add to your wave that allow you to automate certain tasks within a wave.  A robot can read the contents of a wave and then perform an action.  There’s a myriad of robots you could create that will allow an enterprise worker to be more productive. Here are a few: Read More »

Best Job in Tech?

Image by Yandle on Flickr used under Creative Commons

Image by Yandle on Flickr used under Creative Commons

So, Rich and Anthony are at Google I/O today, and I’m hearing everyone was blown away by Google Wave.

Rich tweeted, IM’ed and finally called me to say how awesome it was. I’m now waiting to watch the hour-and-a-half demo that rocked so hard.

I’m hoping Rich’s session went well. He was bummed that they conflicted with another Wave session. So, hopefully the room wasn’t too empty.

A couple Oracle folks were in attendance and snapped a few photos. We’ll embed the video when it’s posted, and maybe Rich will post some thoughts.

Anyway, to fill the air in the meantime, I have a question.

I’ve had several different job roles in my tech career, support/IT, consulting, sales consulting, development, and if you work in tech long enough, you probably dabble in all of the above and others at one point or another.

Which do you like best?

I’d have to say I prefer development to the others because I enjoy solving problems with software. Not that the other roles don’t have this too, but in development, it’s the main focus. I always prefer the requirements, design and build phases, and like a true development wonk, I tend to lose interest during testing and documentation.

I know, it’s tough to ensure you’ve solved a problem if you’re not testing enough, which is another reason I like beta-testing. At least then, I don’t have to guess all the ways users will behave; I can just turn them loose to show me.

Plus, you don’t have the urgency of support or sales, which is nice.

Tell us what you prefer and why in the comments.

OpenID: WebVisions 2009

As promised, here’s the riveting second installment of my sort-of recap from WebVisions last week.

WebVisions 2009

On Friday last week, I went to the OpenID panel discussion, hosted by Marshall Kirkpatrick of ReadWriteWeb and starring Scott Kveton, vice-chair of the OpenID foundation board of directors and bacon enthusiast, Chris Messina, community advocate for OpenID, OAuth, and open web in general, and my pal Rick Turoczy, local OpenID wonk.

Dave Recordan, who was scheduled to be on the panel, had to bail early, so Rick stepped in to take his place, a fact I teased him about mercilessly at lunch before the panel.

Rick is no OpenID slouch though. He has covered OpenID and open web for several years, and not just as they relate to the Pacific Northwest. Still, it was fun to tease him. Read More »

See Rich at Google I/O

Google I/OA quick note, Rich will be presenting at Google I/O this Thursday on a panel called “OpenSocial in the Enterprise“.

He’ll be sharing our experiences with OpenSocial and Connect. Although we haven’t yet released our OpenSocial container, Rich and Anthony have been tinkering with it for over a year and have a sandbox environment we’ve been using internally for interested developers.

The guys are attending both days I think, so if you’re going or wanted that extra push to go, you can meet them there.

Google I/O runs May 27-28 at the good old Moscone Center in San Francisco.

Not sure if the panel will be recorded, but I suspect it will be. Maybe Rich will find a moment to blog his thoughts next week.

Thanks to Chet for reminding me.

@oraclenerd

The Future of Mobile: WebVisions 2009

Last Thursday and Friday, I attended the 2009 iteration of WebVisions, a conference held here in Portland focused on the future of web design and development.

WebVisions 2009

As with last year, my goal for attending was to gain new design perspectives. Web design is constantly evolving, and we use many of the innovations present on the consumer web internally in Connect. Rich is the primary design force on our team, and I like to broaden my knowledge of what’s out there to add balance to what he knows and likes to do.

Interface design is highly opinionated, so it’s always helpful to have a wider range of opinions from which to choose.

I haven’t been to any conferences since Defrag last November, but I can tell from reading that conferences have changed. WebVisions was no different. There was a distinct emphasis on social media (ahem, Twitter) not present last year.

I started on a daily recap, but I’m not sure that’s valuable.

Instead, I’ll focus on the two sessions I found most interesting: “Future of Mobile: Native Apps vs. Mobile Web vs. Hybrid Apps” and “OpenID: The Panel Discussion“. Read More »

Use Twitter to Leave a Comment

New signin via TwitterI’m so far behind on my reading, having been on vacation and currently attending WebVisions.

Still, I noticed a post to the Disqus blog from last week announcing their support for sign-in via Twitter. You may recall they also support Facebook Connect, which I enabled back in March, and now you can also use your Twitter account.

The integration uses Twitter’s OAuth implementation, so you won’t need to supply a password to Disqus or to us. The first time you use it, you’ll be redirected to the Twitter OAuth page where you allow Disqus and Twitter to exchange your credentials. After that initial handshake, you’ll be good to go.  Very similar to the Facebook Connect implementation.

No fuss, no mess.

Kudos to the Disqus team. The setup took me literally less than five minutes. You can tweet your comments too, and they will include by @theappslab so we can continue to chatter on Twitter.

In a bit of kismet, I just so happened to be sitting in Chris Messina’s session called “New Assumptions for Designers of the Social Web“. One of his assumptions is that your design must support many methods for authentication; the days of denormalizing your identity and credentials on every new site have ended.

Chris is an advocate for OpenID and OAuth, so not a surprise. I just so happened to catch the post from Disqus during his talk. Funny bit of accidental synchronicity.

Anyway, enjoy.

OraTweet Leaves the Nest

Hello, my name is OraTweetFirst off, thanks for hanging in there while I caught up on my R&R.

I came back today to hear the happy news that OraTweet will soon be available to anyone who wants to give it whirl. Noel is prepping the final package for distribution, but if you’re interested now, head over to oratweet.com and sign up to be notified when it’s ready.

The distribution requires APEX and Oracle DB, natch. APEX is a very active community, and I’m sure people like Chet and Dimitri Gielis will be chomping at the bit to get their hands on it.

I’m really stoked to see OraTweet released into the world for several reasons.

First and foremost, it’s just the “side project turned mission-critical application” story I love. Yes, believe it or not some teams here other than ours use micro-blogging for daily operational work. We have lots of internal use cases that Noel plans to share on oratweet.com.

We’re not the only ones. Laura Fitton of Pistachio Consulting covered Oracle and OraTweet, among other enterprises using micro-blogging for work, in her whitepaper “Enterprise Micro-Sharing“.

Stories like OraTweet are common, e.g. ESME, a project fostered in the SDN, was launched about the same time OraTweet went live in June of last year.

Some people are surprised that Oracle has a micro-blogging application at all.

If you read here, you know we have a soft spot for internal innovation like Connect, which is integrated with OraTweet today. We have big plans to build out a tighter integration that will link OraTweet and Connect groups, allowing people to interact with Connect directly from OraTweet and vice versa from email, SMS and IM.

Let’s not forgot Clayton’s Oracle People iPhone app, which adds another way for people to use Connect and OraTweet. Read More »

Wayback Machine: 24 Months Ago

It’s nearly over, you made it. I’ll be back soon to answer all your comments, right after I catch up on thousand or so emails.

We didn’t really start blogging until June 2007, so technically it’s 23 months, but here’s the archive from June 2007.

Wow, some oldies, but goodies in that bunch. Hoped you enjoyed those blasts from the recent past. I’ll get back to talking about Connect and Twitter soon.

Wayback Machine: 18 Months Ago

Third installment, you’re past halfway there now. I know you miss me. I’m probably jonesing for the ‘tubes right now. Enjoy.

Here’s the archive from November 2007.

It’s almost over, hang in there and talk among yourselves.

Wayback Machine: 12 Months Ago

The second installment of the wayback digest, a.k.a. the “I’m gone, but I want to keep the content fresh” series. Enjoy.

Here’s the archive from May 2008, a mere twelve months ago. Feels like an eternity, looking over the posts. Anyway . . .

  • My First BarCamp: I’m a fan of the unconference format. Hoping this year’s OpenWorld will get more takers as it becomes more understood and accessible.
  • Suggest a Session is a Hit: I hope they decide to run this again. Chet should submit a talk on the how-tos and lessons learned from his COLLABORATE 09 adventure. Thinking this year is a tipping point for interest in that.
  • Random Twitter Effects: This post is pretty germane now, considering how many people are jumping into Twitter.
  • I’m Ready for Preso 2.0: I’m not the only one anymore. I see more visually interesting enterprisey presentation nowadays. The caveat for all you people out there spicing up your presentation with Flickr images is be aware of and comply with the licensing.
  • AppsLab FAQ: What if Someone Posts Porn?: Remember the FAQ series? Yeah, me neither. This was one of my favorite questions to answer. I guess people have moved on because I rarely get it anymore.

Talk among yourselves.

Wayback Machine: 6 Months Ago

So, I’m headed off the grid for a while. In my absence, I figured I’d keep the content fresh by recycling some old stuff.

A bit ironic, but bear with me. Blogging for me is very tied to what’s happening right now.

We’ve been around for a little over two years now, but it seems like a lot longer. So, I thought it might be interesting to take a stroll down memory lane and reminisce on posts from the past.

As a bonus, the automagically generated, possible related posts may dig up some other new-old content you might enjoy.

Maybe you’ll get lucky, and one of my esteemed colleagues will blog in my absence.

Enjoy.

Here’s the archive from November 2008, a mere six months ago Feels like an eternity, looking over the posts.

A couple jump out as interesting.

  • Defrag08 Presentation: Paul’s presentation a Defrag 08 includes some interesting analysis of the Connect and Mix communities. Check out his slides.
  • FriendFeed Brings the Firehose to IM: Even though I struggle to adopt FriendFeed as a part of my daily routine, I love what they’re doing, especially the functionality and their design. I’ve seen an increase in people subscribing to my feed lately, so maybe they’re making headway. Hope so.
  • How to Do a Set-Top Box: This one was a funny study in how to get comments. People love their TiVos.
  • “Looks Good, Works Well”: A rare, but interesting post, from Rich, this one covers some great design principles. Design is always fun to discuss because it’s 1% functionality and 99% opinion. Or something like that.
  • Let’s Take a Legal Break: I’m fascinated and sometimes horrified by the legal precedent the courts are setting around technical issues. Maybe the new administration will address this with a technical education office or something.

Talk among yourselves.

Twitter’s #fixreplies Boo-Boo

remember fail cat? i do b/c i am an uber tweeter

Update: Twitter founder Biz Stone has posted exactly the explanation we (all 3% of us) wanted, and I completely understand the hurry to rush out without fully thinking through the loud ramifications of the squeaky 3%. Kudos.

You’ve probably heard about the Twitter @replies fiasco by now.

Marshall has a good recap and explanation of the “fix” they’ve implemented. If you thought the feature was hard to understand before, the subsequent changes have made it even more difficult to understand.

Personally, I have to pile on the dis train. I’ve always touted the discovery feature of following all the @replies; I used this feature a lot–to find new people and find people I know (or know of) on Twitter. It helped foster and grow the community. Plus, it’s hard cheese for early adopters who have used the service for a long time before the n00bs overran it.

No early adopter, no Twitter.

As a product manager, I’ve followed the story with interest because it has been an interesting case study that is directly applicable to our work on Connect and the recent redesign. Read More »

What’s New in Connect 4.0?

Image by Banalities on Flickr used under Creative Commons (thx @jpiwowar)

Image by Banalities on Flickr used under Creative Commons (thx @jpiwowar)

As I mentioned last week, we’ve released the 4.0 version of Connect, which includes a boat-load of new stuff.

Our main goals for this release were:

  • Put the focus on people, not on objects.
  • Make it dead simple to share anything.
  • Aggregate information by supporting multiple sources.
  • Provide intelligent filtering for easy viewing.
  • Consolidate output of the information we aggregate.
  • Give groups a more independent experience.

These grew out of a few itches we wanted to scratch: aggregation, easy sharing, better groups. Plus, while they were at it, Rich and Anthony cleaned up the code, significantly re-architected the data model and stretched their UI legs a bit with some sweet AJAX goodness.

For those of you still reading who aren’t employees and can’t check it out for yourselves, Connect had been very similar to Mix in functionality if you need a baseline.

I’ll cover each of our goals in turn. Read More »

My Jaunty Adventure

So, Canonical released the latest version of the Ubuntu distro recently, Jaunty Jackalope, version 9.04.

I played with Jaunty in a VM a bit when it was in alpha, and I didn’t notice many new features, compared to Intrepid, aside from the new login splash screen and the Growl-style notifications.

New login splash

I waited a few days, then last week, I decided to take the plunge. The upgrade option in the Update Manager was too tempting, and yes, I usually prefer an upgrade to a fresh install, at least I did.

Since I had gone from Hardy to Intrepid with no issues, I figured this would be as easy. This was a mistake.

If you follow me on Twitter, you’ve probably see that my upgrade hasn’t gone very smoothly at all. I compounded my mistake by doing an upgrade the same week I was working on the Connect upgrade, further compounding the issues I hit. Thankfully, I had a working machine to use, otherwise I would have been distraught.

The problems started when I rebooted after the upgrade, and the display was all splotchy with weird lines. When I logged in, the display was unusable. Turns out there’s an issue with Intel video chips, related to all the eye-candy visual effects I was using in Intrepid. Read More »

I Guess We’re a Product Team After All

I should order some vinyl stickers, paper doesn't wear well.Well, our big redesign of Connect, version 4.0, is finally live. Anthony and Rich are knocking out some final issues, but we cut over earlier this afternoon.

Luckily, it’s the weekend. So, our users aren’t using right now.

Unluckily, it’s the weekend, and everyone on the team has plans.

Next week, I’ll fill you in on the new stuff. So, tune in or out, depending on your interest level.

This is by far our biggest release, probably larger than when we switched to the Mix JRuby code line last Summer. Connect is just under two years old. Born in June 2007 as the IdeaFactory, we’ve managed to iteration four times, and the feature set is surprisingly large.

I’m continually impressed with Rich and Anthony’s ability to accomplish so much with so little.

As we realized this week, we’ve set the bar very high, and now that we have a lot of users, we have to move away from the startup mentality a bit and plan more.

For perspective, last June, when we switched to the JRuby code base, Connect had about 36,000 pageviews from 3,000 odd users. We’ve served 40,000 pageviews this week to just over 2,800 users, and Connect was down for about 12 hours while we tested the production migration.

Lately, a typical week would have topped the numbers for all of June 2008 and then some. Read More »

Kidnapping Data?

in ur server napping ur dataThis is a new one for me.

Earlier this week, the Washington Post reported (via Wikileaks) that hackers had compromised a Virginia state prescription web site, deleted the eight million records and replaced the home page with a ransom note.

The ransom demand, $10 million.

Apparently, this isn’t the first case of datanapping, which doesn’t surprise me. I am surprised that I don’t remember seeing cases like this in the past.

I guess they are kept quiet up for good reason.

On the other hand, it’s pretty frequent to hear about laptops with sensitive data going missing or being stolen, but I’ve always wondered where the data go. I figure in most cases, laptop thefts are smash-and-grab crimes that are meant to turn a quick buck. The perpetrator doesn’t bother to scan for useful data.

After all, if you were given someone else’s laptop right now and told to find something useful, how long would it take you to give up in frustration. Think about your own machine. You’d have to sift through a mind-numbing amount of useless crud before finding anything remotely useful.

Please tell me you don’t have a password.doc file on your desktop.

Still, when personal information goes missing like that, don’t you wonder how easy or hard it would be to find it. Even if you knew what the prize was, it might not be easy to find.

Datanapping is quite the opposite. Read More »

2009: Year of the Side Project

Photo by Hugo90 on Flickr used under Creative Commons

Photo by Hugo90 on Flickr used under Creative Commons

I started this post before the New Year, and it sat in drafts for a long time.

It was never meant to be a prediction post, so the title makes it feel a bit funny. Still, I kept it because this year, the side project seems more common than ever.

Maybe it’s a function of Portland or maybe a function of the geeky crowd with which I associate, but it seems like everyone has so many side projects, that you wonder about their front one (or ones).

As an example, Shizzow started out as a side project for a handful of good people I know here in Portland. They all had full-time gigs (some still do), and Shizzow was a pet project they hoped would take shape. It has (and is awesome), and having at least one side project seems to be the norm, not the exception.

Take my pal Rick, who has about 8,000 different ventures going at any given time, including the Silicon Florist, in addition to his family and his front project that pays the bills.

Rich, Paul and Matt are the same way. So am I. Read More »

Testing is Tough

Photo by diggersf on Flickr, used under Creative Commons

Photo by diggersf on Flickr, used under Creative Commons

We’re currently working on a redesign for Connect, and like any project, waterfall, agile or otherwise, we have a testing phase.

I’ve been designing and building software for a long time, assuming you consider mid-90s a long time, and testing has always been the toughest part of the process.

I’m talking about system testing, which means banging away at a piece of software to make sure it works for as many scenarios as possible. The problem is that no matter how hard you try, you can’t foresee every way that your software will be used. It’s impossible, believe me. Try it sometime with a product that does more than a couple functions.

This is why developers and product managers alike hate testing.

Why?

When you write a system test plan, you have to account for as many use cases as possible. That’s really hard for one person. Then, take into account data.

Large, public data sets are great because they provide you with massive amounts of data, which allow you to test both function and performance. However, if you’re testing something proprietary in nature, e.g. accounting data, how can you account for all the variations?

You can’t. Read More »