Org Web Adapter

Thursday, 11/7/2019

ID

dd018673-26e2-42f6-a726-3fabe641ac3d

Tasks

DONE Set tasks for the day

CLOSED: Thu Nov 7, 201908:01 SCHEDULED: Thu Nov 7, 2019

:LOGBOOK:

CLOCK: Thu Nov 7, 201907:31--Thu Nov 7, 201908:01 => 0:30

:END:

DONE Laundry [3/3]

CLOSED: Thu Nov 7, 201911:11 SCHEDULED: Thu Nov 7, 2019

:LOGBOOK:

CLOCK: Thu Nov 7, 201908:01--Thu Nov 7, 201908:12 => 0:11

:END:

- [X] Start a load of laundry

- [X] Put away dry clothes

- [X] Hang up wet clothes

DONE Communications [3/3]

CLOSED: Thu Nov 7, 201909:43

:LOGBOOK:

CLOCK: Thu Nov 7, 201909:42--Thu Nov 7, 201909:43 => 0:01

CLOCK: Thu Nov 7, 201908:13--Thu Nov 7, 201908:39 => 0:26

:END:

- [X] Check and respond to email

- [X] Check mastodon

- [X] Write a blog post?

DONE Thursday call with Cris

CLOSED: Thu Nov 7, 201909:42 SCHEDULED: <2019-11-07 Thu 08:30-9:30>

:LOGBOOK:

CLOCK: Thu Nov 7, 201908:39--Thu Nov 7, 201909:42 => 1:03

:END:

- Incremental refactoring

- Cowboys, Ranchers and Farmers

- How to get engineering-only tickets in sprints

- Squad that's led by engineering, not by product

- Make a list of refactor-able code

- Create checklist for PRs: write tests, feature flags?, query updates?

DONE Write in daily journal

CLOSED: Thu Nov 7, 201911:11 SCHEDULED: Thu Nov 7, 2019

:LOGBOOK:

CLOCK: Thu Nov 7, 201909:44--Thu Nov 7, 201910:10 => 0:26

:END:

DONE Figure out next steps with constraint on group names

CLOSED: Thu Nov 7, 201918:48 SCHEDULED: Thu Nov 7, 2019

- Note taken on Thu Nov 7, 201912:51 \\

This came up again today with another constraint issue. Paul suggested making it

a one-off script. I think I'd like to find a way to consistently make these

sorts of database changes without having to back to the well everytime.

:LOGBOOK:

CLOCK: Thu Nov 7, 201916:36--Thu Nov 7, 201918:48 => 2:12

CLOCK: Thu Nov 7, 201914:15--Thu Nov 7, 201916:15 => 2:00

CLOCK: Thu Nov 7, 201912:10--Thu Nov 7, 201912:16 => 0:06

:END:

This https://github.com/15five/fifteen5/pull/24792

1. Product input around how to rename conflicting groups that already exist (specifically smart groups)

- Seems like we had a pretty clear answer at one point

2. Thought around what to do if the concurrently created index ends up in an invalid state (revert and re-run migration, most likely)

- What if we run this in a one-off?

DONE Cleaning the house

CLOSED: Thu Nov 7, 201916:17 SCHEDULED: Thu Nov 7, 2019

:LOGBOOK:

CLOCK: Thu Nov 7, 201913:09--Thu Nov 7, 201914:15 => 1:06

CLOCK: Thu Nov 7, 201911:12--Thu Nov 7, 201912:10 => 0:58

:END:

- [X] Clean bathroom surfaces

- [X] Scrub bathroom floor

- [X] Dishes

DONE Complete my 15Five

CLOSED: Thu Nov 7, 201916:17 SCHEDULED: Thu Nov 7, 2019

DONE Cross train

CLOSED: Thu Nov 7, 201916:36

:LOGBOOK:

CLOCK: Thu Nov 7, 201916:17--Thu Nov 7, 201916:36 => 0:19

:END:

DONE Dinner

CLOSED: Fri Nov 8, 201907:54 SCHEDULED: Thu Nov 7, 2019

:LOGBOOK:

CLOCK: Thu Nov 7, 201918:48--Thu Nov 7, 201919:40 => 13:06

:END:

DONE Bob's Burger's

CLOSED: Fri Nov 8, 201907:56

:LOGBOOK:

CLOCK: Thu Nov 7, 201919:40--Thu Nov 7, 201920:27 => 13:06

:END:

DONE Bedtime

CLOSED: Fri Nov 8, 201907:54 SCHEDULED: Thu Nov 7, 2019

:LOGBOOK:

CLOCK: Thu Nov 7, 201920:26--Thu Nov 7, 201920:40 => 0:14

:END:

DONE Watch Poldark

CLOSED: Fri Nov 8, 201907:54 SCHEDULED: Thu Nov 7, 2019

:LOGBOOK:

CLOCK: Thu Nov 7, 201920:26--Thu Nov 7, 201921:30 => 1:04

:END:

DONE Watch NFL

CLOSED: Fri Nov 8, 201907:56

:LOGBOOK:

CLOCK: Thu Nov 7, 201920:26--Thu Nov 7, 201921:30 => 1:04

:END:

Journal

Today got off to a rocky start. A relatively simple pull request had to have two

revisits to get done, one by me and one by Andrii. Basically I forgot to put the

initial PR behind a feature flag, and once that was done I didn't test the

feature flag addition locally so it totally failed on staging.

Andrii was nice about pointing out that it was missed in PR review, but I still

feel bad.

Thankfully I also had a meeting with Cris scheduled for this morning, so I was

able to broach the subject with him. He proposed creating a pull request

checklist that I run through whenever I open a pull request. Things like

checking for tricky migrations or feature flags or ensuring good test coverage.

We also came up with a wonderful analogy for styles of development. The Cowboy

and the Farmer developers, one of whom plays fast and loose, and the other

favors process and structure.

---

I was hoping to run today, but I mistimed it and by the time I came upstairs it

was pretty well raining. Thankfully I was able to get the dogs in before they

got too gross and cold.

Report

#+BEGIN: clocktable :scope file :maxlevel 3 :formula % :compact t :tags t

#+CAPTION: Clock summary at Thu Nov 7, 201919:01

| Tags | Headline | Time | % |

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

| | *Total time* | *9:18* | 100.0 |

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

| | Thursday, 11/7/2019 | 9:18 | 100.0 |

| | \_ Tasks | 9:18 | 100.0 |

| @personal, tasks, daily | \_ Set tasks for the day | 0:30 | 5.4 |

| @home, laundry, chores | \_ Laundry [3/3] | 0:11 | 2.0 |

| @personal, email, comms | \_ Communications [3/3] | 0:27 | 4.8 |

| @personal, mentorship, cris | \_ Thursday call with Cris | 1:03 | 11.3 |

| @personal, habit, journal | \_ Write in daily journal | 0:26 | 4.7 |

| | \_ Figure out next steps with constraint... | 4:18 | 46.2 |

| cleaning, chores, @home | \_ Cleaning the house | 2:04 | 22.2 |

| xtrain, @personal, exercise | \_ Cross train | 0:19 | 3.4 |

#+END: