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.

https://en.wikipedia.org/wiki/Open-source_software

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

Not having something in the first place and losing something you have are two different things. It’s like saying to someone who just lost their partner “don’t feel bad, for the first n years of your life you didn’t have a partner and you were fine”

Additionally, it’s not billions of years of nothing. It’s an eternity of nothing. Billions of years may as well be the blink of an eye relative to eternity.

God, I’m getting anxious just talking about it.

[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!)