Wednesday, June 12

[soid]

 The plan was to get to the office by 9:30, before the standup, meaning I should plan for delays and get there by 9:10 at last. It was about 7:40 when I heard the alarm and looked at the phone in fear that it was 9 already. I brewed some coffee, brushed my teeth, grabbed a cookie, and headed to the train.

The train was crowded; I got to sit only by 96th Street. Trying to read Kleppmann’s book, but in fact, sipping coffee, biting the cookie, and looking at the girl dressed in an all-black business suit and white socks with straightened black hair. It was about 28th Street when I realized I had only read about one page of Kleppmann. I tried to focus and read something about conflict resolution during replication. 

The plan was to test all my new UI on physical devices, so I happily put three of them in front of them and started clicking them, then I realized it would be better if I also deployed the Lambda change, so I tested all together. 

And so I spent all day with this lambda. First, needed to upgrade nodejs from 14 to 20: is it possible that something breaks after, before I upgrade the code? I don’t know. So spent a couple of hours googling it. Apparently, it may work just fine, despite the major version upgrade. So, I messaged Will telling him I thought this risk was okay, but there was a small chance of things going bad. Two or three hours I spent overthinking it? Anyway, it went unnoticed. Everything was just fine.

Then, my new API still didn’t show up. That I spent the rest of the day trying to understand what was missing in API Gateway.

By 4pm I remembered that the evening plan was the concert. Bad thoughts were coming to my mind: why did I even start all these upgrades? What if something I touched breaks tonight? Will I go back from the concert and troubleshoot it until fixed? And if I don’t figure out API Gateway it will be bothering me all evening. I should take control of my mind, – I was telling myself – I will be careful not to break anything tonight, and I will forget everything and enjoy the concert after, and I will be there if something breaks, – I was telling myself.

I talked to B about planning for the picnic: she was excited. Concert, picnic, whatever – planning is exciting for her. Picnic planning is a challenge; we gotta bring the lights, two blankets, a scarf in case it’s cold, etc. She was in planning mode excited how cool she planned everything.

Luckily by 5, I figured API Gateway: there was one permission and one route missed. Finally, it worked. It gave me some peace of mind for the evening.

The concert in Central Park was scheduled for 8pm. We got to a grocery store by 6, grabbed some Rosé, cheeses, and sausages, and then headed to the park. By 7 the park was pretty full already. We hardly found a spot for our blanket, pretty far from the stage. L&M couldn’t come cause of baby Ann, but R joined us. We chatted and listened to Beethoven, Mendelssohn, Rimsky-Korsakov, and some young local composers, the younger of whom was just 8 years old. B’s light on our picnic blanket was very charming when it got dark.

Note for next year: get to the park by 5:30 to find a better spot, just hang out there for the evening, bring a ticker blanket or a pad cause the ground is still cold, and don’t go to the bathroom right before the fireworks.

Comments

[juan_gandhi]

"Testing it all together" may be not the right idea, unless you tested it all separately before that. (Been there.)

[soid]

Ah, I know what you're talking about, that is true. But this is indeed the time to test it all together already after everything was tested separately.

[juan_gandhi]

I see; sure, an important step.