[-] sarahasakura 2 points 1 year ago

No worries about having the time wrong, I was surprised when it was going to be starting around 5

A buddy and I were 3rd row, and I had a blast! I'll say up front I don't keep up much with either brand

Some of the match endings felt a bit abrupt, and there were a few mistakes made earlier in the show, but overall some good spots, a good surprise in the Douki v Callihan match, and a good crowd

[-] sarahasakura 1 points 2 years ago

I've been trying to ignore most of the news cycle, and enjoy the month. I've been out to my friends as "transfemme on the inside" for years but this pride I asked a small group to use she/her and the name "Sarah" for me

I've also taken time to explicitly be more femme, even if it's just been in the house

It's been a good month, even if it's been contained. My town has been supportive, but it's residents are a mixed bag - a small blip of acceptance in a pretty unaccepting area

[-] sarahasakura 1 points 2 years ago

My primary languages are Java (for work), Javascript (for work), and C/C++ (for hobbies). Earlier in my career, I used to use the debugger a lot to help figure out what's going on when my applications were running, but I really don't reach for it as a tool anymore. Now, I'll typically gravitate towards either logging things (at a debug level that I can turn on and off at runtime) or I'll write tests to help me organize my thoughts, and expectations

I don't remember when, or if ever, I made the deliberate decision to switch my methodology, but I feel like the benefit of doing things in logging or tests gives me two things. 6 months later, I can look back and remind myself that I was having trouble in that area; it can remind me how I fixed it too. Those things also can serve as a sanity check that if I'm changing things in that area, I don't end up breaking it again (at least breaking it in the same way)

With that said, I will reach for the debugger as a prototyping tool. IntelliJ IDEA (and probably other Java debuggers) allow you to execute statements on-the-fly. I'll run my app up to the point where I know what I want to do, but don't know exactly how to do it. Being able to run my app up to the point of that, then pause it and get to try different statements to see what comes back has sped up my development pretty well. Logging or testing don't really apply for that kind of exploration, and pausing to run arbitrary statements beats the other options in how quickly and minimally that exploration can be done

[-] sarahasakura 2 points 2 years ago

It's a good call - glad to hear you're taking care of yourself. Burnout can be really paralyzing

view more: ‹ prev next ›

sarahasakura

joined 2 years ago