gtaylor

34 ms·

301.
by gtaylor 12y ago
It's funny, because "brainstorming" means different things to different people/companies in different contexts. For us, it's sitting with a coffee and talking about a problem and possible solutions randomly. It&#x27
302.
by gtaylor 12y ago
I see there are already some contrarian-because-I-feel-like it replies, but this is a really succinct way to put it. Of course there are exceptions and edge cases, but EC2 is all about elasticity. If that doesn't appeal to you, don&#x2
303.
by gtaylor 12y ago
> It sounds to me like you expected managing remotely to be exactly the same as managing locally. You expected to be able to gauge the morale of the team, to know what people though of the groups future, etc without having to actually DO
304.
by gtaylor 12y ago
At my current company, we worked together on-site for about a year and a half. The last three and a half years, I moved off and worked remotely. While I can agree that there are benefits, I think the company would have been better served to
305.
by gtaylor 12y ago
> How is this even a failure? Google Code was the best at what it did for several years. Google Code had a few good years, and I am grateful that it happened. However, it did fail to win the software forge battle as the space heated up
306.
by gtaylor 12y ago
> Killing reader was a terrible idea. That cut my daily google usage in half and was obviously a key social and relevance asset. It sucks for our niche, but ultimately Google Reader was a product that didn't have any appeal beyond s
307.
by gtaylor 12y ago
> Consumer and 'free' software is the exception, and it's a recent exception with rapid release schedules. It's just shifting the costs from the vendor (maintaining old products) to the consumer (changing/upgradi
308.
by gtaylor 12y ago
> Honestly, I think he was right. Google has a really bad image problem right now where lots of people don't want to get involved with their projects because Google will most likely kill the project just like Reader and Glass. Again
309.
by gtaylor 12y ago
It is puzzling, but I think their rapid ascension has led to some people setting their expectations for Google too high. Others seem to hold them to some golden moral standard (of their own design), for some reason. In the end, they are a f
310.
by gtaylor 12y ago
> Google just needs to be up front about it (and maybe they are) Nobody launches a new product and guarantees "If this doesn't work out, we'll keep it around indefinitely on life support". You don't start a new e
311.
by gtaylor 12y ago
> Although you are correct, it's more a matter of perception / PR image. If we are looking at Google that shuts down pretty popular projects (Reader, Code, and now G+ seems to be shifting) or pretty innovative projects (Wave, G
312.
by gtaylor 12y ago
They kind of get a bad rap for this because of how large and visible they are. The funny thing is that many of the people here on HN have worked on projects that had very finite lifetimes as well, often closing them down for some of the sam
313.
by gtaylor 12y ago
Edit: The parent comment was flagkilled, but he was ranting about how Google should be expected to keep Google Code (and their other failed services) on life support indefinitely out of the kindness of their heart, because negative public
314.
by gtaylor 12y ago
I'm sure some are going to immediately say "Yet another Google casualty", but I feel like this one probably needed to happen. It's been stagnant for years, and they have been on the mindshare decline since the first two
315.
by gtaylor 12y ago
> and has dependably low latency I am particularly interested in this part. If you are able to share any anecdotal experiences, I'd love to hear them.
316.
by gtaylor 12y ago
Could you elaborate on what you liked about it? Rock solid as in availability, feature set, or other?
317.
by gtaylor 12y ago
Did you get any feel for the latency between publishing and consumption? I'm definitely interested, but I'd be looking for no more than a few second delay between publish and potential consumption.
318.
by gtaylor 12y ago
PubSub is conceptually simple. There aren't a ton of moving parts on the consumer side or the producer side. It'd be pretty easy to swap in different techs if all we're talking about is PubSub.
319.
by gtaylor 12y ago
> Not so simple. First, jumping jobs for a lot of people is difficult. It really is that simple. If you want to work for Yahoo, you'll need to relocate. Otherwise, there exists a full world of other possibilities out there for you t
320.
by gtaylor 12y ago
I've worked from home for over three years now, 100% of the time. Having done it and seen how big a difference it makes in feeling connected and involved, I can understand her rationale. It makes tons of sense for Yahoo specifically. T
321.
by gtaylor 12y ago
ltree isn't going to be a one-size-fits-all if you need more than one or two simple sorting conditions. Also, since ltree is really a glorified char field, you end up sorting by character ordinals instead of full values. Of course you
322.
by gtaylor 12y ago
I didn't see a clear "Read the Documentation here" link on the article. That's a bit disappointing. Here's what I found with a quick search on Google: https://docs.docker.com/machine/
323.
by gtaylor 12y ago
eh, I had a wheel bearing go bad on a brand new car after 8k miles. The model/make reviewed excellently, and is still considered a great choice. Two years later, it's been reliable and gets us from point A to point B affordably. M
324.
by gtaylor 12y ago
Is this commonly done? I'd feel like a terrible person doing this. At the very least, have an actual human on the phone doing the mass firing.
325.
by gtaylor 12y ago
What about them?
326.
by gtaylor 12y ago
Anecdotally, I've seen quite a few Django apps using gevent "just because". If you don't need it, you're just incurring additional overhead for no gain (which is what the author is saying). There are legitimate usag
327.
by gtaylor 12y ago
That's re-assuring to hear. Thanks!
328.
by gtaylor 12y ago
I haven't been tinkering with Rust, merely keep an eye on it until 1.0 lands. For those who are currently more in touch with the situation, does this release date look realistic, without quality suffering? Is the 1.0 release premature,
329.
by gtaylor 12y ago
There's a lot of helpful information in the article, much of which I didn't know about. I'm glad that you took the time to link to specific issues, that's very helpful. However, the article is so incredibly negative in t
330.
by gtaylor 12y ago
I am really enjoying it for daemons that don't need to save any state locally (via volumes). For us, it's a great fit for web app servers, background workers, and other things that don't need any guarantee of local persistenc

More ›