Readit Newsmarcusbuffett commented on Clean Code vs. A Philosophy Of Software Design github.com/johnousterhout... · Posted by u/recursivedoubts
I strongly recommend "A Philosophy of Software Design". It basically boils down to measuring the quality of an abstraction by the ratio of the complexity it contains vs the complexity of the interface. Or at least, that's the rule of thumb I came away with, and it's incredible how far that heuristic takes you. I'm constantly thinking about my software design in these terms now, and it's hugely helpful.
I didn't feel like my code became better or easier to maintain, after reading other programming advice books, including "Clean Code".
A distant second recommendation is Programming Pearls, which had some gems in it.
marcusbuffett commented on Show HN: Ricotta – Language Learning to Replace Anki ricotta.affineur.io/... · Posted by u/williamsss
I'd have to see some serious stats to believe whatever SRS algorithm you use is better than FSRS (which is supported in Anki).
Stats for FSRS here (and elsewhere) [0].
[0] https://www.reddit.com/r/Anki/comments/18csuer/fsrs_is_now_t...
Yeah as someone working on educational software, anything hand-rolling their own SRS is a pretty big red flag. Beating FSRS is going to be next to impossible, especially FSRS with parameters optimized from your users’ review history.
marcusbuffett commented on A made-up name is better than no name mbuffett.com/posts/a-made... · Posted by u/marcusbuffett
The article is about (position, move) pairs. Why not call these objects "steps"?
Yeah this is a good shot at using existing verbiage, better than the candidates I came up with at least. Still not entirely self-descriptive, and has some overlap with usage in other parts of the codebase, like in data processing and user onboarding, but maybe that's a fine trade-off to make in order to use a normal word. I'd be equally fine with them being called "steps", but now I'm attached to my Keps :D
marcusbuffett commented on A made-up name is better than no name mbuffett.com/posts/a-made... · Posted by u/marcusbuffett
I really don’t like this idea if you are sharing this code base with anyone else.
I work in one of the magnificent seven and the culture here is codename crazy. Everything has code names, of course: every project, every release of every project, every component or subservice of every project, every internal tool, and often minor features that address some one-off problem in any of the above.
I am sure that these names solve some kind of brevity problem for the people on those immediate teams, but it is a nightmare for everyone else.
It is impossible to reason about or even understand have the statements made by members of other teams in a meeting or communication because every other word they use is a code name for something that you’ve never heard of and the name doesn’t bear any resemblance to what it represents. It drives complexity through the roof.
Oh god yeah I’ve been in this situation too. Working at Apple it was like “is everyone in this meeting cleared for Tigris?” And you’d be like “I don’t know, what the hell is Tigris”, and then it turns out after you check your clearances it’s just iOS 13, which is obviously no mystery that after 12 there will be a 13. Just call it that!
Nothing was named according to what it did either, I think our deploy tool was Carnival? Just codenames everywhere
PY: https://github.com/open-spaced-repetition/py-fsrs
TS: https://github.com/open-spaced-repetition/ts-fsrs
RS: https://github.com/open-spaced-repetition/fsrs-rs
Currently ts-fsrs and rs-fsrs support FSRS 6 and py-fsrs should also support FSRS 6 in the next day or so. Also, both py-fsrs and fsrs-rs include the ability to optimize the FSRS model from your past reviews!