tetha

54 ms·

691.
by tetha 4y ago
Interesting. This is similar to a common optimization in the genre of city builders with walkers, like Caesar or Pharaoh. In these games, buildings like a market or a temple spawn walkers, which walk on roads and distribute services and goo
692.
by tetha 4y ago
Something that could be very cool would be AI driven monitoring analysis and troubleshooting pre-work to support operative staff. Trying to figure out what's exactly going wrong in a complex, distributed system requires the system and
693.
by tetha 4y ago
I've also been wondering if this isn't similar to the boiling frog idea, just on its head. Practically speaking, I don't think I made huge, noticeable progress in my guitar skills over the last 4-5 days, at least I couldn&#x2
694.
by tetha 4y ago
Agreed, I would have expected this to fail shut and require some flag to function. Inconvenient, but in this case, I'd prefer to be inconvenienced and safe rather than conveniently owned.
695.
by tetha 4y ago
This is something I've put into most workflows at $(WORKSPACE=/=heroku) that end up disabling a customers systems. It depends a bit on how hard we have to kill a system for various factors. But for the softest setting, we usually
696.
by tetha 4y ago
I was about to comment too. I'm noticing this very strongly e.g. in my early endeavors in music (2-3 years into the bass, 6 month seriously into the guitar after getting the neck aligned) It sounds trivial, but if you can't solidl
697.
by tetha 4y ago
I would overall agree with this, tbh, and having an understanding of this makes my work place tick. Our team lead - a real strategist - can take very abstract company goals, of "reduce cost, and increase profit, but mostly be more effi
698.
by tetha 4y ago
Put the system into single user mode 15 minutes before disaster. Update all filesystem times and the HW clock to 0 offline. Reboot a couple of times 30 minutes later and fix the timediff in APIs surrounding the system. Easy going. I think I
699.
by tetha 4y ago
We recently had an ad-hoc experiment like this as well "give us basic config management code to download a service, add a systemd service for it, deploy a config and setup reloading of the service" And it had some funny mistakes i
700.
by tetha 4y ago
Yeah. I've been ranting about a similar thing in the context of jsonwebtoken to our security guy some days ago. The vulnerability pretty much goes "Well if I can inject an object with a toString() method of my choosing into your r
701.
by tetha 4y ago
Ah. So it's a referential thing? If we had some absolute zero reference outside the universe - let's call it a great alien petri dish - we probably could find something moving faster than the speed of light, in reference to that a
702.
by tetha 4y ago
Yeah. For our ops-documentation I also have more of a bottom up approach of keeping it stable, which has resulted in the company having two documentation standards. Pretty much all of our docs, and everything concerning more than one team i
703.
by tetha 4y ago
Agreed. I very much like my workplaces approach atm, which I jokingly call medium-sized services, mostly. Due to acquisitions, we have 6 or 7 big messy monoliths and actually, 3-5 infrastructure stacks. This in turn means, we have something
704.
by tetha 4y ago
You can find the original writeup here: https://unit42.paloaltonetworks.com/jsonwebtoken-vulnerabili... It's pretty much yet another one one the pile of object deserialization vulnerabilities.
705.
by tetha 4y ago
> When you say "without coordination", does it mean simultaneous backups from several machines to the same repo are possible? It is, with a bit of (other) coordination. Basically, only one process can actively write to a borg r
706.
by tetha 4y ago
Yes, all hosts accessing the borg repository need the encryption keys or the passphrase of the repository, since it relies on the homomorphic encryption of the repo. And yeah, we tend to partition our borg repos along functionality and need
707.
by tetha 4y ago
Maybe I'm misunderstanding, but the deduplication of Borg happens at a repository level and after the client-side encryption. If several hosts are pushing archives containing the same files (or rather, file contents) into the same repo
708.
by tetha 4y ago
Indeed, very much this. We spent some efforts structuring this at work and now we have 2-3 rules in place. First off, all requests for work and services are always issues either directly in the ticket system, or via mail to a central mail a
709.
by tetha 4y ago
As much as I approve of a skillset to analyze local logs, but after a relatively small scale (10-20 systems), a central decent log aggregation like opensearch or ELK just brings so much value even on 1-3 nodes. It'd be one of the first
710.
by tetha 4y ago
This is true. The issue is that already a relatively small nuclear weapon is perfectly sufficient to wipe out most to all civilian structures. However, it does so in a roughly circular area, and you need to increase the initial explosion a
711.
by tetha 4y ago
Very much reminds me of the stories of my dad how they'd have to start really big bulldozers back in the day of draining german marshes. You'd first hand-crank a small generator to fill up a small battery for the electric starter
712.
by tetha 4y ago
Yeah. And it becomes silly the other way around as well. Take the WadjetEye adventures. People complain that the games are just 4 - 8 hours long. But on the flip side, it's 4 - 8 hours filled with charm, content and gameplay. It doesn&
713.
by tetha 4y ago
That reminds me of the old movie Mimic, in which supposedly sterile insects are released to prey on other insects transmitting a disease to children. The infertility part didn't work and it got messy.
714.
by tetha 4y ago
After dealing with devs, customers, account managers, security guys on the customer side and such a bunch, I'm starting to realize something that's tricky. If you don't know a concept exists - or it slips your mind - you cann
715.
by tetha 4y ago
That makes no sense to me either. In my book, tests in a software project are largely responsible to check that desired functionality exists, most often to stop later changes from breaking functionality. For example, if you're in the p
716.
by tetha 4y ago
> This whole notion of "documentation can get out of sync with the code, so it's better not to write it at all" is so nonsensical. To me, this feels similar to finding the correct granularity of unit tests or tests in gene
717.
by tetha 4y ago
A good rule of thumb I've heard about a few years ago: Assume you're explaining this chunk of a system to a team member standing next to you. Write that down. And don't worry about the tone feeling casual. And once or twice a
718.
by tetha 4y ago
You jest, but we've had weeks during which - out of 6 people - one was on vacation, two were sick, and then two more had to call in child-sick because their respective day cares had to close due to positive covid tests. And suddenly yo
719.
by tetha 4y ago
Additionally, a team of one has no redundancy. You know, how Bob is responsible for maintaining the business critical databases, and now the databases are on fire and Bob is on a canoe tour through Canada without a phone. Oops. For business
720.
by tetha 4y ago
There is russian kmem-roulette[1] - dd if=/dev/urandom of=/dev/kmem bs=1 count=1 seek=$RANDOM 1: http://bash.org/?926695

More ›