//Important Takeaways from Best Practices in SaaS Conference

Important Takeaways from Best Practices in SaaS Conference

Last Tuesday, 40 attendees from across the cloud, SaaS and DevOps spectrum came together to hear from industry leaders about “Best Practices in SaaS Operations” at Google TLV. .

Companies at Conference

As professionals working in the cloud, hearing from colleagues and professionals offers an opportunity to discuss emerging issues and trends that will shape the future of the industry.

The focus of the conference was to offer practical takeaways about topics that impact all those working in cloud computing.


Here are the key takeaways in order of speakers. We’ve also included their presentations on Slideshare.

Developers are NOT Operations Guys

Ofir Nachmani, Cloud Evangelist at IamonDemand

Ofir Nachmani, Cloud Evangelist at IamonDemand

“DevOps” is meant to denote a close collaboration and cross-pollination between what were previously purely development roles, purely operations roles, and purely QA roles. Because software needs to be released at an ever-increasing rate, the old “waterfall” develop-test-release cycle is seen as broken. Developers must also take responsibility for the quality of the testing and release environments.

The increasing scope of responsibility of the “developer”  has given rise to a new job candidate: the “full-stack” developer. Such a developer is capable of doing the job of developer, QA team member, operations analyst, sysadmin, and DBA. Before you accuse me of hyperbole, go back and read that list again. Is there any role in the list whose duties you wouldn’t expect a “full-stack” developer to be well versed in?

Due to constrained resources,companies are forced to take on the role of DBA and fix the issue themselves.

At any one time, a developer at may be acting as a developer, QA tester, deployment/operations analyst, sysadmin, or DBA. That’s just the nature of the business, and some people thrive in that type of environment. Somewhere along the way, however, we tricked ourselves into thinking that because, at any one time, a start-up developer had to take on different roles he or she should actually be all those things at once.

Forcing developers to take on additional roles traditionally performed by specialists means that they:

  • aren’t spending their time developing

  • need to keep up with an enormous domain of knowledge

  • are going to burn out