I highly recommend installing fzf, and its shell integration. Makes your Ctrl + r magnitudes more pleasant to use!
vvv
More than that, your editor doesn't run with root permissions, which reduces the risk of accidentally overwriting something you didn't mean to.
it feels to me, like they're less looking for new people to start doing this "work", but more to connect with people who already happen to be enthusiastically going to events and showing off their laptops.
This is up there with left-pad now!
I really think that's the secret end game behind all the AI stuff in both Windows and MacOS. MS account required to use it. (anyone know if you need to be signed in to apple ID for apple ai?) "on device" inference that sometimes will reach out to the cloud. when it feels like it. maybe sometimes the cloud will reach out to you and ask your cpu to help out with training.
that, and better local content analysis. "no we aren't sending everything the microphone picks up to our servers, of course not. just the transcript that your local stt model made of it, you won't even notice the bandwidth!)"
Macy's now has a Toys Я Us branded toy department.
I don't know. I'm typing this in a razr 40 ultra with a shattered outer screen. on one hand, it sucks that it's shattered. on the other hand, I'm happy it has a second screen as a point of redundancy?
... but there is a way, and it has been proven.
One of the more memorable physics classes I've had went into the history of discoveries that led to our understanding of relativity. The relevant story here, starts with how sound travels though air.
Let's say you're standing at the bottom of a building shouting to your friend peeking out a window on the 5th floor. On a calm day, that friend will hear you at pretty much the same time as someone standing the same distance away, but on the street. However, if it's windy, the wind pushes around the air through which the sound of your voice is traveling, the friend up in the window will have a slight delay in receiving that sound. This can of course be verified with more scientific rigor, like a sound sent in two perpendicular directions activating a light.
Scientist at the time thought that light, like sound, must travel though some medium, and they called this theoretical medium the Aether. Since this medium is not locked to Earth, they figured they must be capable of detecting movement of this medium, an Aether wind, if you will. If somehow the movement of this medium caused the speed of light in one direction to be faster than another due to the movement of this medium, measuring the speed in two directions perpendicular to each other would reveal that difference. After a series of experiments of increasing distances and measurement sensitivities (think mirrors on mountain tops to measure the time for a laser beam to reflect), no change in the speed of light based on direction was found.
Please enjoy this wikipedia hole: https://en.m.wikipedia.org/wiki/Michelson%E2%80%93Morley_experiment , and please consider a bit of caution before you refer to things as facts in the future!
Are you using PersistentVolumes? If your storage class supports it, looks like there's a volume snapshot concept you can use, have you looked into that?
Not sure what you're doing, but if we're talking about a bog standard service backed by a db, I don't think having automated reverts of that data is the best idea. you might lose something! That said, triggering a snapshot of your db as a step before deployment is a pretty reasonable idea.
Reverting a service back to a previous version should be straightforward enough, and any dedicated ci/cd tool should have an API to get you information from the last successful deploy, whether that is the actual artifact you're deploying, or a reference to a registry.
As you're probably entirely unsurprised by, there are a ton of ways to skin this cat. you might consider investing in preventative measures, testing your data migration in a lower environment, splitting out db change commits from service logic commits, doing some sort of blue/green or canary deployment.
I get fairly nerd-sniped when it comes to build pipelines so happy to talk more concretely if you'd like to provide some more details!
Not even Chrome is blocking some of the add-ons...
is that something you know for sure? or has Google quietly complied with similar requests, without making a statement like Mozilla has here?
and it's potentially an existential threat.