Leave a comment

Fake News – Java is Dead!

Roger FrechBy Roger Frech, Senior Software Engineer

“Java is Dead”, “Java is Dying”, “Java is Obsolete” and other variations on the meme of Java mortality appear frequently on line in the IT “press”.  These are click-bait, intended to draw your attention to a headline, or get some cheap SEO.  For the more complex and nuanced truth about trends in Java usage – look beyond opinions for evidence.

Continue reading


Leave a comment

VPN = Virtual Productivity is NONSTOP!

By James Cavazos, Senior Performance Test Engineer

In most tech companies, it has become commonplace to have VPN access to allow for working remotely. This can allow for greater productivity and flexibility for employees should they need to work from home or during business trips. It can also lead to some drawbacks. If you are not careful you could see a lot of your time-off spent doing work to the point that it feels like you never left the office. This can be especially difficult for workaholics and people with mindsets that can’t leave things unfinished.

Continue reading


1 Comment

A Practical Look at Go, Part 1

By Ken Walker Senior Software Engineer

About two years ago, I was working on a project written in the Go language. Go was originally developed by Google in 2007 for internal use, but was later released (open source) for general use. The project I was on was a large enterprise-wide service that collected large amounts of data (and did it well). This article introduces some of the interesting aspects of the language that might entice you to consider it for your own use, while pointing out a few things of which to be aware if you do.

Continue reading


Leave a comment

Noting Special Events in Retrospectives, to Capture Sources of Technical Debt

By Paul Cooper, Senior Performance Test Engineer

A fundamental expectation for a high performing Agile team is to have clear requirements to begin building the product(s) with sprints and validating demos. The Agile approach supports the philosophy and the reality as long as the integrity of the requirements remain clear and well thought through. What happens when requirements run amok? Continue reading


Leave a comment

Data Driven Testing – Separating Automation Code from Test Data

By Paul Cooper, Senior Performance Test Engineer

Test automation can be a costly time consuming endeavor. Often automation code and test data become entangled, leading to both fragile tests and fragile automation code. Once that happens, new tests will require programming to implement them. This helps us understand why testers now need coding skills. Design changes to the application, such as changing where or how a value is input, will also require updating the automation code and in turn may disrupt the test data.

Continue reading