“Technology, like art, is a soaring exercise of the human imagination.”* To my way of thinking this is true for Open Source Software in three respects—the innovation and journey of open source, the evolution of the developer and engineering roles, and the ongoing improvement and enhancement of the Software Development Life Cycle (SDLC). Perhaps there are others you can think of, but those resonate for me. The creation and appreciation for art requires curiosity, divergent thinking, and attention to detail. It took all three of these traits for leaders like Bruce Perens and Richard Stallman to blaze the open source trail. Developers and engineers, too, have that same propensity and passion for exploration.
And that brings us to the SDLC.
The SDLC history doesn’t run as long and deep as that of software programs, and the progression of these processes today are tied directly to a company’s ROI, success, and ability to meet customer demands and deliver high quality products. This, too, takes some study and a different way of thinking.
If you are a developer or software engineer you most likely respect the process while dreading any and all pressures change and new requirements may put on your already bloated workload. However, license compliance, IP management, and security are more of a priority today than ever before with the rise of open source use. To lessen the load, tools to support license compliance should be easy to integrate into the SDLC as well as easy to use.
Alex Rybak, Director of Product management at Flexera is hosting a three-part webinar series focused on the engineering process, and more specifically on:
Part 3: Looking Ahead: 2020 and Beyond
If you are a developer, engineer, or anyone involved with the decisioning around your Software Development Life Cycle, this series is a don’t miss. After all, technology, like art, requires continued reflection and study. Perhaps it’s time to consider or re-examine the impact of Software Composition Analysis on both the business and your role in the software development process.
*Quote from Daniel Bell