hackula1

Love it. I had a lot of fun playing around with it.

I found it hugely useful in the .Net world. With closed source, obscure errors cannot be as easily tracked down, especially when they are not covered by MSDN or a prominent blog. A couple years after switching to an open source stack, I barely use it at all, and when I do finally hit a wall and ask a question, I get an answer ~20% of the time (compared to 90%+ when I was in .Net). I am a huge fan of SO, but good docs and readable code go a lot further.

Looks very cool. Pricing is a bit confusing though.

    1 user, 1+ user, unlimited users

What does 1+ user mean if not unlimited?

Also, row limits are not listed in the top tier, making me think that they are either unlimited, or that the go until they break due to a technical limitation somewhere after 5k rows.

I got distracted and was looking at your other posts, when I noticed that the 5 or so I had looked at all said "1 day ago". I thought you must be a lunatic until I actually went back and read this post and saw that your dates had been lost. :)

I always assumed the handled it through Accounts Receivable.

> But if he can, we’ll get Node v0.12 delivered a lot faster and have a stronger community.

And of course, Strongloop could not help but make another half way claim that they are the ones "in charge" of node. This current stuff aside, I just cannot believe their lack of shame when trying to take commercial credit for a community project.

Ben is not a Joyent employee, but a Strongloop employee/cofounder. I Cannot say I am terribly surprised. Strongloop has rubbed me the wrong way from the very beginning. Since they have launched, they have displayed all the integrity of a used car salesman. I know they have some very strong core devs, and I know they are not all like this, but their public image has been max-sleaze ever since they started marketing in shady ways suggesting that they were the creators of node.js.

The stuff we are going through right now might seem scary, but McCarthyism was not exactly the golden age of trust. It was not so long ago that "mainstream" society did not trust blacks, working women, the japanese, or jews. We (royal "we" here, emphasis on the royalty) still don't seem to trust gays, atheists, or many other groups. Mistrust is what keeps humanity sharp, but it is also what has been holding us since the beginning.

> the person who says 'yes' is more likely to not be fired than the person who says no

Within reason, I completely disagree with this. The best engineers and PMs are the ones who effectively manage expectations.

This is a pretty important note. Especially on the east coast, C# is by far the easiest language to jumpstart a career in for young devs, and is a very safe bet for veterans as well. Java jobs are practically non-existent in many mid size east coast cities. I am now 100% node.js and python, but I probably would not have made it in the door if it was not for C# when I was starting out. The job market heavily favors devs, and the tooling makes it possible for self taught people to gloss over the fundamentals until they have enough time to go back and learn them. Also, if you think Stackoverflow is useful as a dynamic language dev, you would not believe how much more useful it is as a C# dev. I have no idea why, but SO seems to heavily favor C# over everything else. This is not to say that other languages get no love over there, but John Skeet alone has probably answered more obscure C# questions than all the other languages combined. I am only being half hyperbolic here.

For some reason it is saying that my ideal weight is 265, which is about 100 pounds to many. Also, it says I should be exercising 27 hrs/wk. 4 hours of exercise per day seems unreasonable.

A couple other oddities of geography I have noticed as a geospatial system developer.

- Outside the US and Europe things tend to get really wacky with geography and geospatial data. Many GIS products are licensed per country for this very reason.

- In the US, zip codes are the most terrible type of geography to use for any meaningful analysis, as they are constantly changing and do not actually have defined borders. Zip codes are basically just labels that get appended to street segments.

- If you look in the back of the ~200 page pdf that comes with most digital geographic data, you will find an appendix. 99% of the appendix is a section typically called "disputed territories", and 99% of the disputed territories are China claiming to own another nation. I never realized quite the extent of the megalomania until I read a few of those.

As someone who writes predictive analytics software, I can say that you are dead on. Most of analytics is a process of doing one of two things:

1) Extrapolation of data where samples are lacking.

2) Taking big data and making it little data so that you can actually comprehend it.

My goal in practically every algorithm/tool I write is to take a several billion records and condense it into something that can be put in a spreadsheet, put on a chart, or rendered on a map. Analysts roll their eyes every time some big data guru releases another map with 7 trillion points on it. "Oh so you took 3 weeks rendering a map that looks like yet another population map, when you could have rendered this instantaneously with a choropleth?"

This applies to type II diabetics, but not to type I. As a type I diabetic, I would be dead pretty quick without carbs. Proteins and fats can raise blood sugar, but they do it very slowly, so I would have no way to correct low blood sugars before they got out of control.

Minor nitpick, I know, but the two types get conflated often, leading to misinformation. I cannot count how many times people have been surprised that I am diabetic, since I am thin (which is normal, since it is not weight related, and actually leads to weight loss when untreated).