The older I get, the less time passes between starting a new project and reading the readme / manpages for a library.
The older I get, the less time passes between starting a new project and reading the readme / manpages for a library.
Huh, I’ve only heard business logic before.
You just need a little Tenacity.
Was going to mention this. Finding a smaller community focused on a specific project can afford more collaborative learning while contributing to projects that need help. It’s also a good way to learn humility, like finding that one person in the corner of the office who constantly picks apart your PRs without any emotion or judgement and genuinely improves your own code by learning from mistakes.
For clarity, the recommendation is specifically 3 copies of your data, not 3 backups.
3-2-1 backup; 3 copies of the data, 2 types of storage devices, 1 off-site storage location.
So in a typical homelab case you would have your primary hot data, the actual device being used to create and manage that data, your desktop. You’d regularly backup that data into warm storage such as a NAS with redundancy (raid Z1, Z2, etc). Followed by regular but slower intervals of backups to a remote location, such as a duplicate NAS with a secure tunnel or even an external drive(s) sitting at a friend or family member’s house, bank vault, wherever. That would be considered cold storage (and should be automated as such if it’s constantly powered).
My own addition to this is that at least one of the hot / warm devices should be on battery backup in case of power events. I’ll always advocate that to be the primary machine but in homelab the server would be more important and the NAS would be part of that stack.
Cloud is not considered a backup unless the data owner is also the storage owner, for general reliability reasons related to control over the system and storage. Cloud is, however, a reasonable temporary storage for moves and transfers.
Yeah I found which key and that has been a little more useful than nothing, but it’s a half-way solution, like showing shortcut next to menu items in a normal GUI application. Thank you for the suggestion!
This is me wondering… is there anyone who curates and categorizes lists of open source projects actively looking for contributions? Possibly with an organization based on experience level? It’s often hard to tell what project are active enough that entry, intermediate, or experienced level help is needed and for what.
Frogs rule!
I really wish rider would respect when I turn it off. It just keeps re-enabling itself.
I do this with cold milk or creamer when making hot chocolate. Make a nice paste by continuously mixing it while waiting for the water to boil is plenty good enough and makes it much tastier!
Tell that to Microsoft!
bool?
In my experience, token limits mean nothing on larger context windows. 1 million tokens can easily be taken up by a very small amount of complex files. It also doesn’t do great traversing a tree to selectively find context which seems to be the most limiting factor I’ve run against trying to incorporate LLMs into complex and unknown (to me) projects. By the time I’ve sufficiently hunted down and provided the context, I’ve read enough of the codebase to answer most questions I was going to ask.
I get that, it’s a valid point. But in OOP, objects can be things and do things. That’s kinda the whole point. We’re approaching detailed criticism of contextless development concepts though so it kinda doesn’t matter.
Properties are great when you can cache the computation which may be updated a little slower than every time it’s accessed. Getter that checks if an update is needed and maybe even updates the cached value then returns it. Very handy for lazy loading.
It’s fun and interesting all the experimentation that went on back then. As someone deaf in one ear… it’s hard to truly appreciate, but I get it.
The odd config files on inconsistent drive should just be symlinks (I think you want hard links?) so that your repo can contain all your actual code and file tracking. If necessary, keep a script on hand that can be run when mounted to recreate broken links.
This is a very strange setup and goes against standard practice separation of software and hardware unless this is some embedded thing in which case you wouldn’t have a repo on it at all.
Or just make a bunch of static helpers >:)
Same with your pits and junk. Just a normal bar of unscented soap is all you need to not be stinky and prevent bacterial growth particularly during the summer. Unless you have special needs based on skin conditions or gland conditions of course.
Have you tried Penny’s Big Breakaway yet? Been eyeing it and based on your list here, seems right up your alley.