mlLK

> Cloud monitoring is a saturated market.

It's like yeah, it's saturated but it's saturated because the infrastructure is we're hosting it on is still and forever changing. Take some serverless CloudFormation in AWS; there was no good solution for application monitoring until someone specifically started solving for it because no one in their right mind was going to use CloudWatch and none of the other existing monitoring solutions/tools could fit the bill either unless they started from scratch and solved for that specific new infrastructure.

<Insert shameless Epsagon plug here />

The Cloud monitoring market might seem saturated but that's because there is no "silver bullet" solution given how much infrastructure has been and continues to change.

I'll admit that I am new to ruby and coming from Python I immediately fell in love with pry and was wondering if there was anyone out there who utilizes such a work-flow involving some sort of REPL. I have been having a hard-time figuring out a way to do this with pry in rails.

Given your background, I'd scratch all these "big picture" or "overly ambitious" ideas and return to a domain you're more confident in, pick something (axiom, rule, theorem, etc.) specific, and see if you can express or simulate an example of the "thing" in action.

Who cares? Generally the last thing I do is try to get practical with my portfolio just to impress some third party; depending on who you are, what field you're interested in, and everything else in your portfolio, the projects you produce will only vary as much as you originally imagined them.

If you're projects aren't interesting to you, are they really worth doing? All this aside, if I were OP I wouldn't be shy about chalking-up this experiment as a "project" since most ad agencies and creative types eat this stuff up.

Coolest application I've seen come out of node.js is http://mrdoob.com/125/Multiuser_Sketchpad_HTML5. I'd be interested in what others are doing in it; let alone, how they got about doing they wanted to do in it.

I think it's more revealing this way if you are interested in how increased traffic and site participation is effecting this 6% you mentioned above or that "days alive" value; IOW, how is increased traffic and new user participation effecting the rate at which this sample is posting comments?

In the end, I don't think increased traffic is effecting the discussion to the extent that it really matters; I think what really keeps everyone else in check is the frequency at which older members are posting comments.

This list is a good start, but far from up to date; just see, this (http://www.google.com/search?num=100&hl=en&safe=off&...) for YC 10.

Looks like he wrote a thesis on "seed accelerators" using YC as a model.

Easiest way I can describe is take all that crap on all those code snippet sites out there + all the basic features from DCVS + some experienced developers/programmers with some time to kill + somebody that knows what they've written is crap yet functional and is looking for some suggestions.

I got the idea from the simple fact that there are still plenty of people out there writing sub-par code who could never dream of pushing something serious they've written to github or bitbucket. The goal I had in mind was to a create sort of preliminary sandbox for users to push projects/snippets anonymously to a place where others could criticize, make fun of, and explain to them why their code fails. I'm sure the concept could easily attract programmers trolling other programmers, but that's also part of the fun since the community your pushing it for know their code was crap to begin with.

A couple more comparisons I couldn't resist: a DCVS for 4chan or extending pastebin to the point that it has an API and a user community who prefer logging and learning from their failures by contributing to this repository.

Except I never use it, googling site:reddit.com along with my search terms and possibly inurl:subreddit-keyword gets the job done