-jjp

Work, home, bike, kids, dog, cats, music, collaboration, programming...

Dec 7
Brrrrrrrr Brutal cold this weekend, well, brutal for Portland. Even colder this morning. Crazy blue, pink and white sky as well. Time to break out the wool hat for my morning commute. Busy Weekend I spent a good deal of Saturday working to sort out the Sunday morning release details with Eric Mosberger from our SCM team. Many moving parts, and we lost the support of his teammate since he went over his already agreed to cap on hours. Saturday night found us chauffeuring boys around to social engagements. Good side of this was MA and I found time for a dinner out alone. Went to Tabla in barely NE Portland. Nice time, okay dinner, overall uninteresting place though. Way too many people looking busy but not quite working for our tastes. Bit too spendy as well. Especially the drinks in our opinion. After dinner, I found myself having to drive Joe from party A in Milwaukie to party B in Tigard. Went to see The Informant while he did whatever teenagers do at parties these days. Pretty boring movie. Odd. Sunday morning started off with the maintenance deployment at work. Ended up being fairly complicated and taking up almost the whole day. Seven thirty until about one in the afternoon for the whole thing. Spent a big chunk after that wondering about ways to clean things up to make them smoother. Laundry list follows. Better application tool for Engine Menus. I want to write a Menu editor, export/import, compare tool in Django/Jython for this Better application logging - we need to come up with some consistent way to log request successes as well as errors. That way we can use logs to tell us when things are working properly Better hooks to validate whether a deployed version actually is running properly on all nodes. Often times we can’t tell whether something is up or not on all nodes. Saner place to look for all application check out procedures in our team wiki. Saner place to capture what our online monitoring tools are actually monitoring so we can tell what’s really not working when it sets of the klaxon bells. Retrospectives after deploys with the SCM team.

Brrrrrrrr

Brutal cold this weekend, well, brutal for Portland. Even colder this morning. Crazy blue, pink and white sky as well. Time to break out the wool hat for my morning commute.

Busy Weekend

I spent a good deal of Saturday working to sort out the Sunday morning release details with Eric Mosberger from our SCM team. Many moving parts, and we lost the support of his teammate since he went over his already agreed to cap on hours.

Saturday night found us chauffeuring boys around to social engagements. Good side of this was MA and I found time for a dinner out alone. Went to Tabla in barely NE Portland. Nice time, okay dinner, overall uninteresting place though. Way too many people looking busy but not quite working for our tastes. Bit too spendy as well. Especially the drinks in our opinion.

After dinner, I found myself having to drive Joe from party A in Milwaukie to party B in Tigard. Went to see The Informant while he did whatever teenagers do at parties these days. Pretty boring movie. Odd.

Sunday morning started off with the maintenance deployment at work. Ended up being fairly complicated and taking up almost the whole day. Seven thirty until about one in the afternoon for the whole thing. Spent a big chunk after that wondering about ways to clean things up to make them smoother. Laundry list follows.

  • Better application tool for Engine Menus. I want to write a Menu editor, export/import, compare tool in Django/Jython for this
  • Better application logging - we need to come up with some consistent way to log request successes as well as errors. That way we can use logs to tell us when things are working properly
  • Better hooks to validate whether a deployed version actually is running properly on all nodes. Often times we can’t tell whether something is up or not on all nodes.
  • Saner place to look for all application check out procedures in our team wiki.
  • Saner place to capture what our online monitoring tools are actually monitoring so we can tell what’s really not working when it sets of the klaxon bells.
  • Retrospectives after deploys with the SCM team.
Posted at 7:46 AM