Learn about the primary DevOps tool types you should be using on the mainframe and across platforms. Get examples of Compuware mainframe DevOps tools and some of their primary open-systems integrations.
Converting to an Agile SCM tool like ISPW from one you’ve used for years seems daunting at first. But Compuware’s SCM Migration Services team will make the process as painless as possible for you.
Chat apps should be considered essential for mainframe teams to adopt as they work to move the platform into their enterprise’s DevOps toolchain.
Twelve questions to help you rate the quality of your mainframe development, based on the "Joel Test" from Joel Spolsky, CEO and co-founder of Stack Overflow.
ISPW’s integration of automatic, graphical Impact Analysis is another example of how source code management can be made much more simple and Agile by automating certain aspects of the tool.
To me, the tradition of making New Year’s resolutions is very much like traditional Waterfall development: You plan your enhancements—in this case resolutions—and deliver them only once a year.
When I see someone staring at a green screen and coding, I get the same sense as when I watch a historical reenactment: a strong sense of how things were. Nostalgia is fine, but that doesn't mean we should continue living in the past.
As a Product Manager I’m constantly looking for the win-win option of something that provides flexibility with minimal complexity. Often this balance is only achieved by starting with the right philosophy and continually learning from customer experience.
Here at Compuware we converted from CA Endevor to ISPW for our Source Code Management (SCM). I noticed right away that ISPW used a superior way to implement exits. You simply go to a panel and select the exit you need to modify from a list of all available exits. This is important because there is no hunting around to find the exits—they are all listed.
Sometimes things like SCM products are naturally complex, but that complexity should be handled out of the view and participation of the user. The goal of a product should be what we’ve termed "elegant simplicity": a simple, intuitive and natural way to accomplish what needs to done.
Having now used ISPW versus Endevor, you quickly appreciate the benefits of its modern architecture. You quickly begin to value the improvements in efficiency, performance and power you get with a database. And, you quickly come to the conclusion, why did I let myself fall into the day-to-day trap of tolerating the loss of productivity from a Source Code Management that is a prisoner of the past?
There's a lot of talk and hype about Big Data and with that comes confusion and mistakes. Here are five big mistakes you can make when starting a Big Data initiative. Ignore the source of your data. Don't pay attention to the origins of your data; it will just slow [...]
Credit: Joe + Jeanette Archie I was affected by the flooding that hit the Detroit area recently. While cleaning out my basement I was struck by the amount of things I had—for no good reason. Let me explain. Many things I had, I had because they were given [...]
I’ve written a lot about metrics as a means to gauge the complexity of a program including SLOC and the Halstead and McCabe metrics. An often over looked metric – and one I haven’t touched on before – is one that’s in plain sight: comments Comments are added to programs [...]
The McCabe Complexity Metric, as discussed in my last post, relates to the number of decision points (points where the logic path splits) in a section of code. When used along with the Halstead Metric, the McCabe Metric can help you objectively assess and compare the complexity of new programs [...]
In my last post I discussed code complexity and the advantages of breaking complex code into smaller blocks. But how can we judge the size of these blocks? How can we quickly know the number of decisions in each block? If we think in terms of the delicate balance in [...]
“Any darn fool can make something complex; it takes a genius to make something simple.” This quote has been attributed to different people, from Albert Einstein to Pete Seeger. Whatever the origin, I think it really applies to code. When given a task to accomplish developers should all be able [...]