Software Engineering at Google
books.google.com
Software Engineering at Google
1–10 of 73 posts
Re: Software Engineering at Google
#2Re: Software Engineering at Google
#3I see a lot of upvotes -- has anyone read this? Is it actually good?
Re: Software Engineering at Google
#4Re: Software Engineering at Google
#5I see a lot of upvotes -- has anyone read this? Is it actually good?
Re: Software Engineering at Google
#6I see a lot of upvotes -- has anyone read this? Is it actually good?
Re: Software Engineering at Google
#7I see a lot of upvotes -- has anyone read this? Is it actually good?
If those quick talks were any indication, there will be a lot of value in this book for experienced developers.
Re: Software Engineering at Google
#8I see a lot of upvotes -- has anyone read this? Is it actually good?
Re: Software Engineering at Google
#9Google 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 looking latency distribution.
Those goals are not sustainable in normal businesses, even tech ones.
Google places very little emphasis on things like code readability and testability because it’s easy for them to do rewrites or just run tests on 1 million cores to shake out race conditions and locks.
Read this for entertainment but don’t try to blindly apply it to your work environment. Most of it will make you a bad engineer for non-FAANG envs.
Re: Software Engineering at Google
#10If 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…