Business continuity plan testing day.
Just chilling
Business continuity plan testing day.
Star spangled banner, autocorrect edition:
Oh Daddy can you see by the Dawn’s easily long What do probably we jailed add the Twilight last glowing Whoa being strips and bright state They’d the person force Or the ramparts we watched We’re so thankful streaming
And the tickets red flare The bonds busting in sure Have proof their the night That it flat was still there
Oh saw guys that day spangled banner yet and Or the leave of the few And the home of the brave
I wish this wasn’t so true.
I use Linux because of compiz fusion cube desktop. We are not the same.
Is there a language that anyone would say really does fare well for continued development or is it just that few people enjoy maintaining code? I’ve maintained some pretty old Go programs I wrote and didn’t mind it at all. I’ve inherited some brand new ones and wanted to rage quit immediately. I’ve also hated my own code too, so it’s not just whether or not I wrote it.
I have found maintainability is vastly more about the abstractions and architecture (modules and cohesive design etc) chosen than it is about the language.
It’s cool, you just have to drop a grand every year or two to enjoy that gorgeous screen. Think of it like a subscription to a 15% prettier screen for only 5x the price over 10 years.
Lol that makes more sense now that you clarify. I’ve heard great things about farm simulator too though. It’s certainly cheaper than a ranch.
For your actual question apparently fastfetch?
Get a remote job and do both until you know enough to quit tech?
The stupidest system is always the one I didn’t build myself. 😤
I say this in the engineering sense. I didn’t build capitalism please don’t hate me.
Yeah, for sure. And it’s already been forked. I have a feeling/hope that this might drive forks for some of the other popular software like consul.
Yeah, I think they meant IaC. IoC I’ve usually seen as “inversion of control” which is something else.
I think it was big for easy local dev setups in a VM. But I think docker has pretty much taken over a lot of those use cases since a build can happen in a container pretty trivially across platforms these days. Plus be ready to deploy with the same tools, which Vagrant didn’t cover.
Formerly open source company with a few really great projects. Terraform being one of the best known. Vault is probably the second most popular unless you go back when vagrant was bigger.
I’m definitely about to deploy it at home and replace vault just to be ready.
I think they’re just trying to take over. But yes.
Yeah, the image (not mine, but the best I found quickly) kinda shows a rebase+merge as the third image. As the other commenter mentioned, the new commit in the second image is the merge commit that would include any conflict resolutions.
Merge takes two commits and smooshes them together at their current state, and may require one commit to reconcile changes. Rebase takes a whole branch and moves it, as if you started working on it from a more recent base commit, and will ask you to reconcile changes as it replays history.
Or homeassistant. Or gitlab/github actions. So much yaml.
200G of packages is 200G I can’t use for games and media.