awesome-scalability
awesome-falsehood
Our great sponsors
| awesome-scalability | awesome-falsehood | |
|---|---|---|
| 6 | 50 | |
| 52,917 | 22,972 | |
| - | - | |
| 6.3 | 7.6 | |
| 27 days ago | 5 days ago | |
| MIT License | Creative Commons Zero v1.0 Universal |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
awesome-scalability
- Ask HN: What are some of the best blog posts by software engineers?
-
100+ Must Know Github Repositories For Any Programmer
3. Awesome Scalability
-
SRE DevOps Interview Questions — Linux Troubleshooting
Scalability, Reliability and Performance for Large Systems
-
You should be reading academic computer science papers
Also check out awesome-scalability which is a categorized list of whitepapers, talks, and blogposts around system design. Lots of good stuff there.
- Looking back on what you know now, what concepts took you a surprising amount of effort and time to truly understand?
- The Patterns of Scalable, Reliable, and Performant Large-Scale Systems
awesome-falsehood
-
Ask HN: Did you encounter any Leap Year bugs today? How bad was it?
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
-
24 GitHub repos with 372M views that you can't miss out as a software engineer
Falsehoods Programmers Believe in: https://github.com/kdeldycke/awesome-falsehood
-
Why is it still a practice to not allow special characters in name fields?
Also, a list of other falsehood-programmers-believe collections: awesome-falsehood.
-
Bjarne Stroustrup Quotes
> 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
-
Ask HN: How to handle Asian-style “Family name first” when designing interfaces
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...
-
Facebook must pay $100.000 to Norway each day for violating our right to privacy
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
- Falsehoods Programmers Believe In
-
How to organize structs in the code
If you're interested in this sort of thing there's a whole bunch more: https://github.com/kdeldycke/awesome-falsehood
-
Store your epoch times as 64-bit floats
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.
What are some alternatives?
awesome-distributed-systems - A curated list to learn about distributed systems
nocode - The best way to write secure and reliable applications. Write nothing; deploy nowhere.
system-design-interview - System design interview for IT companies
libphonenumber - Google's common Java, C++ and JavaScript library for parsing, formatting, and validating international phone numbers.
awesome-tf - Curated list of resources on HashiCorp's Terraform and OpenTofu
tinygettext - A simple gettext replacement that works directly on .po files
awesome-javascript-learning - A tiny list limited to the best JavaScript Learning Resources
awesome-gbadev - A curated list of Game Boy Advance development resources
Systemizer - A system design tool that allows you to simulate data flow of distributed systems.
vscode-gitlens - Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more
awesome-sre - A curated list of Site Reliability and Production Engineering resources.
awesome-remote-job - A curated list of awesome remote jobs and resources. Inspired by https://github.com/vinta/awesome-python