MODERNIZATION AND REFACTORING-IMPROVING THE DESIGN OF SOFTWARE
A quick guide to Modernization and why rules applicable to refactoring are an essential strategy for success. Improving the design of software after it has been written is a common practice. Eventually the User Interface, the code and the database slowly sinks from engineering to eventually hacking. With Modernization, you can take a bad, even chaotic, design and rework it into a well-structured application. If you continue to ignore refactoring, the internal software design and the overall goal of the software tends to decay. As changes occur for short term goals, often without a full comprehension of the application, the application will lose its structure and business value. The cost to maintain and change the application becomes cost prohibitive and slow. This session will provide some guidelines to facilitate quicker and easier change in the flowing world of business and software change.
The DevOps Playing Field-The Tools of Ignorance
The tools of ignorance is a nickname for a catchers protective equipment: catchers mask,chest protector, and shin guards. The usage was meant to be ironic, contrasting the intelligence needed by a catcher to handle the duties of the position with the foolishness needed to play a position hazardous enough to require so much protective equipment. The world of IT is very much the same. In this session, we will take a walk through the DevOps diamond of concepts, history, offerings and best practices. How intelligence is required but also the concept of teamwork and the significant role teamwork plays in the final results. Avoidable mistakes can jeopardize the adoption success in a DevOps strategy and add peril to your production dreams and business value stream. The statistics are in to demystify the myth, you can deploy changes faster with less errors.
March 21, 2019
<<- Click Powered by an easy and affordable Event Management Host