Yeah this happened to me at least once, and I had to spend several hours with low-level recovery software to get my files back. This was the catalyst that finally got me to ditch windows for good 7 years ago.
> I do believe that there is real value in pursuing functional programming, but it would be irresponsible to exhort everyone to abandon their C++ compilers and start coding in Lisp, Haskell, or, to be blunt, any other fringe language. To the eternal chagrin of language designers, there are plenty of externalities that can overwhelm the benefits of a language, and game development has more than most fields.
I wrote some tooling to help debug sql queries with many CTEs. It parses the sql, finds all the CTEs, and prints the result of each CTE formatted as csv. If the .sql file changes on disk, it reruns the query and tells you which CTEs’ output changed. Saved me hours in debugging.
Why do you need a warm standby for production? Do you need >= 3 nines?
Our staging environment has its own instance that is rebuilt from prod, with pii removed, every day outside working hours (this normally takes about 15 minutes). It’s fantastic for testing migrations, and is easy to support compared with a warm standby.
"Do you need >= 3 nines?" No, it's a one person project. I'd be happy with a single 9 or even no 9s just a 99.0 haha
I switched to warm standby to reduce stress on the production db which was in the cloud. There is just a single production server and having it constantly run the heavy data processing MVs + handle queries was CPU intensive and slowed everything down. The CPU was costly.
To fix those issues, especially the CPU, I run the primary on a home server where it can crank the CPU as much as it wants running the data processing MVs and then sends the processed WALs to the warm standby that just handles the queries.
This has fixed those CPU and slow queries (when an MV is updating a table that is being constantly read). But introduced headaches anytime I update postgres.
My understanding is the 'fix' is to move data processing to another postgresql DB or flow? My biggest reason for not using another DB is I didn't like the idea of losing direct relations for keys.
Anyways, I appreciate the input, it's been a thorny issue I hit once or twice a year and am always unsure if what I'm doing is 'normal' or what I should do to fix it.
Get rid of the ethanol mandate. Replace those acres of corn with solar panels and an understory of native plants. One likely biased source I read a while back said that about 1/3 of this land would be sufficient to power all the cars and trucks in the US if they were all EVs.
Windows as a platform lost the war many years ago when the web (and then mobile) took over, and is no longer a key part of Microsoft’s business since the CEO switch in 2014.
Microsoft’s current strategy is to 1) keep a stranglehold on enterprise (so, Office and 365 subscriptions) and 2) make money on workloads regardless of platform (with Azure).
What new software, besides games, targets windows anymore? If you wanted to target windows, what SDK and language would you build on, and how many times will it be replaced with $new_hotness in the next 10 years?
I have a similar experience with my GPU. Got a 3090 and found that nvidia’s linux driver enforces a minimum GPU fan speed of 30% regardless of temperature. That’s unacceptably loud if you’re in the same room. After hours of searching online, flashing the GPU’s bios is apparently the only solution, so I bought a bunch of acoustic foam instead.
I’m still 100% Linux on all devices, but this bit really sucks.
I was in the same boat, doing most text navigation on the keyboard and fully adapted to the quirky arrangement of home/end/pgup/pgdn of the Microsoft natural keyboard elite I’d been coding on for 23 years.
But I do a lot of nomading, so I really wanted a small keyboard. And I’m a tall guy, so I was looking for a full split (I tried the Kinesis Freestyle2 for a while but didn’t love it).
I bought a ZSA Voyager. The first day I went from ~120wpm to 20. I hated it and had buyer’s remorse. Second week, I was still switching to another keyboard in the afternoons because I was making so many typos and felt so tired. I swapped out most of the switches with higher force ones, and that helped a ton. It took about two months before the keyboard disappeared again and there was only me and the work.
The biggest single win is that backspace is under my right thumb next to space bar, which felt life-changing once I got used to it (if I were still using a normal keyboard, I’d probably re-map right alt to backspace). And while word selection with ctrl+shift+arrow took a bit longer to get used to, now I appreciate not having to move my fingers at all to hit the arrow keys.
Nine months later, you can pry the Voyager from my cold dead hands. It’s probably the last keyboard I’ll ever buy. I do wish it had two more keys (haven’t found good homes for Alt and ~) but overall I’m very happy with where I ended up.