327 karma · joined December 6, 2013
Please read the definition of name calling.
> This is a very sensitive issue and people have good reason to believe every hiccup is intentional.
True, yet I still don't see any reason for me getting insulted.
traceroute output for google dns: traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets 1 192.168.1.1 (192.168.1.1) 1.916 ms 1.885 ms 1.872 ms
2 81.212.171.79.static.turktelekom.com.tr (81.212.171.79) 6.546 ms 6.548 ms 7.746 ms
3 93.155.0.130 (93.155.0.130) 8.952 ms 8.962 ms 9.998 ms
4 * * *
5 gayrettepe-t2-2-gayrettepe-t3-6.turktelekom.com.tr.119.156.212.in-addr.arpa (212.156.119.143) 11.529 ms 12.833 ms 13.350 ms
6 72.14.223.21 (72.14.223.21) 22.117 ms 23.176 ms 23.174 ms
7 64.233.175.188 (64.233.175.188) 45.687 ms 44.425 ms 44.377 ms
8 216.239.48.117 (216.239.48.117) 44.844 ms 216.239.48.125 (216.239.48.125) 59.738 ms 50.628 ms
9 209.85.254.114 (209.85.254.114) 50.647 ms 50.649 ms 51.616 ms
10 * * *
11 google-public-dns-a.google.com (8.8.8.8) 53.117 ms 53.809 ms 51.228 ms
--
traceroute output for twitter.com:
1 P-2812HNUL-F1.P-2812HNUL-F1 (192.168.1.1) 27.282 ms 27.520 ms 27.748 ms
2 81.212.171.79.static.turktelekom.com.tr (81.212.171.79) 32.212 ms 32.926 ms 33.018 ms
3 93.155.0.130 (93.155.0.130) 34.917 ms 34.817 ms 40.507 ms
4 * * *
5 gayrettepe-t2-3-gayrettepe-t3-6.turktelekom.com.tr.25.212.81.in-addr.arpa (81.212.25.72) 42.955 ms * 3174.208 ms
6 ulus-t2-3-gayrettepe-t2-3.turktelekom.com.tr.204.212.81.in-addr.arpa (81.212.204.205) 56.691 ms 21.201 ms 20.673 ms
7 * * ulus-t2-1-ulus-t2-3.turktelekom.com.tr.197.212.81.in-addr.arpa (81.212.197.197) 2853.324 ms
8 ulus-t3-6-ulus-t2-1.turktelekom.com.tr.29.212.81.in-addr.arpa (81.212.29.99) 22.575 ms 22.747 ms 19.829 ms
9 * * *
10 * * *
11 * * *
(It looks like 8th node drops all the packages)
--
just to be on the safe side, this is for the yandex dns:
traceroute to 77.88.8.8 (77.88.8.8), 30 hops max, 60 byte packets
1 P-2812HNUL-F1.P-2812HNUL-F1 (192.168.1.1) 4.234 ms 4.725 ms 5.196 ms
2 81.212.171.79.static.turktelekom.com.tr (81.212.171.79) 9.674 ms 10.857 ms 11.185 ms
3 93.155.0.130 (93.155.0.130) 12.008 ms 12.007 ms 13.069 ms
4 * * *
5 gayrettepe-t2-2-gayrettepe-t3-6.turktelekom.com.tr.119.156.212.in-addr.arpa (212.156.119.143) 15.934 ms 18.825 ms 15.887 ms
6 ams-col-1-gayrettepe-t2-2.turktelekom.com.tr.102.156.212.in-addr.arpa (212.156.102.69) 70.412 ms * * 7 ams-ix.retn.net (195.69.145.216) 101.343 ms 101.304 ms 101.318 ms
8 GW-Yandex.retn.net (87.245.246.14) 65.985 ms 62.182 ms 63.166 ms
9 tulip-ae1.yndx.net (87.250.239.46) 79.653 ms 78.998 ms 63.158 ms
10 dns.yandex.ru (77.88.8.8) 73.809 ms 67.510 ms 67.868 ms
It is pure hoax. I'm also very discontended these very recent restrictive movements, probably the authors at webrazzi are feeling the same way, but by publishing such news without verification, the media becomes more and more a tool for propaganda.
Seriously, there is so much bullcrap going on, I don't know what to believe anymore.
In the context of Software Development you can get into wherever you want if you have enough references, be it your contributions to open-source softwares, your past job experience etc.. pretty much everything that proves you can get stuff done and cause as few as trouble possible.
To understand my point throughly, you need to understand that most people -if not everybody- wants some form of determinism. Understand that the people who hires you has practially no way to know for sure how useful you will be to them, so the things you have done in the past has to stand for you. You can view a college degree simply as a reference that is supported by your college indicating that you know some things, which implies you are likely to perform better than the other Joe which doesn't have a degree.
A college degree is the safest, easiest and most reliable way to weigh a canditate's ability, though its not the perfect method, more importantly it is not "the" method.
SRM matches are unique in the way that forces you to come up with a working implemetation in relatively short time. The problems present there will definitely help you to hasten your thought process.
In addition to this, I suggest you to check coursera's algorithm classes if you haven't already. Besides classic MOOC stuff they have an explicit section named job interview questions. These should help you better your algorithm knowledge.