Will your software outlast the original developers? Almost certainly yes. But will you be able to maintain it? This course will teach you how to maintain cost-efficient and functioning software through planning and development strategies.
Studies show that software maintenance represents 50%-80% of the lifetime cost of software. Failing to respond to platform changes, increased demand or newly discovered security flaws can bring down software - and kill a business. In this course, Building Software That Lasts - A Guide to Maintainable Software, you'll discover how advanced planning strategies and factoring maintainability into the development process from the beginning will dramatically reduce the costs and risks related to keeping your software running long after the original developers have left. First, you'll learn about why software needs to be maintained at all and how maintenance is shaped by the nature of the software. Next, you'll learn how to reduce costs by keeping maintainability in mind at every step in development and how to manage any potential risks. Finally, you'll cover how to maintain software for the long term and prepare for the possibility of your software needing a rebuild after a long period of time. By the end of this course, you will have a much more comprehensive understanding of software maintenance, why it's important, and how to build software that lasts.
Dan Appleman is a well known author, software developer, and speaker. Currently the CTO of Full Circle Insights, he is the author of numerous books, ebooks, and online courses on various topics (technology and other). His latest book is "Advanced Apex Programming" - advancedapex.com Personal Website http://danappleman.com.
Course Overview Hi, my name is Dan Appleman, and if you apply the techniques you learn in this course, it will not only save your company money, it may save your company. Hear me out. I've been a software vendor, a consultant, and I'm currently the CTO of a company selling analytic Software as a Service to enterprises large and small, and along the way I've seen nothing more costly, painful, and heartbreaking than maintenance failures. I've seen companies desperate for help because they've lost the installation disks for tools and software from vendors that no longer exist, or even lost their source code. I've been on projects where not only did the software not work as expected, they couldn't tell me what was expected, or what they had originally asked for. I've seen software fail due to platform upgrades that weren't so much unanticipated, as ignored, and I've seen companies completely dependent on software that they didn't even realize they were using. They all spent more than they had to, to the point that some of them aren't around anymore, and not only were those problems avoidable, most of them could've been prevented easily and inexpensively with just a little bit of foresight. That's what this course is about, foresight. The kinds of things you can do while building software to reduce the long-term costs and risks of any software project. The things you can do now to save money, save your company, and avoid the stress of living through some of the stories that I'm going to share with you in this course.