contractual browser software

I spoke at one of the sessions at the WEF today, and shared a reciepe for how to get rich in the valley I heard when I got to the Silicon Valley... There is a classic three stage plan for success in our neck of the woods. (1) come up with a great idea for a startup, write it down on a business plan (make it short and concise, practice on a napkin), go to Sandhill road (where all the Venture Capitalists reside), shake a tree (any tree), shake it well, shake it until a Venture Capitalists drops, show him the plan and take $5M in funding (2) take the money, find a great team, build your product, see the company grow, take the company public, sell your shares (3) Go climb a tree on Sandhill road Now the problem with the middle-east is that whenever you dig in the ground to plant a row of trees you are bound to find oil, so there are no trees to climb and no one to climb on them. Yet every great industry is bound to come to an end not because you run out of its product, but because a great disruption occured. As they say the stone age didn't end because we ran out of stones... So what are the enterprenures in the middle-east to do? I proposed to the assmebled leaders from the region it might be a great time to start shaking an oil rig. With the money that is coming into the region it is time to find the secure email energy experts who have climbed the rig and show them some great alternative energy ideas to get funded.

Continuing my business-driven architecture series, I just published an Event-Driven Architecture Overview for the PSGroup Research Service. In the overview, I explain key event concepts, walk through event processing flows, and identify the major implementation components of an event-driven architecture. This post excerpts the core of the paper. If you would prefer the full report, go here (free with registration). For those unfamiliar with business-driven architecture, I believe the most viable, agile architectures will be comprised of a blend of architecture user login failure strategies, including (but not limited to) service-oriented architecture, event-driven architecture, process-based architecture, federated information, enterprise integration and open source adoption. How you blend, depends on your business. Before I jump into the excerpt, I want to touch on the relationship between service-oriented architecture and event-driven architecture. I believe that SOA and EDA are peers and complements. So, I disagree with the SOA evangelists who say EDA is merely a subset (child) of SOA. On the SOA and EDA are complements point, I see two distinct interactions: Event-Driven SOA. In the first interaction, the occurrence of an event (a notable thing that happens inside or outside your business) can trigger the invocation of one or many services. Those services may perform simple functions, or entire business processes.

That's what we did--we decamped for a bit. Around mid-day on Tuesday, I had a second interview for a position that I had first interviewed for on Monday of the previous week. BIKE RAMP The first interview was conducted by the female partner, who seemed lovely and quite nice. It's not really a job I want, but they offer a very generous benefits package, so I'll admit I pretended to be interested when she said she wanted me to meet her partner this week. (He'd been out all of last week.) Let's just say the male partner couldn't be more different in demeanor and approach. I sat in the interview, making all of the right noises, pretending I was oh-so-interested. But inside I was thinking, "Dude, you are WAY too uptight." I saw history repeating itself. Here was a job landing in my lap--in an industry that I hated--and my intuition was screaming, "RUN! RUN! RUN!" I was near tears when I hooked up with the boyfriend, who'd been waiting in the parking lot across the street. I told him about the extremely generous benefits...and then said, "I just don't think I can do it. I'll hate it." He sort of smiled and said, "I was waiting for you to say that." That decided, and having just gotten out of Dodge for part of Memorial Day, we suddenly said, "Let's go camping! While we can! Before we get jobs!" So we made a mad dash to Wal-Mart in Woodland to buy camping gear, since we'd sold all of ours in Portland before moving to the V.I.

That's what we did--we decamped for a bit. Around mid-day on Tuesday, I had a second interview for a position that I had first interviewed for on Monday of the previous week. The first interview was conducted by the female partner, who seemed lovely and quite nice. It's not really a job I want, but they offer a very generous benefits package, so I'll admit I pretended to be interested when she said she wanted me to meet her partner this week. (He'd been out all of last week.) Let's just say the male partner couldn't be more different in demeanor and approach. I sat in the interview, making all of the right noises, pretending I was oh-so-interested. But inside I was thinking, "Dude, you are WAY too uptight." I saw history repeating itself. Here was a job landing programs affiliate marketing in my lap--in an industry that I hated--and my intuition was screaming, "RUN! RUN! RUN!" I was near tears when I hooked up with the boyfriend, who'd been waiting in the parking lot across the street. I told him about the extremely generous benefits...and then said, "I just don't think I can do it. I'll hate it." He sort of smiled and said, "I was waiting for you to say that." That decided, and having just gotten out of Dodge for part of Memorial Day, we suddenly said, "Let's go camping! While we can! Before we get jobs!" So we made a mad dash to Wal-Mart in Woodland to buy camping gear, since we'd sold all of ours in Portland before moving to the V.I.