Amazon Web Services supports the creation of a network running on their infrastructure that is rich enough for separate public and private subnets just like you may have done in the past on your own internal network. The difference is that the machines, or EC2 instances, running in these Virtual Private Cloud subnets can also be situated in different data centers, or Availability Zones, in front of an Elastic Load Balancer that should be resilient to individual machine failures or even entire data centers failing. Very few companies hosting their own machines have that capability, and as a bonus this can be accomplished by developer.
2014-01-14 11:33:42 +0000 technology amazon aws cloud network
Homespun programmed metallophone played by falling marbles: precedent, directions and guide.
2008-09-01 11:33:42 +0000
Project reviews, or retrospectives, are broadly adopted within agile and other development communities as a mechanism to enable team learning through experience. They are often structured as a forum for the team to review recent experiences in a constructive way, then moving onto generating a list of lessons learned and potential changes to investigate or include in future development work. The reviews are frequently supported by only minimal data which can lead the team to be ignorant of significant but gradual changes over the course of the project, or as a mechanism to support hypotheses of the team. Could a ready access to such metrics and reports for use in a supporting role within retrospectives be effective?
2007-10-02 13:05:42 +0000 devcreek testing retrospective
We have assembled a new cut of the animation based on the testing activity collected during the first 9 months of developing DevCreek. It now includes a short guide on reading the animation and the inclusion of auditory cues. The sounds go some way to highlighting a number of the rhythms present during development.
2007-09-10 13:05:42 +0000 devcreek testing animation
I missed it the first few times it was mentioned. I then assumed it was an in-joke amongst all these North Americans. Later mistook it at as a compliment on a team member’s attire. Eventually, I realized they were all taking about one of our charts, the so called “t-shirt” chart.
2007-08-02 13:05:42 +0000 devcreek testing visualization
Representing the testing activity of a developer has been an area that we have explored on a few occasions. There are a number of reports that graph the totals of test runs, tests run, failure rates, and so on by day or over other intervals. Though these reveal some useful information, especially in combination with each other, so far they haven’t been so successful representing the activity in direct way. A way that reveals, or at least hints at, the testing style of a developer. Do they practice test first? Do they scope out their work by writing many failing tests, then make them pass one by one? Are they refactoring, or actively adding new tests?
2007-03-27 13:05:42 +0000 devcreek testing visualization
Things were going along quite well in the project room until our PM, the resident stress tester of the group - he has that delicate ‘bam-bam’ touch that is so important for exploratory testing, managed to get our SWT/RCP client application enter a weird mode. New editors wouldn’t appear, but you could still move between existing ones. And where had the menus gone? After we found the application log, which we normally get to from the About Box off the Help menu though of course that didn’t open anymore, our faces went white when the exception stack slithered onto the screen:
2006-06-05 11:33:42 +0000 swt windows technology diagnosis