309 karma · joined December 13, 2009
Firstly, i'm not married nor do i have children. Secondly, these things will come, in time.
I find it discouraging that you feel that one can't take pride or enjoy work while being "a cog". This isn't about 'everlasting glory'; it's about enjoyment, it's about fun, it's about being proud about what you've created and owning it, it's about respect from your peers, it's about being a part of something.
As you said, "if it is something you actually want to be doing then that is one thing". It is. It is exactly what i want to be doing.
I feel that the author's post doesn't apply in my case, because:
- Some of the problems i work on are amazing. They're interesting and fun, and i enjoy them outside the normal "work hours".
- Twitter has an "unlimited"—be respectful to your team—holiday policy. I've probably taken about 6-7 weeks off in my one and a quarter years here.
- Breakfast, lunch, and dinner are served for free. While you might not count that as 'being paid overtime', the costs of food can add up.
- This behaviour is not required. I know people who do 9-5 and that's it. They get their work done within deadlines, and there's no issue with that.
So, am i to assume that Twitter is a huge exception? I'm not so sure. I think that while Twitter is a special environment, there are many companies that offer similar benefits.
Maybe the real statement shouldn't be "don't do unpaid overtime", but:
"Your work is going to fill a large part of your life, and the only way to be truly satisfied is to do what you believe is great work. And the only way to do great work is to love what you do. If you haven’t found it yet, keep looking. Don’t settle." - Steve Jobs
Maybe you should follow more tech news. This might have more details: http://www.businessinsider.com/exclusive-interview-twitter-c...
According to many people I work with, Twitter is the best place they've ever worked. The perks are great, the challenges exceptional, and the culture inspiring.
Join The Flock - http://twitter.com/jobs
I'm not sure that saying Twitter has 'grown more like Weibo' is accurate given that those features have been around since before the redesign.
(disclosure: I work for Twitter)
I'm not sure it'll make a difference, but maybe it could.
P.S. Come work at Twitter, it's awesome.
From this, we can launch better products. I can't go into specifics, but there's some really good stuff coming in the future.
Secondly, we're not just focused on making money. There are many teams at Twitter working on many amazing things unrelated to a financial goal.
It's not a bubble until we (Twitter) install a slide in the office.
Twitter's subtext being 'we don’t want your clients using our API and diluting our ability to advertise'.
While neither of these statements are true, the concept of offering a protocol instead of an API is an interesting one. Though, the quote "open protocols are basically a gentleman's agreement" does indicate a similar issue to the one that's being projected onto Twitter.
As shantanubala says, upgrading a protocol with mass adoption could be very difficult, this can then cause issues when you want to offer new services, or deprecate certain calls as they may be too complex at scale.
Coordination definitely seems to be a huge issue when dealing with these open social networks. If a security issue is found in a server which can leak information, how long would it take for every server to be patched? I think a good example for this is to ask how many WordPress blogs get hacked because they're running on old copies of the code?
Twitter is hiring in San Francisco. I just started there.
Here's a list of the positions available: http://twitter.com/positions.html.
I wasn't originally going to post this, but i saw this http://mashable.com/2011/01/01/twitter-jobs-2/ and thought it might be worth adding.
The author comments:
"-I think i must make it clear. There are a few non-CG elements in the shortfilm: photographer (shot on greenscreen), pigeons, timelapsed growing flowers, flying airplane and sky backgrounds."
To begin with readability, i'm pretty sure that programmers are capable of working out the end of a line without the use of a semicolon: Scala has no such requirement of semicolons. Surely, the best way to ensure readability is, like in spoken language, to use common terms and expressions. Finding the obscure uses of the language to ensure the forceful requirement of a semicolon just seems petty and unhelpful. It is the equivalent of being overly prolix within a natural language, therefore limiting the ability to communicate.
The elimination of random bugs is a little more tricky to discern. Sure, there are occasional issues that can be caused by the lack of semicolons, for example (taken from the quoted text):
a = b + c (d + e).print()
But let's face it, if you're writing your javascript like that then you probably need to re-evaluate the your use of (d + e). After all, the majority of browsers now use javascript compilers that are more than capable of constant folding. Therefore meaning that:
a = b + c var f = d + e f.print()
should therefore be no less efficient and, on the side of readability, you could even name f to be something worthwhile.
The best minifiers (YUI and Google's Closure Compiler) are perfectly capable of minifying javascript without semicolons. If your minifier is having issues because you haven't inserted a semicolon, then—obviously—it's not doing its job properly.
In my writing of javascript, I very rarely use semicolons and the issues described have never come up. Often the expressions given as to why it is necessary are extreme and obscure to the point whereby using those expressions may not be the best policy. I'm not advocating the idea of never using semicolons (something i pretty much do), I'm just saying that the requirement for constant use is pointless.
The YUI minifier, for example, works perfectly fine without semicolons in the original. Equally, the Google Closure Compiler does also.
If you're using a minifier that just removes new lines and suffers without semicolons, I think you should rethink your minifcation process.