liquidgecka

13 ms·

91.
by liquidgecka 7y ago
There was a delivery benefit. At the time we were one of the largest server manufactures by volume. Generally we were on the same scale as Dell or HP. Buying from only a single vendor had serious cost implications sure, but there was also a
92.
by liquidgecka 7y ago
Sorry it is just not true that Google was AMD exclusive. During that time Google had a I/A release cycle where every other hardware platform cycled between Intel and AMD. I will give you that AMD had a huge issue launching and I still
93.
by liquidgecka 8y ago
damn it.. of course you would update the spec right before I release my config parser. =) I have been working on a TOML reader/writer for golang that supports read/change/write and format (like go fmt) that sometime I will ge
94.
by liquidgecka 8y ago
And yet I bet nobody mentioned the "fire rain" in our first data center, the load bearing mac mini, or the surprise Snoop Dog visit/party! =)
95.
by liquidgecka 8y ago
I remember all those iPhone suckers having to download special apps to remove conversations in the early days since it only allowed you to delete them one at a time. =) I also remember getting on a bend to make all fake alerting go away aft
96.
by liquidgecka 8y ago
You know.. I found a special box (PowerMac Pro) in the "special closet" that had been moved like 5 times. It was Blane's old desktop and it had the twitter codebase checked out from like ~2007 era? Kind of nifty seeing just h
97.
by liquidgecka 8y ago
I believe it was James May that said: "You have come up with a clever solution to a problem you shouldn't have had in the first place!" =)
98.
by liquidgecka 8y ago
That got nuked right about the time that I started! I never saw it live.
99.
by liquidgecka 8y ago
Funny thing is that the place I am at now uses Zookeeper.. luckily it has not been trouble for us though. =)
100.
by liquidgecka 8y ago
If anybody is interested in random Twitter internal stuff I might bang up a medium post one day. I was neck deep in the infra side of things for years and have all sorts of funny stories. Our managed hosting provider wouldn't let us us
101.
by liquidgecka 8y ago
That was a period when the only people talking outside the company were the ones not trying to fix things inside of the company. Twitter never had dedicated machines for individual users. Its just not how the infra ever worked (at least unt
102.
by liquidgecka 8y ago
Long time no see man! =)
103.
by liquidgecka 8y ago
Much of that was just bad design decisions in the early days creating a momentum that was unstoppable and unreplacable at the speed we were growing. In the early days they implemented a Kitama system for memcache. It worked great so long as
104.
by liquidgecka 8y ago
Everybody knows about the "fail whale".. nobody knows about the "moan cone".. The image is lost to history but it was captured by this account ages ago: https://twitter.com/moan_cone IT was thrown when t
105.
by liquidgecka 9y ago
I have a very short gmail address so I get _loads_ of spam daily. The above is actually correct. Emails from my address, even though they are spoofed will show up in my Sent folder until I mark them as Junk. I just checked with the 3-4 spam
106.
by liquidgecka 9y ago
Somebody misprinted a flier for a local town meeting.. the email was SUPPOSED to be congresman.<myname>@gmail.com but instead it got cut off to just <myname>@gmail.com. I started getting a wave of hate mail asking how I could ha
107.
by liquidgecka 9y ago
yea.. me. =) I also made spam@gmail.com and basically broke gmail (too many emails to a single destination for the system to handle in those days).. but I got an AWESOME trove of spam reports to use as testing data! =)
108.
by liquidgecka 9y ago
Yea.. try having a short (5 character) @ gmail.com address.. For _years_ I have dealt with this issue. Every time I seem to finally get things to not automatically get added I get hit with another round of lazy google engineers that don&#x2
109.
by liquidgecka 9y ago
At the time Twitter had a ton of features under the hood that kept being supported and maintained, all of which just added complexity to the system. We had an API service, a web interface, the legacy web interface that was still used for se
110.
by liquidgecka 9y ago
Spammers would sign up for enterprise accounts, drop a couple hundred or more to get priority access, then spam the ever living hell out of the internet because they knew that we couldn't just disable the accounts outright. In the tim
111.
by liquidgecka 9y ago
Yea but those designers knew the magnitudes that they were dealing with and built them into every single layer of the system. Its easy to build a system that handles "x million transactions a second". Its MUCH harder to build a sy
112.
by liquidgecka 9y ago
Its not described well at all in the article, but the instance on sticking with a RoR framework well beyond what it could rightfully scale up to is what kept us from building a great, great many features, least of which was harassment tooli
113.
by liquidgecka 9y ago
Thats what kept happening and it was an abysmal failure. Every so often a person would have a brilliant idea on how to solve our scaling issues. They would then disappear into a corner to invent yet-another-bird-themed-datastore. After a fe
114.
by liquidgecka 9y ago
Hi! I am one of the dudes that actually helped kill the fail whale so I feel I can speak to this topic. =) Steve and John were both good developers that wrote some seriously critical components of the system and were a big part of getting t
115.
by liquidgecka 9y ago
Hi, early Twitter employee here. The reliability team called the infrastructure Fisher-Price internally so this wasn't just one random executive coming up with a term on his/her own. The problem wasn't ruby. The problem was t
116.
by liquidgecka 9y ago
Oh I know.. trust me. I used to work in the team that handled that very problem and yet right now I can't get google to stop spam processing mails that fetches from my private IMAP server for my wife's gmail account. Everybody I k
117.
by liquidgecka 9y ago
Worked there.. I cared. I responded on forums, dealt with customers large and small, bot direct and as a point of engineering contact. Here is the problem with a company like Google: SPAM. Want to support the regular user? You are going to
118.
by liquidgecka 9y ago
I was that guy many times (Former Spam, Abuse, Delivery SRE). You have to realize that %95 of the time when people reach out to report that mail that they are sending is getting canned its because they are sending SPAM and don't realiz
119.
by liquidgecka 9y ago
Not 0 characters long, just full of unicode whitespace that got stripped out of most rendering layers. It was right up there with people like this: https://twitter.com/_
120.
by liquidgecka 9y ago
I just filed this issue: https://github.com/brockwhittaker/House-Senate-Tax-Bills/iss... You are not properly changing the deduction for married people. You have a single static value that gets used and is the &qu

More ›