In many cases this became part of the enterprise

In many cases this became part of the enterprise

first_img“In many cases this became part of the enterprise ALM culture,” said Flint Brenton, CEO of CollabNet. “However, in healthy collaborating organizations, this was never part of ALM practice. [But] I have heard war stories of badly behaving organizations that played this out in the context of a painful ALM experience.”Before agile, there were a variety of these barriers. The siloed teams were certainly part of the problem, but most of the roadblocks of ALM were cultural. Removing these barriers has allowed software development to become a cohesive unit with other parts of the organization.(Related: ALM can keep your apps in play)“I personally think the best thing that ever happened to the ALM was agile and the DevOps movement,” said Paula Rome, senior product manager at Seapine Software. “That really brought into focus [that] it’s not the tool, it’s the process and the people and how you are working with each other.” Before the shift in software methodologies, the application life cycle was fairly simple—or at least straightforward. Now, contextual elements of ALM have changed drastically because of the evolving nature of the industry. Where the old ALM process was all about managing application development, today’s faster pace of delivery and more complex applications are forcing companies to create a new model that works with current practices.ALM started in the “waterfall” age, but now it has a close relationship with Continuous Delivery, DevOps and agile. Releases that used to take weeks or months now only take a few days. The entire software development industry has experienced a huge shift in culture, and the role of developers (along with their tools) has modernized.ALM’s value is that it gives insight to the teams that are doing development and testing, and the scope of ALM has been broadened to include capabilities around collaborating, getting feedback from customers, and having some sort of strategic plan in place. It’s hard to imagine doing DevOps or agile without ALM, but perhaps with this shock to the system, it’s time to rethink the application life cycle.Embrace the culture shockThe waterfall culture of an organization is in the past for ALM processes. Large organizations that were siloed experienced many problems that could have been solved by tapping into the right tools. Often, teams in different silos would blame others when things went wrong, and that’s when big projects would fail.last_img read more

JDK 13 has entered Rampdown Phase One signaling t

JDK 13 has entered Rampdown Phase One signaling t

first_imgJDK 13 has entered Rampdown Phase One, signaling that the new version of Java is just weeks away based on the timeline of previous iterations. The overall feature set is now frozen so further JEPs will be targeted toward the next release. RELATED CONTENT: The rise of KotlinHere is what you can expect from JDK 13:The new version of JDK includes text blocks, a multi-line string literal that avoids the need for most escape sequences, automatically formats the string in a predictable way, and enhances the readability of strings in Java programs that denote code written in non-Java languages. It is available as a preview. “The need to denote short, medium, and long blocks of text in a Java program is near universal, whether the text is code from other programming languages, structured text representing golden files, or messages in natural languages,” Jim Laskey, senior development manager for Oracle wrote in a post. Also, extended application class-data sharing will allow the dynamic archiving of classes at the end of Java application execution. This will eliminate the need for users to do trial runs to create a class list for each application. JDK 13 reimplement Legacy Socket API which will make it easier to work with user-mode threads known as fibers. The ZGC heap will return unused heap memory to the operating system. Additionally, ‘switch’ can be used either as a statement or an expression. These changes will “simplify everyday coding, and prepare the way for the use of pattern matching (JEP 305) in ‘switch’,” according to the JDK team.JDK 13 is expected to enter Rampdown Phase Two next month. The final release candidate is aimed for the end of August while general availability should be sometime in September. A full list of features is available here.last_img read more