Skip to main content

CloudStock 2012 is happening tomorrow! Stop by my panel in Developer Theater!


Tomorrow I will have the pleasure of speaking at an amazing event – CloudStock 2012.

First of all I have a confessio - I love CloudStock. It’s an event for developers by developers. Moscone West is a great venue and the Force.com crew puts on an exciting show.

Part of the reason I love CloudStock is that it still maintains a “down to earth” vibe. You can approach organizers, ask questions in the developer theatre, and get help from developer advocates at companies like DocuSign, GitHub, Twilio, Amazon, Mashery, Heroku and, of course, Force.com. This is a general spirit of camaraderie among participants.

Through the years Dave Carroll and Nick Tran (the guys who created the Force.com developer community) have maintained an easy-going, approachable atmosphere that sets the tone for everything that happens at Cloudstock.

If you are around, please join me for an interactive panel on API design in the Developer Theatre at 5:30PM tomorrow. While we have some slides to kick off the conversation, we will make this a truly CloudStock type experience so that it is very interactive. You will be able to join the discussion with the folks who are helping DocuSign design the next generation of our REST AP – including Chuck Mortimore and Dave Carroll of salesforce.com, Neil Mansilla of Mashery, Jeff Douglas and Dave Messinger of Appirio/CloudSpokes, and Mike Leach of Facebook. We will be discussing the trade-offs and design considerations for DocuSign's eSignature REST API.

Time: 5:30 p.m. - 6:30 p.m.
Room: Developer Theater

Be sure to register for the event at: www.cloudstockevent.com
Also, to get a free developer sandbox with DocuSign, visit: www.docusign.com/devcenter
Post a 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!

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …

Two Critical Questions for Your Next Interview

I’ve interviewed probably over 500 engineering and management candidates over the last several years.  There have been a lot of really smart people who have applied at DocuSign, Microsoft and Tempo Automation. A surprising number of them didn’t have a clear answer to these two essential questions:

Why are you interested in joining our team?Why should we be interested in you? 
If you are an applicant, having a prepared answer for these questions is critical.  If you are a hiring manager, you should ask them and have a clear answer to these questions at the end of the first interaction with your future team mate.

In a field where work is somewhat predictable and static, those questions are less critical, but in software development perseverance, ingenuity and focus make all the difference. These are the two main questions that will separate a subpar and a superb hire.

When I discuss those two questions with an applicant I try to go below the surface.  Generic answers like “it says you ar…