There are certainly different kinds of developers writing different types of tests. I usually only write the tests first if I‘m adding a critical functionality to some method or function already present.
However having automated tests can help you when you can‘t easily understand the code or when you want to refactor that code to make sure you‘re not breaking existing functionality.
What you‘re describing with external devs often happens when these devs can‘t access the real data - plus you often want these tests to be automated, which usually brings with it the requirement of atomicity, i.e. you want one test run running in parallel with another not effecting each other. That usually doesn‘t work well with a real database (unless you really take your test engineering to the overengineered tier).
Another point to keep in mind - many distros now ship Podman instead of Docker, with Fedora being at the forefront of that change. If you‘re currently running Docker, you might want to check if your setup is drop-in compatible with Podman as some images will not work (usually related to permission or user switching, privileged ports).
To get nginx ingress to use the external clients IP, you can configure the ingress controllers traffic policy. Using the helm chart, I used these values:
yaml
controller:
service:
# this has a bunch of downsides, but allows source-ip based access white/deny listing.
externalTrafficPolicy: Local
For the ingress IP, I configured metal-lb to receive traffic on a static IP (using IP4AddressPool and L2Advertisement CRDs from metal-lb), which is then used for the port forwarding. I’ve never tested it because I only have a single worker node, but I expect the metal-lb controller will continue receiving traffic to that same static IP if a node goes down.
Having weak security on your operating system certainly isnt helping when there is some sort of exploit in a browser running on that system. The perfect operating system may not prevent issues inside your browser, but it may limit the damage these do.
I feel like you suggest using Linux reduces security - why do you say that?
What is an unofficial ChatGPT API supposed to be? One where you dont have to pay? I‘d hazard a guess that if that exists, it would just be a wrapper around someone elses API token, for which they are paying. Questions is whether they know about that usage…
I think the NPCs did that in KCD1 if you were dirty, had high charisma but a fancy armor or similar. It feels like it works similarly in KCD2, since their demeanor changes significantly when switching from peasant clothes to a proper armor. Don’t have knights armor or any other fancy outfits yet though, so I can’t tell for KCD2.
No. But the arrow tip points towards the center. Weapon sway makes it nigh impossible to aim on the controller.
I can’t relate to KCD1 since I played that on PC.
Yes, you don’t want to fight against more than one enemy, the game even has a tutorial with a stylistic drawing of you lining up the enemies in a line, so that only one can engage you at any time.
I managed to pull this off with two enemies, with three you would need to tank some hits.
To be honest, it’s still a little hectic for me, but I feel the most notable change is that you can avoid being countered / masterstriked. By positioning your weapon, you can block, perfect block (allows you to strike back) or masterstrike which remains unblockable.
There is now an interesting back and forth between blocking, striking back and being blocked, which can go on forever - until someone has no stamina left or someone pulls off a masterstrike.
I would always recommend good old Debian for a mostly „it just works“ experience. You‘ll find debian packages for most if not all the things you mentioned.
Alternatively you could go the steeper route and use an immutable OS like Fedora CoreOS or Fedora Silverblue for a more desktopy experience.
Hardware wise I‘ve been told the Intel NUC kits work wonders, or similarly specced boxes from Asia. You might get like 32GB RAM, a fairly recent CPU for <400€. Personally I‘m using a 12 year old Mac Mini until it dies, running debian.
63.03% rejecting it is less than I had expected. I was expecting 70% or more, so maybe there is hope for the matter to be reiterated upon in the coming years.
Most likely CD is intended to mean continuous delivery, which commonly means automation in processes that deliver your software to it’s target audience.
There are certainly different kinds of developers writing different types of tests. I usually only write the tests first if I‘m adding a critical functionality to some method or function already present. However having automated tests can help you when you can‘t easily understand the code or when you want to refactor that code to make sure you‘re not breaking existing functionality.
What you‘re describing with external devs often happens when these devs can‘t access the real data - plus you often want these tests to be automated, which usually brings with it the requirement of atomicity, i.e. you want one test run running in parallel with another not effecting each other. That usually doesn‘t work well with a real database (unless you really take your test engineering to the overengineered tier).