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!

Comments

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!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers. Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily acce

Intuitive Programming - Comments

Comments are a topic of vibrant discussion.  Ever since programmers could leave some text in the program that was ignored by the machine the debate started: “what’s a good comment, what’s a bad comment, why comment?” There are endless instructions to programmers that say many of the following things: 1) Describe your function! 2) Don’t write in the comment what you wrote in the code. 3) Tell people why you are doing what you are doing. What I think has been missing from this discourse is the audience for comments and through those audiences there is intent.  The code is being read, skimmed or analyzed by people and tools.  So what are the audiences and reading modes? 1) Maintaining and enhancing the code 2) Skimming through the entire module or file to figure out what the overall structure is 3) Reviewing the test files to check out the test coverage and edge cases 4) Seeing the docstrings of functions while being in a separate file altogether 5) Reviewi