tiramichu

Yeah. Soft furnishings like carpet, rugs, sofas and beds all feel a lot more "natural" to cats, as if they are outside on the grass, so they prefer to do it there.

Unlucky for us it's the absolute last place we want them to be doing it.

Tension, mostly

VSCode is by far and away the best thing Microsoft has ever done. (I'm sure therefore they will ruin it eventually, but that's a separate issue)

Its good for two main reasons IMO:

1. It is plugin-based

2. It is (therefore) language-agnostic

Plugins mean the DE starts as a very lightweight thing that is basically nothing more than a text editor. You can then add as much or as little as you want to get the level of features you are comfortable with but without being too bloated.

And then, because it's all plugins, you can work with any language and still stay within the same editor. Divine.

I personally love how lightweight it is compared to a full IDE because I don't like it when IDEs hide the magic behind UI. Press the button and it compiles huh? But how? What's going on there? What toolchain and commands are being executed?

I much prefer a good MAKEFILE where you know what your entry points are and what is going on, because it makes everything so much more portable and also improves your own knowledge and understanding.

Wireguard doesn't necessarily need to have those limitations, but it will depend in part how your VPN profile is set up.

If you configured your wireguard profile to always route all traffic over the VPN then yeah, you won't be able to access local networks. And maybe that's what you want, in which case fine :)

But you can also set the profile to only route traffic that is destined for an address on the target network (I.e your home network) and the rest will route as normal.

This second type of routing only works properly however when there are no address conflicts between the network you are on (i.e. someone else's WiFi) and your home network.

For this reason if you want to do this it's best to avoid on your own home network the common ranges almost everyone uses as default, i.e. 192.168.0.* and 10.0.0.*

I reconfigured my home network to 192.168.22.* for that reason. Now I never hit conflicts and VPN can stay on all the time but only traversed when needed :)

Don't wait. Do it now before your hand is forced.

And you can say no if you want to!

Tough one. I'd probably end up being the person who just kept politely listening while trying to shut down the conversation amicably like "well anyway" and "I must get cooking dinner now" and "my plants need moisturising" or something.

Neighbours are extremely high on the list of people I want to avoid pissing off, because a neighbour with a grudge against you could be an absolute nightmare (especially when you live in a townhouse and share walls)

I'm sorry you have to deal with that nonsense. And I hope you had a good day with your daughter

The same people who complain on Amazon reviews that the cable broke for "no reason"

No, generally speaking. But sometimes yes.

I would say that myself and most programmers appreciate there is always some logical root cause for why things work or don't, and its very unsatisfying to have thigs work without knowing why. It's also problematic, because if you don't know why then it might break again in future and you can't fix it.

That said, programming is different from pure science. The explicit point of science is to uncover the truth and understand and make it replicable. The point of programming is to have a software product that functions.

So realistically we may as programmers occasionally let something slide without knowing the full detail, because we are working to different goals.

This is especially true based on the category/criticality.

Something "magically" starts working in the core backend payments API code? Not good enough, we need to know exactly what the cause was and cover it in tests.

Something "magically" fixes the UI bug that caused a weird but inconsequential margin padding that affected Samsung Galaxy S21 devices ONLY and no other phone? Hallelujah, it's a miracle.

Maybe it's a really really small book

Right, so the hashing and comparison of hashes also can happen in the back end, and the API response can just be true/false whether it's a match or not. That way the hashes and the hashing algorithm could all stay private.

The comparison API would of course also need its own rate limits and backoff etc to ensure it cannot be used to bruteforce attempts until you get a 'true' back.

All in all it's a terrible idea though and nobody should actually do this.