Posts Tagged "optimyth"
Here at Optimyth Software, until now, we have focused in reducing our customer’s software maintenance cost with our solutions. This doesn’t mean cost reduction is the only benefit our customers get when they implement our solutions, they can help as well in other aspects with different flavors: effective use of software and hardware resources, compliance with application security best practices, improve reliability of the code developed in different programming languages and more.Read More
Who are the target users of application quality tools?
This question has been banging in my head for some time now, and the answer is not simple. As probably know by now, here at Optimyth Software, we develop and sell quality assurance tools based on static code analysis. So, why has this been bothering me? I should now, right? Okay, you caught me, I do know. But, it is a tricky question. Let me explain myself.Read More
Well, it seems like the Mayans got it wrong… Or is it that we want to interpret spooky and apocalyptic events in just the way they had to measure time?
Anyhow, since this old world is going to stick around for a while and by the way we measure time it is Christmas season. I just wanted to forward you a merry, merry Christmas from Optimyth’s team. And since it seems that 2013 is peek out around the corner, our best wishes for the next year.
Just one more thing. Don’t expect much fro this blog in the next couple of week. We will be enjoying the season eating and drinking like it was the end of the world….
See you next year.
Thanks for reading.Read More
If the other day we talked about how one of our customers uses checKing AIM to streamline the application portfolio within a large enterprise -saving in maintenance and application evolution cost-. Today we are going to see how yet another customer from the insurance sector(*) benefits from another use of checKing AIM: align the business with the application code.Read More
In previous posts we have seen the importance of using techniques such as static code analysis on your software. In fact, experts say that you can detect up to 60% of potential defects with these techniques.
When a static code analysis tool is checking the code, it is looking for the use of good practices used by developers in their implementations. Good practices can come from standards such as IBM standards for Cobol or Sun recommendations for Java, from books or from our experience. For static code analysis good practices are implemented by rules that the developers should comply with.Read More