watercolorblind

I'd say shadowrun.

Thank you for the backup link! I hadn't known he had passed, and I didn't expect the link to fail. I first read the story back in 2008 or so, and it's been one of those works that lodged itself in my mind so it's sad to hear he died.

Comfy shirt to wear during yard work, working on the car, painting a wall, or laundry day around the house. It's reasonable to me.

The primary pain point I see here is if devs lean into transactions such that their job is only created together with the everything else that happened.

Losing that guarantee can make the eventual migration harder, even if that migration is to a different postgres instance than the primary db.

As someone who has been quite hard on myself too:

To err is to be human. If you minimize your life to minimize negative impacts on others, you are hurting yourself (and your friends and family). If you make a mistake, learn from it and try to be better. None of us are born with the skill and knowledge to do the right thing all the time, and sometimes there is no right thing, just different tradeoffs with different costs.

When your health data can say you are trans, and the government decides to persecute you, then yes, it important to maintain privacy.

Maybe a uniform tax credit/refund for each citizen that is covered by that level of government. We the citizens can then decide if we fix the issue or continue to generate fines, but at least the budget isn't expecting revenue that could disappear (like the lack of traffic tickets during the beginning of COVID).

A physically impaired person can be a good yoga instructor: they'll suggest alternatives, different/better cues, or provide more accessible classes such as yin or seated yoga.

Just because they are physically impaired now doesn't mean they were before, and an instructor won't necessarily move through the poses with the class since they can have 2-3 classes per day.

We would need ruby support too.

Beyond that, if my MR/PR has two (or more) logical commits, will the tool support reviewing each in isolation? Often times, I will do a refactor in the first commit, and have a second commit with the new feature that makes use of the refactor. Reviewing it all together can result in muddying the water.

Another thought: if I edit a function to call a different function defined elsewhere in my codebase, is there a way to include that functions definition into the canvas (either by the author in preparation for a reviewer, or by the reviewer) to facilitate verifying the behavior across this new boundary?

Some other examples: DragonRuby, and Chef (which I prefer over ansible).