In the mild case, the common side effects are blunting of your emotions
Isn't this the primary effect, more than a side effect? Atleast in my case, it's been super helpful, going from jumping between a 1 to 7 in mood, to just lie around 4-5-6.
HN user
In the mild case, the common side effects are blunting of your emotions
Isn't this the primary effect, more than a side effect? Atleast in my case, it's been super helpful, going from jumping between a 1 to 7 in mood, to just lie around 4-5-6.
Distracted me from reading the article, I just started chasing other people around.
Recently finished The DevOps Handbook[1].
Had a lot of nice insight into good ways of doing DevOps, and I found the examples from real companies incredibly helpful in understand how the concepts help in the real world.
Reminds me of Bocker[0]
Lots of examples without the entire OS as other comments mention, an example would be Googles distroless[0]
I have such a fear for this, that things i invest time/energy into today will be obsolete in half a year, and my time would be essentially "wasted".
As others say, learning the fundamentals will, and trying to get some more general skill out of every tech fad.
(although, full rewrite every 6 months is excessive imo)
I absolutely love how easy it was to capture requests through ADB with your tool, only solution i could find which just worked out of the box.
Motivation is money, the proxy site is serving their own ads.
According to OP, it ranks pretty well on bing.
Does anyone have any experience running kubernetes on hetzner? We're currently using DOKS, but are strongly considering setting something up on bare metal servers, as digital ocean are rather expensive (compared to hetzner that is)
I've been using SonarLint[0] for a while for this, as it not only finds code smells, but also if i do things in a weird way, like doing for(i=0;i>array.length-1;i++){console.log(arrray[i]} instead of just doing for(const element of array).
If nobody watches me play video games, what is the point?
That i enjoy it.
Some people enjoy doing art.
Planned for 3.12
Simple "JIT" compiler for small regions. Compile small regions of specialized code, using a relatively simple, fast compiler.
https://github.com/markshannon/faster-cpython/blob/master/pl...
I recently wrote my first PAM module, using pam-rs[1] so i could do it in rust.
It was a learning experience, a rather enjoyable one though. While going down the rabbit hole, I feel even deeper when my module kept halting in openssh, due to a bug[2] from 2018.
I didn't really feel the pain of debugging the author had, most likely just because my application was simple enough to be tested via log statements though.
[1] https://github.com/anowell/pam-rs [2] https://bugzilla.mindrot.org/show_bug.cgi?id=2876
I've only had one experience with azure support, Back when i was first getting into cloud/playing around with servers, I had forgotten to shut down the VPC i rented there, and I ended up with a bill of ~100$, which is a decent chunk for a student.
Wrote to support, explained my situation, and they removed the bill without any hassle.
My credentials are deactivated when I'm not using them.
This sounds rather interesting, mind elaborating how its done? How would they activate when you use them, but not if anyone else does?
I've been using dnsmasq [1] instead of DHCPD, and it's been fairly easy for me (the built in TFTP server made PXE super easy)
It does also seem like the reporter was extremely careful as to not accidentally access user data
After seeing the pings, I immediately turned off the replication by executing the redis command REPLICAOF no one\n\n. No information from your redis server has been replicated to mine as I used nc and I got only the ping messages.
ofc it's real. They're saying "at this date, we wont update it anymore". The router still works, it just isn't updated anymore.
If i had an old product, there's also some point where i'd say "I wont be updating this anymore", as to phase it out. Expecting something to receive active support forever is unreasonable.
I totally agree, and stopped buying cisco a long time ago. 5 years is too short, i think i've had my current router for 10 already.
The EOL sucks, but that's what people kinda signed up for with Cisco.
I mean, isn't it quite reasonable to not update something post-EOL ? (router EOL of 5 years seems a bit short though)
When cryptopals is mentioned, i've also gotta mention "Cryptohack": https://cryptohack.org/
That's where i've learnt most of my crypto, although it might be more focussed on the breaking than the making part.
I wouldn't really show off nemid/mitid as a shining example for digitalization in Denmark. Mitid came out already with security issues[1].
I do agree that the 20-30 years behind is a gross overestimation, but acting like we're a shining example of modern IT is a stretch as well.
[1] https://www.version2.dk/artikel/eksperter-saar-tvivl-om-sikk...
I know this happened a lot with Sonic Forces.
At work we're running some self hosted service, issue is, the service is quite old, and the client only works with other old openjdk versions, so the vm runs the client.
I'm also running android-x86[1], for a single mobile game with an x86 port
I've spent quite some time on things like cryptohack, and speaking to my cryptography friends, but ECC has never actually stuck as well as this does.
Brilliantly done!
Guess it depends on how you define a significant gap, 1 year? 5 years?
Also working doesn't necessarily equal keeping up with technology. If i'm maintaining some legacy system, I wont have a gap but i might've not learnt anything new for years.
Using it for k8s currently, in a request like
[{"op": "replace", "path":"/spec/template/metadata/annotations/restarted-at", "value": "'$(date -Iseconds)'"}]
to restart/redeploy.
I'd say we get more out of meat, having delicious stuff to eat is awesome.
That part is just about the naïve C
As a completely new admin, could you elaborate on "be very careful with volume mounts"?
In the k8s env I run, the filesystem is backed by ceph, which creates persistent volumes that the different pods can claim. Is it just "be careful not to mount docker.sock"?