ViVr
One of my git habits is to git reset the entire feature branch just before opening a PR, then rebuild it with carefully crafted commits, where i try to make each commit one "step" towards building the feature. This forces me to review every change one last time and then the person doing code review can also follow this progression.
These benefits hold even if the branch ultimately gets squashed when merging into main/master. I also found that even if you squash when merging you can still browse back to the PR in your git repository web UI and still see the full commit history there.
Yes i use bitwarden directly, no self hosting. I do trust them keep my data safe (although i also trusted LastPass at some point, big mistake) but why not also keep a local copy, just in case. The type of data you store in bitwarden is worth the hassle and if Bitwarden Inc. ever gets into big trouble suddenly you'll be glad to have the backup.
It has been a feature request for close to 6 years now: https://community.bitwarden.com/t/allow-attachments-to-be-ex...
On most projects and topics i work on i keep personal notes. Sometimes i copy entire pieces of information from websites into my notes so that i don't lose it when the website dies. Any interesting webpage i at least archive through both archive.today and archive.org. Eventually i might look into taking that locally as well.
Not your keys not your comms. But even then then, apply defense in depth.
> "Sky’s messages ran on a different system than EncroChat’s, and it was more difficult to infect the network with bulk malware. Instead, someone with knowledge of the investigation told me, analysts seem to have launched a “protocol attack” that deceived handsets into revealing their private keys."
It also increases privacy because the contents of the traffic can not be observed by third parties.
Why is the Federal Reserve pouring money into the financial system? Answer lies in short-term issues and structural market changes https://www.ft.com/content/345da16e-d967-11e9-8f9b-77216ebe1....
He's been on many podcasts to explain his theory and provide updates. I will link you an interview at realvision from september 2020 timestamped at 51:55 where he goes through it in summary: https://www.youtube.com/watch?v=h_HCIyc6MaA&t=51m55s
[1] https://twitter.com/csuwildcat/status/1392639419920785411
[2] Same tweets but on threadreader https://threadreaderapp.com/thread/1392639419920785411.html
A trainer can check your form and help you execute the exercise safely but how does an exercise routine injure you?
Meanwhile the FED heroically partakes in piling on debt for the futures generations.
Due to game theory mechanics most network participants have an incentive to play by the rules and agree on rules that are as fair as possible. A hard fork has to be embraced by the majority of the users to be accepted. It's not just the miners or the whales who decide the rules.
Of course there are countless of cryptocurrencies in use right now of which most are doomed to fail (maybe even all but one are doomed to fail).
Doesn't your solution of replacing the possibly buggy code with configuration leave you with configuration that may or may not be buggy?
One example where I have experienced the benefits of a clean codebase is when onboarding new developers. It takes a few days of handholding but once they've started working with the code there's very little room for gotcha situations where they get stuck or inadvertently introduce bugs due to being misdirected by the code that was already there.