![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://aussie.zone/api/v3/image_proxy?url=https%3A%2F%2Flemmy.world%2Fpictrs%2Fimage%2F8f2046ae-5d2e-495f-b467-f7b14ccb4152.png)
I read an interview in the Democrat-Gazette with the daughter of Ms. Taylor, one of the victims. There are no words to describe how awful it must be to have one of your friends or family members just minding their own business only to be shot to death while checking out at the grocery store.
Ms. Taylor’s daughter expressed frustrations that she wasn’t there because she thought she could have done something, implying that she would have shot the assailant. In her defense, the woman’s grieving and people who are in that state tend to think and say all kinds of stuff.
But here’s the thing, the “good guy with a gun” mantra is idealistic at best. Even if you are a “good guy” with a gun, odds are that by the time you can even respond, the “bad guy” has already killed someone. Not to mention that in that very panic filled moment, there’s a much higher chance that you might accidentally shoot another bystander.
“Good guy with a gun” is not a solution to “bad guy with a gun” because no amount of bullets fired by “good guys” will bring back the people who are already dead.
Linqpad is awesome! Sadly, I don’t get to code in C# for my day job anymore but I still use Linqpad all the time. It’s main purpose originally was for building and testing Entity Framework SQL queries but it will run basically any C# code you plug into it on the fly.
Now, I primarily use it for testing out design concepts that end up getting translated to TypeScript. I also use it for validating the hot garbage that Elastic Search is serving up on a given day so I can send a nifty little report (Linqpad easily generates and exports tabular data) to the data team to show them that it is in fact their Elastic Search template that is an error laden dumpster fire rather than my code.
If you’re familiar with C#, F#, or Visual Basic, Linqpad is an incredibly valuable tool.