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

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!

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…

Hire Fast, Fire Fast? Not so Fast.

Silicon Valley is full of advice and it frequently comes from people who have little experience on the subject matter.  A popular topic surrounds hiring and terminations with the king catch phrase being: “Hire Fast, Fire Fast.”  To me, what that usually means is lack of diligence, thought, communication and courage.

When hiring people love going with their gut feel, often with disastrous results.  There is an obvious subject of diversity of thought, appearance and background.  When thinking “fast” you are probably hiring people like yourself because humans quickly react to people who they believe are in their tribe.

A startup that lacks the resources of a big company often becomes so desperate to get technical staff that when a decent candidate comes along, excitement ensues and the employer doesn't slow down to put them through a more rigorous hiring process.

I highly encourage technical founders and engineering executives to write out their precise hiring process.  Of course, y…