aberrate_junior_beatnik (he/him)

I’ve been using linux for 25 years and I can count the number of times I used vi to actually edit something on one hand. They will not “have to use vi sooner or later.”

It’s OK not to like and not use nano. It’s also OK to like and use nano.

It took me way too long to figure out what was wrong with this screenshot

How did the breaker not trip on that? It had one job

Not quite the same thing, but there’s a project that lets you use TPM to protect your host keys: https://github.com/Foxboron/ssh-tpm-agent

[edit: its primary function is to work with clients but buried in the readme it also explains how to use it for host keys]

This has placed the prime minister in a political vise. If he commits to postwar Palestinian rule in Gaza and begins acting seriously to establish it, he loses the far right. But if he commits to resettling Gaza, he loses the Israeli majority and the international community. And so, as he has often done in the past, Netanyahu has chosen not to choose

Oh, he’s chosen.

$375 million in today’s dollars would cover (adjusted for inflation) the marketing and development of Call of Duty: Modern Warfare 2. https://en.wikipedia.org/wiki/List_of_most_expensive_video_games_to_develop

Obviously taken to an extreme it’s bad, but I think it’s fine to have a function that can do one thing two or more different ways and ignore a certain parameter if one of the ways doesn’t need it. I’ve done some programming against the Win32 API and this is what jumped to mind for me, and I think it’s the typical case here. If I were designing from scratch I might split it into n functions that do it one way, but it’s such a small difference I wouldn’t fret over it. And of course making a change to the Windows API is an undertaking, probably not worth it in most cases.

Ok, but we all should admit: .net is a terrible name.

IMO the best way to ensure that traffic always goes through a VPN is to use network namespaces. The wireguard website has an article describing the process. In a nutshell, you create a dedicated namespace to put the physical interface in, create the wireguard interface in that namespace, then move the wireguard interface to the root (“normal”) namespace. That way the only way to get traffic out without the VPN is to run a program in that dedicated namespace.

Open-source software (OSS) is computer software that is released under a license in which the copyright holder grants users the rights to use, study, change, and distribute the software and its source code to anyone and for any purpose.

I had really hoped that by time we would finally have got beyond good & evil.

[Edit: upon reflection, this post went too far. To any who saw it, I apologize.]

Wow it must be an extremely novel experience for an iOS programmer to have a company arbitrarily make decisions about what you can and cannot do on their platform

The channel is Programmer Humor, not Programming Humor

My opinion: don’t sweat it, either way. I know that’s easy to say from the outside, but it’s still true. Do what you are most comfortable with. It sounds like you have plenty of ammunition if you want to put your foot down & insist on quality practices. Reject PRs that don’t meet best practices, and point to the internal docs you have. If the dev reacts angrily, blame the company & say you are worried about getting in trouble.

Or if confrontation makes you more uncomfortable, just let it slide. If the shit hits the fan, the senior dev is the senior dev. Just say you were following their lead.

Above all, remember that the company you are working for is not your friend and not your ally. Look out for your own interests first & don’t stress about work as much as possible (I get that’s easy to say and tough to do, but it’s still the best idea!)