Daily Coping 27 Jul 2021

I started to add a daily coping tip to the SQLServerCentral newsletter and to the Community Circle, which is helping me deal with the issues in the world. I’m adding my responses for each day here. All my coping tips are under this tag. 

Today’s tip is to see something good about something that went wrong.

I was coming home from vacation recently and our flight got delayed and delayed. We went from a 2 hour, to a 3 hour, to a 5 hour delay. Then the flight was moved to the next morning, early at 6am, which meant we needed to find lodging and get up incredibly early.

After quite a few hours in the airport, we grabbed a taxi and went to a hotel. No reasonably priced hotels nearby, so a much longer ride than we wanted, no restaurant at the hotel or anything close, and by the time we arrived, we were only about 8 hours from needing to leave again.

Easy to complain and be upset. It was better to appreciate that I got another night with my wife away from life, and we could afford to deal with the issues, and we’d gotten some food at the airport earlier and had some snacks in bags. We’d seen friends in the airport and had time to chat with them, which hadn’t happened much this past year.

Looking at the positives reduced stress and reminded me that life was good that day, even with a few bumps in the road.

Posted in Blog | Tagged , , | Comments Off on Daily Coping 27 Jul 2021

The Post Pandemic Office Experience

I traveled to Pasadena, CA this week to work with a few other Redgaters in an office. There was a get together planned this week for the entire staff, many of whom have not seen each other in a year. Some have never met. When I heard about this, I requested permission to go. My request was approved, and I spent a couple of days in our LA WeWork space.

I had mentioned I was coming in our Slack channel, and reached out to a few people, hoping to get some people in the office while I was there. I flew out early one morning, with a view I hadn’t seen in a long time.

20210721_094016

I enjoy flying into LA, crossing the mountains and desert, seeing landmarks along the way, watching the transition from nature to very developed (and large) city. It always makes me smile. In this case, I arrived and quickly got a Lyft up to the office. Along the way I had gotten a note from someone that masks were needed in the common spaces, and a few phone numbers to text for admission.

I wasn’t sure what to expect, as I’ve seen various incarnations of co-working spaces. In this case, WeWork is a large space that’s been cut down and separated with lots of glass walls. There is a lot of security in our building, and I needed someone to use a card to activate the elevator, as well as leave the elevator lobby area. Inside, there are lots of small offices, containing 1, 2, 4, or more desks. While it’s a space where you can see far through the glass walls, it’s also small as there are lots of walls.

Here’s an example of a larger space, with 5 desks, but I saw plenty of much smaller offices with 1 or 2 desks.

20210721_150957

Redgate has their own space, which is separated from others. Almost all offices have a separate key card entry system.

20210721_152106

My first day, there were 4 of us in the office. I knew them all, and I contact them regularly on Slack or in Zoom calls, but it was nice to sit and be able to chat with them in person. Inside our offices, we didn’t have to wear masks, but the coffee machine and bathroom were outside, so I kept mine handy in a pocket.

We did have a small snack area, which was nice. It felt a little abandoned though, with few of us around.

20210721_152121

There were really 4 separate areas of desks, and I had one to myself. I almost started to set up next to someone, but then a few people got on the phone and I realized how loud it can be. All the glass and relatively low ceilings make it hard to work in a group, at least in our space.

20210721_111949

We went out to lunch, and took some breaks to talk about work or life, and it felt normal, albeit rather limited with so few people.

The second day was better, with about 10-12 people in the office. It was much louder and a little harder to work, but it felt like a busy organization again. I liked it, and was glad I had the chance to experience it.

As with many things during this pandemic, things changed. There was an order from the Pasadena Health Department that took effect between my first and second days noting that we had to wear masks, even in our own space. Annoying, but not that much of a problem. I suspect that might keep some people from coming back, or at least make them think about coming less frequently.

We also had a get-together at a local pub. We were outside, and most of the California staff came. It was interesting in that 8-10 were people no one had met. People hired during the pandemic, who had been working 100% remote while with the company. That was a little strange, but it’s how life goes.

We talked, laughed, and appreciated the time to get together. I realize that I do enjoy going to an office some time, and I’m hoping I’ll get back to Pasadena 2-3 times a year. It was a good trip, long and tiring for me with two early flights, but great for my mental health, and a way to catch up with people that I haven’t seen in a long time.

I hope more people come back, at least part time, as it seemed we all missed the chance to get together and talk.

Posted in Blog | Tagged , | Comments Off on The Post Pandemic Office Experience

Do You Have ALL the YAML?

YAML is a file format, and as with many formats, some of us love them and some of us hate them.  It seems to be better than XML in many ways, and perhaps easier to deal with the JSON. It might not be better than csv/tsv/delimited formats for large transfers but for many of us, it’s a nice format for configuration items.

While the format felt fairly intuitive to me, and it’s not hard to write, it is quite persnickety about whitespace. This makes using some plugin, like the Red Hat YAML extension for VS Code, important to help you prevent mistakes. Even as easy as the format can be to read and understand, it’s also easy to make mistakes with the whitespace as you indent and try to add subkeys.

I was watching an AWS talk, and there was an interesting note about using YAML for control planes and being sure that you have some sort of checksum if you do. Why? Because you aren’t sure if you have the entire file. A YAML file could be truncated in any file transfer, and it would still appear to be valid. Hearing that made me realize that those annoying closure tags in XML and JSON might have some value.

Those of you that work with YAML, how are you sure you got the entire file? Is there something you’d program in? Do you checksum the file and pass that along? Do you include a required, closing key:value tag of some sort? I don’t, but I might think about doing so in any place where an invalid or incomplete file might cause me problems. This certainly seems like something you’d want in a control file, like one used for Kubernetes.

In most cases, we assume if we can read a file, then we have the complete file. I don’t know of many customers that require some sort of checksum or validation for a file. Certainly, if a CSV or TSV was missing rows, the file might still appear valid to an import process. XML and JSON should have a closing tag or character, so we’d hope we could catch this, but maybe not.

Moving around data through files, especially data used to drive processes, should include some error handling. That would mean that we have some way to detect if part of our file is missing. There are ways, but it seems that in many cases we’ve gotten lazy about implementing them in file transfers. Certainly, I don’t see people adding a checksum to their YAML files, which seems like something that we’d want to require.

Steve Jones

Listen to the podcast at Libsyn, Stitcher, Spotify, or iTunes.

Posted in Editorial | Tagged | 1 Comment

Daily Coping 26 Jul 2021

I started to add a daily coping tip to the SQLServerCentral newsletter and to the Community Circle, which is helping me deal with the issues in the world. I’m adding my responses for each day here. All my coping tips are under this tag. 

Today’s tip is to remember a tough time during the pandemic and how you got through it.

The pandemic seems to be easing for me the last month, so I’m definitely coping better. However, I talk with people around the world, and their experiences often remind me of how life was months ago for me.

One of the tough times I had in the last year was last fall. I friend died from COVID, I got the disease, and Colorado locked down quite a bit more than we had before that. I couldn’t go places, visit people, and even my coaching outlet shut down for awhile. There were some days in the late fall when things felt hopeless. I knew they weren’t, but to me, I was struggling to be positive.

One thing that helped me was talking.

I don’t do that well, or often enough, with those close to me. I especially don’t share my struggles well, but I learned to share more with my wife, and she supported me. I talked with my kids, and a few friends, getting them to remind me of good things, to try and find ways to get me to smile, relax, and find hope.

It worked, and many things got better in life and the world.

Posted in Blog | Tagged , , | Comments Off on Daily Coping 26 Jul 2021