All the probability mathematics aside, the real world we live in is probably a lot less random even with the best hardware random number generators.
I've moved on to something like TSID(where security isn't a factor) or uuidv7 to make sure this never really occurs in practice rather than over engineering the code with retries.
Can someone explain how is this different from lambda calculus, it seems like you can derive the same in both. I don't understand both well enough and hence the question.
This is similar to how I solved a BYOK(bring your own key) feature at work. We had a lot of hardcoded endpoints and structures on the client and code that was too difficult to move over a nice BYOK structure within the given timeframe. So we ended up making a proxy that basically injected customer keys as they passed through our servers. note that there are a lot security implications doing this.
NotebookLM is a success in spite of the interface not because of it.
Pretty awful UX to be honest.
Credit goes to the backend engineers who made this happen.
Took me ages to figure out you can copy paste simple text. Editing any text isn't great either.
Why isn't there a dedicated markdown notes section with folder and files? Most of us won't have ready to use PDFs but almost all of know how to use a text editor and paste text into it. Your Notes app UI is without proper support for editing and maintaining notes.
Are you a middle aged+ developer? You read the DDD/CQRS/event driven book or viewed the conference. My dear friend, you have fallen victim to developer porn. It's very addictive. You end up playing "the architecture game" rather than building anything useful.
I have yet to come across ONE good large scale project that makes use of these and isn't a big ball of mud.
I wish I had the time to do any of this. I could probably do it on a weekend but maintaining it, upgrading it to keep up with new releases would be something I wouldn't have time for.
I end up just paying a cloud provider and forget about it.
Anyone else on the same boat? What has been your approach?
After working with NATS, I wouldn't want to touch Kafka even with a long stick. Its just too complex and a memory hog for no good reason. It doesn't have all the features that NATS supports as well.
Not racist but offensive indeed. It's like relating school shootings to white people. A white child sitting in Norway might not relate and may find it offensive and insulting.
I feel, What's more harder are the jet engines on fighter planes. These are usually a decade or two ahead in terms of advancements. The technology here trickles down to commercial jet engines slowly. Things like Metullargy for blades etc are a closely guarded secret. China and India are pouring billions into research just to get theirs close to even the lower end of what GE has to offer.
This is the way to go, pretty much solves, 404 resource not found or route not found. But you will get laughed at by so called architectural dogmatists. Remember we aren't really doing REST, it's just RPC and let's call it that.
Shoehorning http protocols error codes as application error codes, drinking the cool aid and calling it best practice is beyond bizzare.