And no, I have not tested it because I don’t know how I’m actually supposed to do that.
depends on what you backup and how.
if it’s just “dumb” files (videos, music pictures etc.), just retrieve them from your backups and check if you can open the files.
complex stuff? probably try to rebuild the complex stuff from a backup and check if it works as expected and is in the state you expect it to be in. how to do that really depends on the complex stuff.
i’d guess for most people it’s enough to make sure to backup dumb files and configurations, so they can rebuild their stuff rather than being able to restore a complex system in exactly the same state it was in before bad things happened.
technicaly correct, and i am no lawyer, but i can’t see how in the world i owe anyone a warranty that loads code on their machines, compiles it and uses it, all without any input by me.
everything that i intend to be more than throw away code, that lives for whatever reason in a public repo gets either an MIT or an gplv3 license.
Access control and offering a sound interface.
You don’t need getters and setters if every attribute is public, but you might want to make sure attributes are accessed in a specific way or a change to an object has to trigger something, or the change has to wait until the object is done with something. Java just has tools to enforce a user of your objects to access its attributes through the methods you designed for that. It’s a safeguard against unintended side effects, to only open up inner workings of a class as littles as necessary.
In a language without something like private attributes you’d have to account for far more ways someone might mutate the state of objects created by your code, it opens you up to far more possible mistakes.
I guess the biggest difference for users is that nostr relays don’t federate with one another. So you’ll have to query multiple relays yourself if you want to see stuff outside of the relay(s) you post to. The other big difference is that your identity is a keypair. The relays you send to only know your public key and that’s it.
E: someone running a relay could still decide you need to create an account or something, but this account is only the permission to use this specific relay. Your identity would still be your keypair, so moving to another relay is easy.
If null is a valid value for the field there is no reason why a builder should not construct an object where the field is null.
The only thing i dislike about the pattern is that a class utilizing the builder to retrieve the object has to know a lot about how the object has to be constructed, however it makes for very readable code imho.
I guess some lessons need to be learned through pain.
Yes, all those hurt. They sometimes still do, most of us are not machines that turn caffeine into code and we are never as clever as we think we are.
https://jsommers.github.io/cbook/cbook.pdf
Might be a good way for someone who is familiar with a higher level language.
Than there is of course “The C Programming Language” by Ritchie and Kernighan and “advanced programming in the unix enviroment” by stevens and rago.
So, i’d guess just get your feet wet with small stuff. Find out how to take arguments from the command line, or read a file, maybe programm a simple guess the number game. After you are more familiar with the syntax and so on you could look into using your c code in a higher level language. For python you’d have to look into ctypes for that.
Maybe something like x-com or phoenix point?
The only movement there is part of the battle
Or are you looking for a non stop gauntlet of fights in an old final fantasy style? Then some of those deck building /card battler games like slay the spire or night of the full moon might scratch a simmiliar itch, even if they are not party based.
sometimes i like that a lot of my work is typical enterprise stuff. nothing gets to prod without some poor soul working through a huge test catalogue on a seperate environment and/or a higher up signs off on it.
it’s also annoying because, you cant “just ship” a small fix or change without someone signing off on it.