21–30 of 73 posts
Earlier quoted context omitted.
I think in such cases it's because people probably use upvotes as bookmarks to "read later" ( ...some day, for sure! )
Just so people know, you can use "favorite" for that. You can also favorite comments.
Earlier quoted context omitted.
as someone who worked previously at google, and went back to the start up world working with php mysql, this is not true at all
How is it not? Seems like simple economics to me. Something like maintaining a custom kernel distribution takes ${x} amount of engineer time for ${y} amount of “savings” (better perf, custom patches, nonstandard features, whatever). Why bother until you have a fleet of machines large enough for y to be greater than x?
The biggest proprietary sink for most people is stuff like the build system/tooling/etc. Not many people have to be in a role where you're micro-optimizing something. They certainly exist, but not in the numbers some people on here seem to think.
I guess it makes sense that a book would be the logical conclusion of Hyrum's Law ( https://www.hyrumslaw.com/ ).
I guess it makes sense that a book would be the logical conclusion of Hyrum's Law ( https://www.hyrumslaw.com/ ).
I see a lot of upvotes -- has anyone read this? Is it actually good?
If you’re interested in becoming a software engineer or are junior, do not read this and cargo cult it because many of these things will not be good practices for 99.99% of the industry. Google has custom tooling, custom kernels, custom hardware, etc and legions of support at every layer of the stack. Complexity is not eschewed but it is rather embraced if it means some slight improvement in utilization or better loo…
This is complete nonsense. Google's code review and testing and reliability practices are better and more sensible than most big and small companies I have worked for and heard about.