Today: 2.4mi (37min)
- 5min walk
- 21min repeat (7x)
- 2min run
- 1min walk*
- 11min walk*
Of note:
- 6th walk was 1:45, and cool-down was 10:15, but I’m too lazy to format it
- I completed 2.1mi in 30min. Usually (like, for ever) I go 2mi in 30min. Progress.
Today: 2.4mi (37min)
Of note:
The plan:
The actual: 2.4mi
oof
Today: 2mi
Sunday: 2.25mi
Today: 2.9mi
Next time, I’ll plan the route back.
Here’s the tail end of my bike commute to work.
The ritual for new hires at a past company included asking the new hire to copy a stack of papers containing the “shared knowledge and lore” of the organization. The new hire spent most of the first two days filling out HR paperwork, making copies, and reading the copied material. This kept them out of the hair of the manager/mentor who probably had a bunch of fires to put out from the weekend.
Fast-forward to today, where I was pointed at the wiki and the pages referencing ‘New Engineer’ and ‘New QA’ necessary information, giving the lead of my new group time to figure out what to do with me. (I’m in training for the next 3 weeks)
I can speed-skim with the best of them, and I noticed an interesting pattern. Clusters of last-modified dates.
Bunches of pages were updated in the past week. Another clump in the past 2 months. Then another cluster 6 months ago. More clusters at 2 years and 3.5 years in the past.
The clusters seem to be thematic, too. Almost like they correlate with starts of new approaches, or changes in approaches.
Hmmmm. Cultural archaeology can be such fun.
A quick hint about managing test data for “enterprise” applications.
Does the application under test rely on a large central database?
If so, is that large central database backed up on a regular basis?
If so, can you get access to the backup files?
For some testing tasks, it might be easier to just load a new database instance from those backups than to create and populate a database from scratch.
In one case, we dropped, truncated, and pruned a number of tables from the backup, then created a new backup file. A much smaller backup file. One that loaded in one hour instead of many hours.
apropos of nothing, some stream of consciousness thoughts while scanning twitter. (hey look, I’m blogging again!)
Over the past few weeks, I’ve been working through the book Agile Java – Crafting Code with Test Driven Development, by Jeff Langr. Why?
I’ve had some interesting experiences (thoughts and feelings) doing this, and I’ll write up some details in separate posts.
I just finished lesson 12. Earlier, I wrote the following in my notes:
I’ve gotten through the end of lesson 6, and I’m very impressed. I feel confident that I can recommend this book to my coworker, and he’ll be better off going through it than not.
I’ve been using eclipse more than intellij for lessons 5 and 6, and I’m steadily becomeing more comfortable with it.
I found and installed the EclEmma plug-in, and very much like using code coverage to identify code I can delete after some refactoring. And I’m duly impressed that I get 100% code coverage when I run my tests*
*actually, almost 100%. the gaps are things like assertTrue not being called with a false condition (duh), never calling the constructor of a utility class, and not testing the default methods for enums. I can live with that, for now.
One thing I did not expect was that my brain felt like it filled up and overflowed, and I kept forgetting what I was doing, as I got towards the end of the lesson 6 exercises.
more on that last bit soon.