Skip to main content

CloudStock Recap

Cloudstock was a very special event. I hope that salesforce.com puts one together next year. DocuSign team did extremely well. We have had several hundred conversations with cool developers and hosted three sessions on Cloud computing and the eSignature API.

Several things that I thought were interesting:
1) It's amazing how many of the cloud developers have their sights on international solutions. I talked to a guy who was doing loan servicing in France. There was a group of consultants that were doing a supply agreement application for a Chinese partner. There were many other people who are taking their US based solutions world wide. This is great!

2) Mobile is entering enterprise computing. I talked to a developer who is doing a medical records system that will need to be rendered on the iPhone and iPad. Fields sales organizations are now getting connected to the cloud. The trend is undeniable.

Overall there is another big shift that is happening - people are creating apps faster and getting feedback from customers faster. I talked to a great cloud billing company and we agreed to do a prototype together. Our estimate is that we can put something together in half a day. That's right - half a day. In half a day people didn't even put requirements together in the past.

The success of CloudStock proves that our decision to go all in to the Cloud in 2003 was the right one!

-mb

PS: Don't forget that we are hosting a developer meetup in Seattle on 12/15. Register here: https://www.developerforce.com/events/seattle_developer_meetup/registration.php?d=70130000000Fkg2

Comments

Ben Siscovick said…
nice recap. this is def the age of the cloud and will only continue to become more so with the passage of time.

Popular posts from this blog

Quality of Code is Quality of Life

About 20 years ago when I started working in technology companies I remember “the best” engineers had similar patterns:
-They worked crazy hours
-They knew the systems no one else knew
-They could react and deliver something faster than anyone else
You could always hear other employees say: “Bob is really smart, no one knows how to get anything done in system X besides him!”

This reinforced optimization around being the only person who knew how to do something in some part of the code.  That in turn reinforced job security and bargaining for those engineers, but also chained them to a particular system.  We had big code bases of C++ or Java code where some “Bob” hacked up features as soon as he possibly could.  “Bob” would have occasional nuclear disasters where he’d sleep in the office or through the weekend and then everyone would thank him for how he “saved the day.”  “Bob” sacrificed his quality of life to get praise when he hacked stuff up quickly and then the second time when n…

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of
different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers.

Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily accessible…