So often many of us who have been in IT for a number of years think of software services as something getting done off shore by a large staff focused on their screens with their ‘blinders’ on. This could not be further from the truth. We have many extraordinary software development experts today focused primarily on the customer experience while using the ever improving technologies that make sure customers are no longer frustrated with websites being down, product availability advertised being untrue, or any number of issues we all encounter that causes our blood pressure to rise.
Agile has been around for many years now with many organizations tailoring their agile approach in different ways that work best for them.
“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.
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.
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.
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