<img height="1" width="1" style="display:none" src="https://alb.reddit.com/snoo.gif?q=CAAHAAABAAoACQAAACi3UkU6AA==&amp;s=hMfJ_f7PVQOiL2csDznj0MZz_-_Sym2oeAYASWsHW4c=">

Enrique Carbonell

Enrique Carbonell

Enrique Carbonell

Pyxis

M.S. & B.S. Computer Science at UCLV, with +9 year of experience building enterprise software solution. I’ve been working as Software Engineer, Team lead and automation nut. I work as Operations Engineer & DevOps Advocate at Pyxis. I’m member of the company team that drives adoption of new technologies and I’m constantly involved in automation and exploring ways to do it properly and as risk free as possible. I have strong interest in DevOps and BigData challenges. I’m part of the team that usually support the transition to a microservice oriented architecture on immutable infrastructure, containers and elastic partitioning. Collaterally, I work as an organizer and regular speaker at international conferences and IT workshops in Cuba, addressing issues of the DevOps cultural movement, and I am an active member of the Docker community. When I’m not writing codes or researching new technologies, I enjoys traveling and sharing my knowledges with other like minded professionals who want to make the world more awesome. Outside of work, I loves spending time with family and building exciting projects.

 

Session: Automate or NOT from the beginning, that is the question...

The DevOps cultural movement, from its definition, has emphasized the importance of preserving order among the 3 pillars: "people → processes → technologies"; But is it feasible to follow this sequence and how can we put it into practice? Where to start the transformation of the ways of doing and generating value in the organization? Is there a golden rule to transform and achieve the adoption of DevOps in organizations? These are recurring questions when you start to implement something that everyone wants, but not everyone knows how achieve it.

Many bet to include tools, others for the organizational vision of the processes; but "where we want to go" is the key. The focus of this presentation is to begin with the definition of the business objectives and refine and correct them under the continuous feedback supported by the tasks of collaboration and automation. Some cases of our experiences will be shared about the DevOps services that are usually requested by clients and some of the points of failure of customer requirements that demonstrate that with measurement and continuous experimentation we can improve business metrics.