Change has always been one of the most important wheels driving the IT industry. IT product vendors, systems integrators, technology vendors, a plethora of consulting service providers –- all partner with customers to engineer, deliver and enable change in some form or the other.
Today: The NSA/FBI project mining communications data from tech companies, a coder's life in links, a high-performance fork of Google's LevelDB, Text Adventures vs. MUDs vs. Roguelikes, and more.
So we are running a quite a bit of automated UI testing and we have found over a large number of concurrent test nodes that even when the Xvnc plugin has correctly started that the environment is not always ready or reliable.
Secure Code Reviews and application Pen Tests are both important practices in a secure software development program. But if you could only do one of them, if you had limited time or limited budget, which should you choose?
With so many cogs collaborating in the infra-machine, a check on their collaboration seems rather mandatory -- like any other integration test for your in-house managed service. After all that was key idea behind having automated configuration management itself.
I’ve been noodling on the phrase “Thinking Together.” Thinking Together is one aspect of the mindset that Product Owners need to embrace. I have been using this phrase with new Product Owners to explain why many Agile practices work.
Whether it’s organizational dysfunction, discovering a role isn’t right for you, abusive management, or unethical requests, we look at the nagging yellow flags that pile up and can ignite into red flags that start your mind down the road of: Going, Going…Gone.
“But our customers don’t want 10 new versions a year. The last release alone had over 600 bugs!” retorts the hotline manager. “How about a small update with just a handful of bugs?”
A quick Java snippet for log scraping.
Let's imagine we're storing an order as a JSON document and serving it up with minor server-side processing, again as JSON. An example document might be like this...
While configuration management tools like Chef or Puppet are a critical component of the DevOps Toolchain for building scalable infrastructure, they are only one piece of the automation puzzle.
With a simulation, you create a safe environment in which people can experiment with learning a new skill or seeing how they operate. There are two critical pieces to the simulation...
Have you ever had a feeling that your automated tests are becoming overhead for the project? That the effort to keep them green seems to be higher than the added value? Then maybe what you do is integration testing and not unit testing.
Continuous Delivery is a software development discipline where you build software in such a way that the software can be released to production at any time. You’re doing continuous delivery when...
As there is no “official” definition for DevOps, many individuals and organizations have their own definition. This morning at Innovate, IBM introduced its take.
The growing cost of most software development efforts can be traced back to one underlying cause – the lack of visibility into the software.
Writing a single application or installer that will work uniformly on 32-bit and
64-bit machines is complicated. Here's how.
Today: Arduino on the farm, Flask wants your help, and pure procedural programming with Fishbike. Plus: Intricate circuit-board beasties and wisdom from Joss Whedon in an unexpected place.
In this talk, Paul Gerrard discusses continuous delivery, particularly as it pertains to long-term requirements. Testing up front, he says, helps to deliver "front-door quality, not back-door quality."
One of the challenges of an automated build and test environment is you want your build to be fast, so that you can get fast feedback, but comprehensive tests take a long time to run.
I’ve already blogged about Deploying on Azure Web Site with Database Project in the past, but in that article I showed how to accomplish it with customization of the Build Template.
I've evaluated many open source projects and realized that APIs are often not documented well. It is important for the community to know what the reasons behind this.
Should we deploy a unique tool that is able to manage a wide variety of technologies and quality domains, or do we need a “pure player” tool dedicated to each technology’s specificities?
What is so cool about the possibility to access private class members from outside? Everyone keeps asking you during job interviews what are the basic rules of object oriented programming.
I would suggest going slowly toward automated modernization. I'm not easily convinced that any automated tool can preserve what's meaningful and ignore the parts which are quirks, bugs or legacy cruft that needs to be disposed of.