Some years ago--never mind how long precisely--having little or no money in my purse... I had a great chance to do some Test-Driven Reverse Engineering on a rather complex C program. I extracted test cases. I worked with the users to gather test cases. And I rewrote their legacy app …
more ...Somewhere, I have a vague recollection of reading advice from someone (Bill Gates?) that it takes three versions to get things right. The context may have been a justification of the wild success of Windows 3.0.
Or, I could be just making it up.
But one thing I have …
more ...Just stumbled across several blog postings on unit test naming.
Essentially the TestCase will name the fixture. That's pretty easy to understand.
The cool part is this: each test method is a two-part clause: condition_"should"_result or "when"_condition_"then"_result.
See https://wiki.openmrs.org/display/docs/Unit …
more ...For the 757 Python Meetup group, someone proposed looking at some Python code they had which was slow. The code implemented a variation on the Elo chess rating system. It applied the ratings to other sports, and used the points scored as well as basic win/lose/tie to work …
more ...After talking about some experience with legacy modernization (or migration), I received information from Blue Phoenix about their approach to modernization.
Before talking about modernization, it's important to think about the following issue from two points of view.
Modernization can amount to nothing more than Paving the Cowpaths.
From a …
more ...Here's an object lesson in bad requirements writing.
"Good" is defined as a nice simple and intuitive GUI interface. I would be able to just pick symbol from a pallette and put it somewhere and the software would automatically adjust the spacing.
Some problems.
Read up on compass variation or declination. For example, this NOAA site provides some useful information.
Mariners use the magnetic variation to compute the difference between True north (i.e., aligned with the grid on the chart) and Magnetic north (i.e., aligned with the compass.)
The essential use …
Years ago, when designing an interface to a vendor's web services, I did the following. This isn't a genius move, but it's worth emphasizing how important it is. And what's most important isn't technical.
Some folks love the twin ideas that (1) "someone" might break the API rules and (2) they must write lots of bonus code to "prevent" problems.
Sigh.
There are three distinct things here.