Thursday, 3/28/2019
- ID
- 8a910a97-bfea-4884-9d8d-f9661bdef85c
#+BEGIN: clocktable :scope file :maxlevel 2
#+CAPTION: Clock summary at
| Headline | Time | |
|---------------------+--------+------|
| *Total time* | *9:48* | |
|---------------------+--------+------|
| Thursday, 3/28/2019 | 9:48 | |
| \_ Tasks [6/19] | | 9:48 |
#+END:
Tasks [8/8]
DONE Write in daily journal
:LOGBOOK:
CLOCK: -- => 0:10
:END:
DONE Mentorship meeting with Cris
:LOGBOOK:
CLOCK: -- => 1:32
:END:
Agile, retro
+ Retro is most important meeting
+ If you don't come together and make statements about what works
+ You don't learn
+ Agile is supposed to be quick easy wins
+ Should be able to work around things without quick easy wins
40 hours
+ If you're doing more work, something in the process not right
+ They'd just keep asking you to do things
+ No sense of keeping time respected, everythings always due now
+ Kills personal life
+ Manage up?
+ Important to see people take time off
+ I'll see by example that I shouldn't take time off
+ Sam kept track of increment on spreadsheet each week and take a week off
+ One week at the end of every major project
+ Shoot for 4 weeks a year, 3 projects per year, and one week to yourself
+ Recovery from creative work requires turning your brain off
Foxholes
+ Good to have the comradarie and go through trials together
+ To have a contenious relationship with management
+
Trust
+ Product will usually be the ones to prioritize
+ Tech. details of how a solution works, wont always see dependencies
+ If Eng. doesn't come to the table
+ Happens everywhere, seems like people try to make it easy on engineers
+ Pushing with product person to talke about direction on a periodic basis
+ Want to solve people's problems
+ Put you in role of hearing from user
+ The benefit shouldn't be sharing the burden of support
+ Should contribute to backlog, write up ticket about experience
Product
+ What's the threshold between engineering solutions and solving with what you have?
+ MVPs on twtitter ... dont' have to be software, could just be a process, or spreadsheet
+ Users have very simple needs ... may be very specific
+ Upload photo, want everyone to see it
+ Tech-wise, lots of ways to implement that
+ Breakdown tools into separate processes
+ How to make the happy flow for the customers
+ Guy with 4 logins, would love one log in and a way to change context?
+ Have to do a lot of engineering work
+ Only one guy having that problem, easy to say context is not customer
+ May not be the right tool for him, makes sense not to build for him
+ He is the customer, you do want to build for him
+ Ridecell wasn't willing to say person is or isn't our customer
+ Product would have been better if they chose one or the other
+ Software as tools, give someone a toolbox with a lot of little tools, lots
they can do
+ If you give them one super elaborate
+ An experience often forgotten is
+ How product people react to discoveries of customer facing improvements
DONE Ensure we have a plan for late-merging the internal tool fix :@work:release: :LOGBOOK: CLOCK: [2019-03-28 Thu 10:12]--[2019-03-28 Thu 10:16] => 0:04 :END: Made an ask of Sam to QA the box bug ticket this morning. If he doesn't have bandwidth I'll cheeck with Ayhan. Once they sign off, I'll merge it to master and cherry pick the commit onto tonights release branch.
DONE Prep ingredient list for Emma's cake
:LOGBOOK:
CLOCK: -- => 1:33
:END:
DONE Deploy internal tool fix to prod admin
:LOGBOOK:
CLOCK: -- => 2:09
:END:
Takes forever and a day to deploy these boxes ... :(
DONE Haricut with Peter & Silas
:LOGBOOK:
CLOCK: -- => 0:46
:END:
DONE Set up a personal jenkins server to do builds of my branches
DONE Write up developer journal and copy to Confluence
https://elationhealth.atlassian.net/wiki/spaces/~colin.powell/pages/305823777/Work+log
Journal
Kicked off the morning hanging out with Emma, though it seemed like we both
weren't quite on the same page.
For Emma's birthday this year, I think I'm gonna give her a Tuesday when I take
the day off and we just go for a drive somewhere with Nabby. I thought about a
stay at a Bnb or something like that, but so long as we have Nabby it's not
gonna feel like a getaway that way.
Work log
This morning, I followed up on the late merge of the internal tool fix. I was
planning initially to get it into the release tonight, but Karin pinged me
around noon to ask if it could go out earlier and no practice could be onboarded
without the ability to send API credentials.
So I pinged Ayhan and he got right to work QA certifiying the bug fix. Once I
had his sign off I merged the branch to master, cherry-picked to a patch release
branch and to the official release branch for tonight. I then managed the
deploy to production admin boxes, skipping stage, as it was a pretty simple fix.
Andrew signed off on that path.
In the afternoon I spent a little time setting up a personal jenkins integration
server that can run my development branches. I realized that I was relying on
CircleCI to do the full test suite runs, and that was causing slow down in my
process and an over-dependence on public tools. It also means I can just run the
backend tests and get results faster.
The rest of the day after stand up was spent trying to break the BMI CDS in
various ways to see why it's not picking up the exclusion when a doc tag for a
patient declining the exam exists in the patient's records. I'm still not much
closer to resolving it ... on to tomorrow!