Org Web Adapter

journals/2019_04_05.org

ID
429978fd-d076-4e1d-a610-41dbbda0b41b

Friday, April 5, 2019

Friday, 4/05/2019

#+BEGIN: clocktable :scope file :maxlevel 2

#+CAPTION: Clock summary at

| Headline | Time | |

|---------------------+--------+------|

| *Total time* | *1:25* | |

|---------------------+--------+------|

| Thursday, 4/04/2019 | 1:25 | |

| \_ Tasks [1/10] | | 1:25 |

#+END:

Tasks [6/13]

DONE Write in daily journal

@personalhabitjournal

CLOSED:

:LOGBOOK:

CLOCK: -- => 0:05

:END:

DONE Set tasks for the day

@personaldaily

CLOSED:

:LOGBOOK:

CLOCK: -- => 0:09

:END:

Priorities today are to make sure the data warehouse jump host issue has been

explored and either concluded to wait until Justin gets back, do first rounds

of testing on 1210 and RM-2292. Anything I get done beyond that will be a bonus.

DONE Ping Jacob to ask about getting DW jumphost access

@workdatawarehouseaccess

CLOSED:

:LOGBOOK:

CLOCK: -- => 0:01

:END:

Notes

Sent this AM:

Morning from the East Coast, Jacob! When you get in the office today, I need

some help that involves Lauren Hill's computer. She has an SSH key that can

access the data-warehouse jump host computer. She's the only person who is still

employed here and not on vacation with access, and we have a customer who has

waited a while for access.I'm wondering if you can help me by using her computer

to create an account for me on that machine with my public key. I'm honestly not

even sure if Lauren's user has permission to sudo, so this may not work anyway.

But let me know if you have time so I can communicate with the client. Thanks so

much!

DONE Re-test SWAT-1210 with the working caregap parser

@workcaregapscaregapimporterSWAT1210

CLOSED:

:LOGBOOK:

CLOCK: -- => 0:43

CLOCK: -- => 1:18

:END:

Back to working on this because the measures in the base line for XOCOS and

MSTFACO were soft deleted :facepalm:

Okay, thankfully I've improved my workflow for those updates, so it's not nearly

as painful as it used to be. Need to rebuild 1210 kube env and test and then

I'll kick this back to Ayhan.

DONE FIGmd standup

CLOSED:

:LOGBOOK:

CLOCK: -- => 1:02

:END:

DONE Run through test plan Ayhan dropped on 2292 branch

@workcdsqa

CLOSED:

:LOGBOOK:

CLOCK: -- => 2:11

CLOCK: -- => 1:00

:END:

Had to run copy_cms_measures for both 2018 and 2019 ... hmm

DONE Work with Jacob and Lauren Hill to get access to dw-jumphost

@workdatawarehouseaccess

CLOSED:

DONE Prep pizza crusts for dinner

@homedinner

CLOSED:

Journal

Trouble getting things prioitized again. There was an interesting post on hnews

this morning about agile-light, wherein the goal is to maximize work done during

a sprint, while acknowledging that you can't sprint all the time. The first

week of a month is spent in slack-time, which can be used for a variety of

things, but from a developer's perpsective is not spent working on product work.

Refactor, explore proofs of concept, but don't complete tickets.

I like the idea, but I can see how it's written from an engineer's perspective

and that there are lots of folks involved in decisions at a company, not all of

which are run through developers. It would take a diligent manager to keep that

slack week free of stress such that the sprints really were done with full energy.

For what it's worth, at Elation, we've pretty much switched to a full-on Kanban

style of work. We haven't closed a sprint in weeks, and don't think about work

like that at all anymore. At least part of that is due to the FIGmd project,

which Ed very wisely pointed out is, because of our thid party, much more

waterfall-y.

---

After such a blustery and cold spring day, today is amazingly still. Crazy how

the world can vary so dramatically.

Work log