Skip to main content

10 Reasons I’m Going to Cloudstock on Dec. 6th


Cloudstock, an all day event for developers focused on developing in the cloud, will welcome a large number of thought leaders and business leaders in the cloud as sponsors and presenters! Cloudstock is on the day before salesforce.com’s annual user conference, Dreamforce.
As a sponsor of Dreamforce, we’re busy gearing up by creating new samples, developing a new integration with a key partner and creating new presentations to show how developers can use electronic signatures in the Cloud. While the pressure will escalate up to the very last minute, we’re setting aside the last day before Dreamforce for Cloudstock.
The top 10 reasons the DocuSign technical evangelists are taking a full day for Cloudstock:
  1. John Musser’s evaluation of the Cloud API landscape: John and the entire ProgrammableWeb team keep their hands on the pulse on most of the web services – we’re looking forward to a big picture view.
  2. Session from Box.net’s Hieu Nguyen and Jeremy Glassenberg: Sometimes we get so caught up in the web services that it’s good when an expert like Jeremy steps out and shares a holistic approach to integration. You will definitely see me at the “Connecting Services Inside & Out: Thinking Outside the API” session.
  3. Dave Carroll’s deep dive into using the Force.com database: Accessing Force.com database through the web services has been on my “to-learn” list for some time. Who better to get an overview of Force.com technology from, than Dave?
  4. Learning about the interests of the PHP community: Many PHP programmers have joined the DocuSign developer program and it looks like Amazon has invested into showing how PHP can be used on their Amazon Web Services platform. I’d like to see what kind of questions interest the PHP community.
  5. Insights from Google: Google will discuss the Google Marketplace and since we just launched an e-Signature Marketplace, I’d love to hear what guys at Google pitch to their potential and existing software developers.
  6. Amazing demos: I’ve heard about Twilio’s amazing presentations, and though I personally have not touched phone technologies in ten years I am curious to see John Sheehan create solutions on stage right in front of the audience.
  7. Hackathons: I love hackathons; and while I am not the fastest coder, I enjoy seeing what other people can come up with in a short time. I also like to think that it’s just great to be in the running.
  8. Java + Force.com: I always loved Java. I enjoyed being part of the Java Community Process 10 years ago and defining some of the interfaces. The ability to use Java with Force.com is an amazing combination of winning technologies. VMForce.com is a promising solution for our customers and partners; I need to see what it’s all about.
  9. Networking! I am a natural networker – I like meeting new people especially if they are sharp and have good ideas! My first job ever was handing out flyers for my dad’s vet clinic at a dog show – ever since, going to expos and meeting people in the industry always puts a smile on my face. Cloudstock will be great for that.
  10. Someone mentioned there will be food… I just want to let everyone know that it still works, even years after college.
See you all at Cloudstock! Look for the DocuSign DevCenter team – Mike Borozdin, Julia Ferraioli, Craig Smith and Veronica Lentfer.
Post a Comment

Popular posts from this blog

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 …

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!

There are Only Two Ways to Treat Your Team

There are only two ways to treat your team: take care of them or let them go.  Early in my management career there have been times when someone has been underperforming on the team.  Before I knew better I let my emotions get the best of me: I’d give them the cold shoulder, avoid including them in conversations and look like I was upset with them. Thankfully with some good mentorship I came up with a simple rule: we are helping each other or you are off the team.

One of the biggest mistakes that folks make a lot of times is letting people linger on for too long.  Hiring good engineers is hard and getting new folks up to speed is hard.  You feel like you are going to miss your product delivery plan if you let someone go.

Letting folks linger when you are unhappy with each other creates a toxic environment.  This toxic environment is generally contagious and brings the entire organization down.  Of course you can’t have a constant state of euphoria on your team, but if a productive and…