The majority of developers spend less than half of their time coding, according to ActiveState's recent Developer Survey 2018: Open Source Runtime Pains. According to the survey, 50% of developers say security is one of their biggest concerns, and 67% say they choose not to add a new language when coding because of difficulties related to corporate policies.
The result is developers devoting time to non-coding activities like retrofitting software for security and compliance criteria after software and languages have been built. And they won't choose the best tool or language for the job because of corporate policies. Their satisfaction goes down and risk goes up.
So, developers aren't able to devote time to high-value work. This creates additional business risk because their time-to-market is slowed, and the organization increases tech debt by not empowering developers to decide on "the best" tech.
How can this issue be solved? One way is to integrate security and compliance workflows into the software development process in four easy steps.
From OpenSource.com
View Full Article
No entries found