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
1 comment

Popular posts from this blog

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!

Why you should take the software job in San Francisco (or not).

Silicon Valley is an iconic place for technology.  Many people say this is the place for the “best and the brightest.”. Apple, Google, Facebook, Salesforce, Twitter and other top companies draw a lot of talent form all over the world and the largest chunk of VC capital goes to companies in the Bay Area, so it seems like moving here is a no brainer!

The real situation is actually not that simple, I believe there are three scenarios where it makes sense, but in many cases living in the Bay yields disappointing results.  The cost of living, housing situation, homeless catastrophe make places like San Francisco a lot less appealing to a lot of people.  So in what situations does it make sense to move to SF?

Startup founder raising millions There are many places to be a startup founder, but if you are looking to raise capital the largest pool of VC money is in the Bay Area.  There is an established network, events and conferences which give founders an opportunity to pitch more people th…

Pull Requests and Code Reviews

Software development involves a great deal of collaboration.  One of the most basic blocks of collaboration on a software development team is a code review.  There have been many different ways of doing code reviews over time, some of this has been dictated by the tools available.  Git and online source collaboration tools created a set of best practices that are worthwhile of adopting on any team.

About a month ago I have looked at various articles about how to best create a Pull Request (PR) and do a code review and the attached presentation is the result of this research.  The presentation can help you guide your team and develop a set of collaboration practices that works for your particular situation.

It’s good to start out with why to seek a code review.  Having clarity about your intentions helps you guide the person helping you with code reviews and also to manage your expectations about you can get out of the code review.  The reasons for seeking a code review are generally …