awesome-falsehood VS system-design-primer

Billing. It always has to be the billing. For a list of all other edge cases, you have: https://github.com/kdeldycke/awesome-falsehood#readme

Falsehoods Programmers Believe in: https://github.com/kdeldycke/awesome-falsehood

Also, a list of other falsehood-programmers-believe collections: awesome-falsehood.

> I feel like there's a "Fallacies programmers believe about text" that should exist somewhere

I got you covered.

https://github.com/kdeldycke/awesome-falsehood#international...

http://garbled.benhamill.com/2017/04/18/falsehoods-programme...

https://jeremyhussell.blogspot.com/2017/11/falsehoods-progra...

https://wiesmann.codiferes.net/wordpress/archives/30296

There's an excellent GitHub repo that lists a lot of common falsehoods regarding names. I'm not sure how useful it'll be to OP, but the repo in general should probably have way more attention than it already does.

https://github.com/kdeldycke/awesome-falsehood#human-identit...

A decent list for this about prices and currency https://gist.github.com/rgs/6509585 and the full list of other falsehoods https://github.com/kdeldycke/awesome-falsehood

If you're interested in this sort of thing there's a whole bunch more: https://github.com/kdeldycke/awesome-falsehood

It's saddening to see the number of people who critique the idea of storing time as an unsigned integer by immediately responding that that means that times before 1970 cannot exist. This bespeaks of a continuing poor knowledge of the subject, despite all of the "falsehoods that programmers believe about" documentation that has grown up.

* https://github.com/kdeldycke/awesome-falsehood#dates-and-tim...

Microsoft, for one example, has been modelling times as a 64-bit unsigned 100-nanosecond count since 1601 (proleptic-Gregorian proleptic-UTC) for about 30 years, now.

* https://learn.microsoft.com/en-us/windows/win32/api/minwinba...

Daniel J. Bernstein in the late 1990s chose a 0 point for an unsigned count so far back that it pre-dates most estimates of the point of the Big Bang.

* http://cr.yp.to/libtai/tai64.html

1970 is not the mandatory origin for every timescale. (Indeed, in the early years of Unix itself there wasn't even a stable origin for time.) It is not a valid reason for dismissing the idea of storing time as an unsigned integer.

It's also sad to note that the headlined page's first sentence has one of the very falsehoods that programmers believe about time in it.

✅ donnemartin/system-design-primer: https://github.com/donnemartin/system-design-primer

View on GitHub

I've been giving interviews for past couple of months and this github repo has helped me so much for system design perspective and I can see myself excelling at interviews. - https://github.com/donnemartin/system-design-primer

You'll be on opiod's probably the first 1-2 days, so sleeping should be fine. Everything will be allright, don't worry too much. Just use the time now to prepare for the time after, make sure you go through post-surgery-essentials thread. Once you are out of the OR you won't have the energy to think about those details, so make sure you take that prep serious.

Tooling isn’t architecture. Figure out what you need to handle both personas and volume/throughput and then lay out the capabilities you’ll need. As you lay out points of ingress, egress, consumption you can start to lay out sequences(think in persona and sequence diagrams to express interactions between services). Lastly, evaluate tools that offer some of these capabilities and weigh the trade-offs (there are always trade-offs: https://github.com/donnemartin/system-design-primer).

[1] https://github.com/donnemartin/system-design-primer [2] https://www.teamblind.com/post/My-Approach-to-System-Design-V4SJARdx