hbogert
Joined 560 karma
- hbogertThe tongue in cheek is strong in this one ^
- Geographically this is unpractical at some locations. Mild understatement. Do you happen to live in a year round sunny place?
- Do a git stash of working dir only after your git add -p. This was how the index/staging was meant to be used... I think
- It's okay to dislike both parties
- When you read your sentence:
> This stuff is popular in government or old businesses that may have been slow to (or unable to for regulatory reasons) jump to AWS/GCP etc.
I think it's fair to say that you think migrating to the hyperscalars is a thing a company should do. That's what my previous post was addressing
- The left and right signalling is such a waste of everyone's time and effort. Reactive pettiness
- you can shorten to:
> writing Terraform configuration, became absolute tyranny.
- The American hyper scalers are not necessarily the place to be. Modern can mean Non-hyper scalar as well. Can this sentiment just die please? Great that its working out for you and you replaced good sysadmins with aws admins, but it should not be the default strategy perse.
- The curse as a power user is that you want to know how it works. I let that feeling go with emacs. I've been happily using it since. My first gateway and killer use case was magit. Life with git will never be the same.
- Indeed, only eventual consistency. The article approaches this subject and mentions the use of the outbox pattern and/or using tools like Debezium.
- It was so freaking no-nonsense, loved it!
- you mean literally with code, or in spirit?
- If both sides abide by the rules a war couldnt have started
- It is truly wonderful. I do think they are missing a clear winner use-case so currently at our company colleagues don't see a clear benefit yet. Though if you take all use-cases where we use yaml or json now, and you'd get a pretty coherent way of working with config. But it's hard to phantom for non-coders and hard to communicate for coders why it's worth the effort for the non-coders.
- There was a time when this was the obvious thing to do when making systems. Sadly that's forgotten. Manpages to read on cli tooling is the same thing of course. Yet people rather go to another window, the browser, and go to a ad-driven website and get the same output as the manpage would give.
- > A big fuss about nothing. If you don’t pay for the IDE they will train on your data unless you opt-out and they will ask you if you want to opt-out _before_ they collect any data (on first launch after the update).
Not sure what I'm missing with spacemacs + LSP compared to vscode. (Spac)emacs does not train on my data. I don't pay for spacemacs.
- Acceleration is actually a thing. The CPU needs to ramp up cycles fast if it wants to feel snappy. It needs to wind down as soon as no significant workload is there anymore. All needed for good efficiency
- Dear lord my region was blessed with cable internet in 1995. Wasn't fast but it was really affordable and the latency was better than dial up. Though once it got crowded during peak hours it crumbled to a halt.
- This is the insight. You'll a worse job even for something as certificate management with letsencrypt. Let alone all the other stuff. If your workload doesn't need that, and you are fine with some downtime, then and only then don't do it.
- I was totally bummed out that despite buying a industry leader's product, a yubikey; I can't use it as a passkey through NFC on android[1]. It's simply not supported, wth. How can this work as a 2FA through NFC, but not as a passkey. It's easy to get into conspiracy theory mode, but this really feels like there's mixed incentives as Google wants to push their vendored passkey implementation.
[1]: https://developers.yubico.com/Developer_Program/WebAuthn_Sta...