Re:Partitioning GitHub’s relational databases to handle scale
by stareatgoats on Tuesday September 28, 2021 @05:34AM
(#28680853)
Read it, and well sure it is a challenge to work on an old codebase, and you need to jump through a few hoops that you don't need in pristine projects. Something tells me this guy wasn't able/willing to make the effort. (Could be a language problem, naming a "bug" a "bag" for example, u and a are not even close on the keyboard).
Re:Partitioning GitHub’s relational databases to handle scale
by samhw on Tuesday September 28, 2021 @06:04AM
(#28681021)
> (Could be a language problem, naming a "bug" a "bag" for example, u and a are not even close on the keyboard).
I think this is reading far too much into nothing. He writes 'bug' correctly about 5 times. I'm not an expert in psycholinguistics, but I suspect there's a phenomenon where you can mangle your internal pronunciation of the word and hit the wrong vowel.
Re:Partitioning GitHub’s relational databases to handle scale
by stareatgoats on Tuesday September 28, 2021 @06:41AM
(#28681216)
> I think this is reading far too much into nothing.
Could be. I could have left that somewhat tenuous side note out, my argument doesn't rest on it.
Re:Partitioning GitHub’s relational databases to handle scale
by aiisjustanif on Wednesday September 29, 2021 @11:37AM
(#28695152)
Though I agree that old codebases are a particular challenge, picking on word confusion is unnecessary. Even if minutiae is important in a legacy codebase. Dyslexia is a real thing. So are linters thankfully.
Do you still think so after reading this: https://news.ycombinator.com/item?id=18442941