2020-10-03, 10:30–11:10 (America/Mexico_City), Best Practices
Language: English
Heavy motivation to automate everything, even the automation itself, is the common understanding of the most DevOps teams. A strong dominance of administrators in those teams (Operations), transform ideas of increasing the development process to a personal playground. Far away from the necessities of the DEV team, which have to create a runable application.
Often Developers have to fight heavily with the provided infrastructure, because this break productivity massively down. In this talk we resume the lessons learned like in the paper agile bullshit from DoD. After more than one decade as configuration manager in different enterprise projects, I discuss nonsense DevOps workflows and how they could detected. Between some important definitions I focus on practical examples of the Java ecosystem.
Marco Schulz (@ElmarDott) studied at HS Merseburg, Germany, computer science and holds an engineers degree in software engineering. The main topics in his field of work are Software Architectures, automatism of the software development process and Software Configuration Management. Since more than 15 years he work in different large Web Application Projects all over the world. Currently he is an independent Consultant, Trainer and publish plenty articles in several computer magazines. Blog: https://enRebaja.wordpress.com E-Mail: marco.schulz@outlook.com