covati's comments

It's not public for one - that's kind of a big one.

That manager advice sound horrible. That is the point of a manager. If you can't trust them with something as basic and important as team interactions, then there is a bigger problem.

I'd say this is a nice little cheatsheet. Which is useful at times, but I agree - this title is misleading.

Edit: The far right has a key, and just below is a box that has a few undocumented items.

This is great for NHL viewers, but even better for GoPro - good to keep getting their name out there as the go to for amazing action footage wherever you are.

well, now that swell is shutting down it might make sense. But I'll miss the variety that I get from swell :(

http://techcrunch.com/2014/07/28/apple-to-buy-swell-for-30-m...

They use statuspage.io, a great service, but most people use to manually set the times that the service was out - but I believe they have an API for that as well.

So I think MailGun just didn't indicate the service was unavailable when they put the outage details in.

I haven't played with segment before, does anyone else have any experience with it? However, I am a huge believer in using one library/system to track events and use one system to ingest them.

One quick note, I've found that it's helpful to build a simple wrapper in my own system for the call to the external library - this means that I have just one place to go if I change who I use to send events to.

I do think this oversimplifies lead scoring a bit, that's an area for a whole blog post to or two - and this seems like a good starting point. This is just to say that being too quick to settle on a lead scoring method can cause a lot of incorrect assumptions later.

I've thought about doing something like this for a while, but on a more dynamic level. More along the lines of capturing check-ins from Facebook and Foursquare as well as other life events and making them available (with permission) via an API.

Someone brought up to me that it would be pretty much like Google Now - which isn't completely correct, but it gets to what the value could be.

Well done guys! Having played with it early on, I can see that you've done a lot to make it even easier to use. I love the custom metrics too, we'll be looking at how we can incorporate some of our info into our page soon.

I disagree, it's about core competency. I have the resources to build and host a number of things. But I pay for quite a bit of software. Things like bug tracking, ticketing, billing, etc. - all because I want to focus on what I do best and let some one else handle the details of this stuff.

This kind of comment is a gross simplification of a market, and just shows that you haven't really thought about it much at all.

-1

I've been playing around with this for a little while now and it seems like a great service for the status page itch. One that we weren't scratching very well in the past.

I haven't even begun to dig into the API yet, but I've been happy with the ease of setup and how simple it is to create, update, and complete an outage or disruption report.

Thanks for the solving this problem, guys!

As a general idea of routing all traffic through one point, yes. However, as a marketing tool to track traffic, they are quite valuable. Sadly, optimal network routes and other considerations take a bake seat to making money.

We've blocked a few of the worst, but mostly just added servers to deal with the load.

We actually found out who one of the worst ones was and contact them. It turns out it was a major legit proxy, but they had a bug in their proxy code that caused refetching of one of our urls over and over. They were very easy to work with and they fixed the bug.

I only skimmed the original article, and I think this woman makes some great point about how absurd his article is.

She has some good points about her experience, however, as she has only had 6 months in this field, and that is working in one company, I'd say she's not the right person to write a rebuttal to anything about the current state of it's culture.

Someone who has worked in multiple companies, in different regions, and at varying levels of organizations would be much more fit.

Again, I'm not saying her article is crap, the bulk of it is a good counterpoint, I'd just like to see someone with a bit of a broader view way in from a woman's perspective.

This is an old story (see the date of 1999?), as a WPI guy ive heard this one a few times

The guy was attempting to use a cute little physics trick. I'm no physics major, but the idea is similar to walking on coals. You can have the liquid nitrogen in your mouth briefly and it doesn't burn you. Swallowing it, however is a totally different story.

So this is free for now, what are you thinking of charging?

We just started playing with this, it seems like a great alternative to backbone for those who want a bit more of the common stuff done for you (esp data binding).

Backbone is a great starting point if you have strong opinions and want to own it from the ground up.

Just my $0.01

I don't think that is necessarily true. Most modern programming languages, as well as the relative cheap nature of RAM, have rendered a true understanding of the inner workings of RAM less important.

Would they be better at their job if they did? Probably. But do they have to? I'm not so sure anymore.

My comment that I posted on the site:

I don't disagree that having a big name on resume can be helpful. But I do think there are other things that should come into consideration.

I worked at several no name startups right out of college. And yes they failed, but I was also given huge opportunities and responsibilities that I never would have had at a larger firm.

And as a hiring manager I don't let names on resumes be my only driver. Just because you worked at Amazon straight out of college doesn't mean you are amazing. It just means they gave you a chance. And it doesn't mean you've done much, you may have just been stuck fixing bugs on one very small aspect of one system. That isn't very valuable in my eyes.

So I think it's worthwhile noting that there is a risk at startups and the name recognition is definitely useful in a crowded market. But name recognition will only get your foot in the door. You'll need some real experience to go the rest of the way, and I have nothing but my years at failed startup to thank for that.

Hey all, Winning vs. Keeping is how I'm starting to look at features that we develop. It's something might help to balance expectations and demands from other groups within the company.

I'd love to hear your thoughts, would this be helpful to you, or do you think this would just complicate your life...