I think this is a strong case for being ‘overemployed’; sorry I couldn’t make the drive (while doing my other/actual job)
I think this is a strong case for being ‘overemployed’; sorry I couldn’t make the drive (while doing my other/actual job)
That and a rotating menu likely adds overhead costs as it prevents you from specializing (skills, equipment, and ingredients acquisition)
Rust’s cargo is great, I’d say it would be best to make the switch sooner rather than later once your code base is established. The build system and tooling alone is a great reason to switch
Honestly executives and board members who receive performance bonuses and golden parachutes should carry extra liability, such that these perks can be denied or even clawed back (and used to help the damages) when their decisions have these sort of outcomes. Nothing wrong with making more when things go well, but if you’re going to take a larger piece of the pie, then you need to be prepared to take a smaller piece when things go wrong (aka, cut executive pay before layoffs, etc.).
I never received this survey and I fly Southwest specifically because I found their boarding process to be less of a hassle (for a single traveler who doesn’t care where they sit). The only way I could see this being beneficial is if they board people in order of assigned seat in such a way as to optimize time to seat, not the BS boarding that other airlines do to try and maximize price of fair, otherwise they will have lost the whole reason I like(d) to fly them… Their simplier, no bs, boarding process.
P.S. I really don’t get people liking to pidgen hole themselves to a specific spot for any of these things, just makes it easier to inflate the prices later
Darn, I missed it, about halfway down
Do they say what state or are we supposed to just know this is Virginia?
This sounds odd to me, unless you connected to an Ethernet port behind a desk or somehow forced open a network closet… They also might not like it if you disconnected one of the public computers to use its cable/port; otherwise if this was an open and public port, you used it as designed and the librarian probably has watched too many Hollywood hacking movies. I have to admit, I never thought of this as a way to bypass the captive portal (sorta just assumed everyone going through the public network would have to hit it, kinda of the equivalent to having everyone sign a liability waiver).
With that said, I can see some institutions not liking connections that aren’t part of the more traditional/commercial networking (but it doesn’t sound like the library took issue with your traffic, just the librarian didn’t like the PHY link you chose to use). For the SMS thing (I haven’t seen that used in a while, you might be able to use some sort of burner number app if they don’t filter them).
SEEEEEEE!!! I told you
I usually wear deodorant (which generally has an antiperspirant in it), but there are days when I don’t/haven’t; in this limited experience I’ve noticed I would generally smell worse if I haven’t been active. It seems like being up and moving around and sweating from ‘labor’ rather than sitting and sweating (not sure how to word that) is less likely to significantly smell. With all that said, I do try to shower after the gym or when I return inside after working on significant outdoor projects.
P.S., another data point to consider is the individual’s age, as hormone levels (generally tied to age) could also influence perspiration
It sounds like git-annex to me (doesn’t have to be 3rd party hosts, you can combine your own systems) where it allows decentralized file management across all your devices. I’d also be curious to see how they handle offline backup/file tracking and the sneakernet use cases (something git-annex supports). As it sounds like it is a true filesystem, it could be a nice upgrade assuming feature parity (one gotcha with git-annex, is since it is using git, you can’t easily have other git repositories inside of it).
Ticks are terrible; creepy just as little things that get on you, but then they also carry all sorts of diseases which really drives up the paranoia after every hike
The concern for code duplication is valid, but as the article mentioned it is also a while off until the Nova project is mainlined. I honestly never thought of how the work to bring in Rust to mainline may in effect lead to a more complete deprecation of older hardware as we start to change API’s older/unmaintained components aren’t updated. On the flip side, trimming out older stuff might save maintainer work going forward.