Design patterns? Data structures? Shit, just pass in a list or an assoc array, and maybe a function here and there
After trying to be relaxed about data structures in python, I can say that, IMO, this is more harmful than beneficial. Good types and structures lead to good code designs.
default values is one of my pet-peeves after using Python regularly. I wish more languages would let you just do something like def do_thing(arg=default_value) without hoops like builder pattern, function overloading, or whatnot
Intel said that with Lunar Lake, it aimed to "bust the myth that [x86] can't be as efficient" as ARM.[3] Analysis of tests performed on Lunar Lake CPUs available at market launch indicated that, although their multi-core performance was not particularly good under full load, their efficiency under everyday use was good, even if the ARM competition still has its advantages.[4]
yeah, I'm not sure I'd have believed this if my ex weren't the same. Seeing me concentrated would turn her on and I've never understood it. I guess we can't rationalize a fetish. She knew how to code too, though.
other solutions that implement similar policies are kopia and rustic
the advantage of using an off the shelf solution is that it's almost certainly more reliable than what anyone can come up with in a few hours, and, it works with incremental backups, so your space requirements are drastically reduced depending how often you run it.
in reality most (all?) states in the US don't charge progressively more for vehicle registration based on weight, and even when they do, the thresholds are really high. So a F-150 weighing over 5000 lbs may pay the same as a Honda Civic weighing half of that.
tbh if I couldn't install Linux as a software dev, I'd consider a different job