Archive for the ‘Uncategorized’ Category

running diary – 2-aug

Sunday, August 2nd, 2009

Today: 2.4mi (37min)

  1. 5min walk
  2. 21min repeat (7x)
    1. 2min run
    2. 1min walk*
  3. 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.

running diary – 26 july

Sunday, July 26th, 2009

The plan:

  1. 5min walk
  2. 15min repeat
    1. 45sec run
    2. 15sec walk
  3. 12min repeat
    1. 105sec run
    2. 15sec walk
    3. 45sec run
    4. 15sec walk
  4. 5min walk

The actual: 2.4mi

  1. 5min walk
  2. 15min repeat
    1. 45sec run
    2. 15sec walk
  3. 105sec run
  4. 15sec walk
  5. 45sec run
  6. 15sec walk
  7. oof

  8. 18min walk

running diary – 23 July

Thursday, July 23rd, 2009

Today: 2mi

  1. 5min walk
  2. 20min repeat
    1. 45sec run
    2. 15sec walk
  3. 5min walk

running diary – 21 july

Tuesday, July 21st, 2009

Sunday: 2.25mi

  1. 5 min walk
  2. 20 min repeat
    1. 60sec run
    2. 90sec walk
  3. 5 min walk

Today: 2.9mi

  1. 5 min walk
  2. 30 min repeat
    1. 40sec run
    2. 20sec walk
  3. 5 min walk

A longer-than-expected ride at lunch

Monday, June 22nd, 2009

Next time, I’ll plan the route back.

Elevation Profile
Track 006

My strenuous ride

Thursday, June 11th, 2009

Here’s the tail end of my bike commute to work.

Elevation Profile
Track 002

The New Gig – Look at the Wiki Waves

Monday, April 27th, 2009

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.

Test Data Management

Wednesday, February 4th, 2009

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.

some of my values

Friday, September 5th, 2008

apropos of nothing, some stream of consciousness thoughts while scanning twitter. (hey look, I’m blogging again!)

  • I like to know what I am doing, and why I am doing it. (mindfulness)
  • I like to know what we are doing, and why we are doing it.
  • I like to know what we did, and why we did it.
  • I like feedback. Fast feedback, and close feedback.
  • I like creating affordances.
  • I like precision and accuracy.
  • I like to tell my audience when I am compromising precision or accuracy in order to better reach another goal.
  • I like people who are hungry to learn. (they make me a better teacher)
  • I like french vanilla ice cream.

Learning Java through TDD

Friday, September 5th, 2008

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’m evaluating it as a self-study guide for a co-worker who wants to learn java.
  • While I’ve read plenty of java, and made small modifications to existing java programs, I’ve never written a major java program from scratch, nor have I ever set out to systematically learn java. So I’m learning java. yay!
  • While I’ve written plenty of tests, and I’ve modified some existing tests, and I’ve written tests before I’ve written code, I’ve never written a major program using xunit-style tests and doing TDD. So I’m learning TDD. yay!
  • I’m also taking the opportunity to immerse myself in eclipse and intellij

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.