in 3e, the tarrasque had regeneration, and couldnt die from negative HP. So the idea of building a town that “farmed” an unconscious tarrasque for its meat/bones/whatever was a popular thought experiment for a setting back in the day. IIRC there was also someone who took the idea and published it as an actual book at some point too (which honestly felt kinda scummy to me, since it was basically a big community project/collaboration)
As an interviewer, I think that certs are only useful if you take the test with a different company than you studied with. So I don’t think I’d care if you have a coursera cert, because I’d assume it just meant you finished the course that you paid for.
It’s worth noting that some coursera courses are created and maintained by actually accredited institutions, and some courses qualify as college credit with ACE accreditation. Also, many tech certifications host their courses on coursera too, like microsoft has official azure cert courses on there.
That doesn’t necessarily mean anything for any given random cert, though, because that means that the entire site is a pretty big grab bag in terms of the usefulness of their certs.
Depends on the person. It’s very “old school” in it’s gameplay, and very hard and punishing, grindy, has perma-death, etc.
I’d think most modern gamers would hate it, but I personally like wizardry to games (though it helps that I’m old enough to have played older versions). If you like old school d&d, it’s very much in the same vein. The remake linked here is pretty good, I already own it from early access.
However, if you ask me to pick one specific project, I get overwhelmed because I don’t know what’s reasonable.
I don’t know enough to know if my ideas are achievable, or if I’d just be bashing my head against the wall. I don’t know if they’re laughably simple tasks, multimillion-dollar propositions, or Goldilocks ideas that would be perfect to learn a coding language.
List out some ideas you’re thinking of. While it may not be obvious to you, someone who is seasoned (me or someone else) might notice at least a general theme or idea to point you in the right direction for where you should go and what you should learn, regardless of if the projects are reasonable.
Note - Most projects take teams to realize, so if your ideas are too large, they might not generally be feasible alone.
Recommend you check out dungeon world. It’s fairly rules light, it’s got a d&d feel, and you have all your “regular” d&d style classes.
It’s a “powered by the apocalypse” system, which means it utilizes a 2d6 rolling mechanic that leans towards success.
That is, generally speaking, it’s a graded scale. Roll 2d6, add modifiers. under 6 is failure, 7-9 is a “medium” success, and 10+ is a “great” success. It leans towards success because the average of 2d6 before modifiers is 7, the lowest success number.
One thing that might trip you up running it (I know it did me), is that enemies don’t get a “turn”. The enemy turn is essentially the player’s failures. You go in to attack and roll a 6? The enemy parries your attack and counters you.
Running arr services on a proxmox cluster to download to a device on the same network. I don’t think there would be any problems but wanted to see what changes need to be done.
I’m essentially doing this with my set up. I have a box running proxmox and a separate networked nas device. There aren’t really any changes, per se, other than pointing the *arr installs at the correct mounts. One thing to make note of, i would make sure that your download, processing, and final locations are all within the same mount point, so that you can take advantage of atomic moves.
i second the comment that you need to consider why you want to do this. You generally need a pretty good reason to split your codebase into multiple languages.
As far as actually doing it, you have a ton of different options, some of which have been mentioned here. Some i can think of off the top of my head:
basically every approach is going to require you to come up with some sort of API that the two work together through, though, an API in the generic sense is basically a shared contract two disconnected pieces of code use to communicate.