Naples
Software Italian Engineer, contributor to the open source community with various projects well documented, passionate about everything related to technological processes. Various degrees and masters on the sofware and engineering processes (civil, industrial and managerial), consultant for international projects and software architectures, lover of web and mobile applications, oriented to the development and devOps automation tools. Scholar of arts, tv series in native language, open-minded, advocate of the self-improvement, and creative writer.
Authored Comments
Thanks for the great explanation about the SRE role and its important value more advanced of the DevOps engineer.I have only one consideration to make, or anyway my personal opionion. The professional figure is very hybrid and skilled, so in such vast topics and applications, one may risk binding or perhaps specializing in a single technological stack or process and making the role so different (or not well defined commonly) depending on the reality in which one works. For me it is important to focus on universal principles and methodologies, being careful not to bind to individual tools (which are always changing in the IT world).
Today the containerization is the core of every DevOps activity and the continuous delivery. For example build automation tools, such as Jenkins (and its fork named Travis), creates (and destroy) a containerized agent to build your module with the required capabilities, using a yaml (or pipeline) config file.