Skip to main content

Meet DocuSign at CloudStock London


If you are a software engineer in Europe you can’t miss the CloudStock London on May 22nd.   Top cloud platform and web service companies are getting together with 3,000+ developers to talk about the best way to create and integrate new generation of applications.

Some of the sessions that I think are going to be very exciting are:
1. Develop Social Apps with Chatter and the Chatter API
2. Market: Introduction to Heroku - Building Next Generation Apps

Along with learning you will also have an opportunity to do some hands on coding with min-hacks.   Good hacks are going to be rewarded with gift cards and hoodies.  The top winners are going to get VIP tickets to Jay-Z and Kanye West’s “Watch the Throne Tour”

DocuSign team is going to showcase our new eSignature REST API.  We can’t wait to show you our new toolkit and maybe help you create a quick Node.js application that you can deploy on Heroku and kiss your fax machine good-bye.  You can actually try some of this technology today by going to http://www.docusign.com/devcenter  and http://iodocs.docusign.com

One of the key things about CloudStock is that it’s free to attend.  Basically you just need to make the time to be there.  Looking forward to connecting to European developers!

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!

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…

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 …