merak136 | 10 years ago | on: Screenshots from developers: 2002 vs. 2015
merak136's comments
merak136 | 12 years ago | on: Systems Past: The software innovations we actually use
merak136 | 12 years ago | on: Aperture Science Personality Core 01 - URL Lengthener
merak136 | 12 years ago | on: Aperture Science Personality Core 01 - URL Lengthener
merak136 | 12 years ago | on: The architecture of Stack Overflow [video]
http://blog.stackoverflow.com/2013/02/why-we-still-believe-i...
merak136 | 12 years ago | on: The architecture of Stack Overflow [video]
[1] StackOverflow has VERY FEW tests. He says that StackOverflow doesn't use many unit tests because of their active community and heavy usage of static code.
[2] Most StackOverflow employees work remotely. This is very different than a lot of companies that are now trying to force employees back into an office.
[3] Heavy usage of Static classes and methods. His main argument is that this gives them better performance than a more standard OO approach.
[4] Caching even simple pages in order to avoid performance issues caused by garbage collection.
[5] They don't worry about making a "Square Wheel". If their developers can write something more lightweight than an already developed alternative, they do! This is very different from the normal mindset of " don't reinvent the wheel ".
[6] Always using multiple monitors. I love this. I feel like my productivity is nearly halved when I am working on one tiny screen.
Overall, I was surprised at how few of the "norms" that they follow. Either way, seems like it could be a pretty cool place to work.
merak136 | 12 years ago | on: The architecture of Stack Overflow [video]
I take this to mean that he feels that StackOverflow doesn't need tests. Not that tests are useless.
merak136 | 12 years ago | on: The Hacker Who Cracked the Code in Iron Man and The Social Network
BTW, I've used both. No need for a snarky response to me as well