Monday, 11/18/2019
- ID
- 8e2fcbb5-3344-4eed-b86f-338f8e195266
Tasks
DONE Dishes
SCHEDULED:
:LOGBOOK:
CLOCK: -- => 0:32
:END:
DONE Set tasks for the day
CLOSED: SCHEDULED:
:LOGBOOK:
CLOCK: -- => 0:13
CLOCK: -- => 0:05
:END:
DONE Andrii / Colin 1-on-1
CLOSED: SCHEDULED: <2019-11-18 Mon 8:00-8:30>
:LOGBOOK:
CLOCK: -- => 1:09
:END:
What I enjoy or find positive about our relationship
- From me
- I love that we can talk through technical issues
- I love that you are proactive about talking through difficult subjects (tasks
taking a long time, motivation issues, getting stuck)
- From Andrii
- Difference of our timezones
- Enjoy 1-on-1s
What I have not enjoyed about our relationship
- Often go for days without talking (timezones?)
- Feel like I'm leaning really hard on you for catching mistakes
- Don't know that much about your interests as an engineer
What can we do over the next 6-12 months to grow as partners?
- In the past, asking "is it interesting to you"
- Be honest with yourself and what is interesting
- Product concerns?
- Find something in PRs to help understand the problem better
- Asking questions all the time, happy to see more questions
- First, need to focus on what we need to do for the customer?
- As you did on today's call, "not sure we need to develop everything"
- Need to get in better direction with Product
- Harry & Robert don't work as much with developers
- Need to find the leverage point with customers
DONE Communications [0/0]
CLOSED: SCHEDULED:
:LOGBOOK:
CLOCK: -- => 1:42
CLOCK: -- => 0:06
:END:
- [X] Check and respond to email
- [X] Check mastodon
- [ ] Write a blog post?
- [X] Jira ticket catchup
Comment on Harry on Custom Attributes
Andrii and I had an interesting discususion this morning during our 1-on-1 about
doing this custom attribute work as backend only in the coming sprint. One of
the things that I was concerned about was the lack of customer needs directly
being addressed by our work. I totally understand how we got here in terms of
aggressively reducing scope on a project to fit in the sprint, but I think
there's a danger in these sort of "backend-only" tickets in that it's hard for
us backend developers to have confidence that what we're building will not need
to be changed dramatically when the UI/UX is implemented.
For this project, I think we're okay to start with the given tickets, with the
exception of permissions (ENG-5424). We can probably keep the story in the
sprint, but it will either be damn simple and less likely to need refactoring
later, or more "feature complete" but at greater risk for needing refactoring.
Aside from ENG-5424, most of this comment is a discussion about how to do this
in the future, and maybe not simply throwing out UI as a way to reduce scope.
DONE Write in daily journal
CLOSED: SCHEDULED:
:LOGBOOK:
CLOCK: -- => 1:01
:END:
DONE Team Boost
CLOSED: SCHEDULED:
- ZOOM
- https://zoom.us/j/647103643
:LOGBOOK:
CLOCK: -- => 0:30
:END:
DONE Lunch
CLOSED:
:LOGBOOK:
CLOCK: -- => 0:40
:END:
DONE Laundry
CLOSED: SCHEDULED:
:LOGBOOK:
CLOCK: -- => 0:26
:END:
DONE Add API endpoint for merging departments
CLOSED: SCHEDULED:
:LOGBOOK:
CLOCK: -- => 0:40
CLOCK: -- => 0:23
CLOCK: -- => 1:10
:END:
DONE Reading Calculus Gems
CLOSED:
:LOGBOOK:
CLOCK: -- => 0:05
:END:
DONE Selectboard meeting
CLOSED: SCHEDULED:
:LOGBOOK:
CLOCK: -- => 1:04
:END:
DONE Animal chores
CLOSED:
:LOGBOOK:
CLOCK: -- => 0:10
:END:
- [X] Feed pigs
- [X] Water chickens
DONE Pick up kids at piano
CLOSED:
:LOGBOOK:
CLOCK: -- ==> 0:30
:END:
DONE Reading Dracula
CLOSED:
:LOGBOOK:
CLOCK: -- => 0:37
:END:
DONE Dinner
CLOSED: SCHEDULED:
:LOGBOOK:
CLOCK: -- => 0:32
:END:
DONE Dishes
CLOSED:
:LOGBOOK:
CLOCK: -- => 0:23
CLOCK: -- => 0:23
:END:
DONE Driving Kember home
CLOSED: SCHEDULED:
:LOGBOOK:
CLOCK: -- => 0:40
:END:
DONE Bedtime
CLOSED: SCHEDULED:
DONE Watching NFL
CLOSED: SCHEDULED:
:LOGBOOK:
CLOCK: -- => 1:07
:END:
DONE Add API endpoint for finding groups that conflict with a group type
CLOSED: SCHEDULED:
:LOGBOOK:
CLOCK: -- => 1:05
:END:
Journal
I had an interesting idea today looking at someone's personal wiki. What if I
used the ability to export org files to HTML to put them up in a place somewhere
on onec.me with a public folder for per-topic org files?
I could keep track of what's missing with to-dos and be able to share my
adventures in various things more easily. One of the things that I've struggled
with as a blogger is writing meaningful posts vs. instructional posts. I think
I'd like to focus more on blogging about my thoughts on processes, rather than
daily travails or how-tos. The daily travails would go in my personal journal
(here :) ), and how-tos could go in the org public folder to be published on onec.me
---
Monday Question: How did a time of personal struggle lead to a breakthru?
The first time I was laid off. I had been drinking the Valley kool-aid of ancient
stoicism and trying to live each day as positively as I could, controlling what
I could control. Turns out I don't control much. Losing my job was a massive gut
check, as I hadn't really seen it coming at all. When I told my wife, she sort
of slow nodded, looked away for a moment then looked back at me and said, "okay,
what's next?"
As I struggled with my value as an engineer and the questions of whether I'd
ever find another remote job as good as that one, I discovered a world of
opportunity that allowed me to grow as an engineer in new roles that I would
have never seen had I not been laid off. In hindsight, my pink slip felt more
like a push out of the nest. And now I'm at 15Five.
---
I have not done a great job of keeping up with task communication. ENG-4141 has
most of the work already done on it. I took a long time figuring out exactly
what was on ask and now the task is probably really simple and I've made it take
much longer than it needed to.
---
Today, I am reminded to keep the Stoic principles in the front of mind. Accept
what nature provides. Work for the common good. Limit my desires to what is
within my control. Accept nothing false. It is human nature to stray from these
principles. Christians would have called this original sin. The intrinsic
bending of our actions towards the destructive. Even when we mean to do good we
often do bad. Belief is a part of our nature and what we choose to believe
taints everything we do. I choose to believe in the power of accountability and
intentional behavior.
Report
#+BEGIN: clocktable :scope file :maxlevel 3 :formula % :compact t :tags t
#+CAPTION: Clock summary at
| Tags | Headline | Time | % |
|--------------------------------------------+------------------------------------------------+---------+-------|
| | *Total time* | *15:58* | 100.0 |
|--------------------------------------------+------------------------------------------------+---------+-------|
| | Monday, 11/18/2019 | 15:58 | 100.0 |
| | \_ Tasks | 15:58 | 100.0 |
| @home, chores, dishes | \_ Dishes | 0:32 | 3.3 |
| @personal, tasks, daily | \_ Set tasks for the day | 0:18 | 1.9 |
| andrii, 1on1, meeting, @15five | \_ Andrii / Colin 1-on-1 | 1:09 | 7.2 |
| @personal, email, comms | \_ Communications [0/0] | 1:48 | 11.3 |
| @personal, habit, journal | \_ Write in daily journal | 1:01 | 6.4 |
| @15five, meeting, boost | \_ Team Boost | 0:30 | 3.1 |
| @family, lunch, meal | \_ Lunch | 0:40 | 4.2 |
| @home, chores, laundry | \_ Laundry | 0:26 | 2.7 |
| @15five, eng4141, feature, api, grouptypes | \_ Add API endpoint for merging departments | 2:13 | 13.9 |
| @personal, reading, calculusgems | \_ Reading Calculus Gems | 0:05 | 0.5 |
| @town, sboard, meeting | \_ Selectboard meeting | 1:04 | 6.7 |
| @farm, animals, chores | \_ Animal chores | 0:10 | 1.0 |
| @kids, errand, piano | \_ Pick up kids at piano | 0:30 | 3.1 |
| @personal, reading, dracula | \_ Reading Dracula | 0:37 | 3.9 |
| @family, dinner, meals | \_ Dinner | 0:32 | 3.3 |
| @home, chores, dishes | \_ Dishes | 0:46 | 4.8 |
| @kids, errand, driving | \_ Driving Kember home | 0:40 | 4.2 |
| @personal, sports, tv, nfl | \_ Watching NFL | 1:52 | 11.7 |
| @15five, eng4141, feature, grouptypes | \_ Add API endpoint for finding groups... | 1:05 | 6.8 |
#+END: