techiferous

I was totally expecting the cure to be a gym membership. Exercise is still the gold standard of care for managing type 2 diabetes.

Hello from Boston! Come see how gridlocked all modes of transportation are during the day and suddenly this idea will shift from the "that's impossible" category to "how can we make this possible" category. We're considering gondolas for public transit, for example. All options should be on the table.

It's common on Reddit.

> we'd find our "genuine" selves

Maybe think about it this way: what are your very _deepest_ values? The things that you think make a life worth living? That's starting to touch your genuine self.

"dangerous", "worse", "rotten"...

The tone of your response has piqued my curiosity more than the content of your response. Why such a strong, negative reaction?

Just delete your account and don't look back. I did years ago and have no regrets. It's junk food.

That place has some sad history: https://en.wikipedia.org/wiki/Depopulation_of_Chagossians_fr...

That's a simple take on a very complex system.

Here is a source: http://phenomena.nationalgeographic.com/2014/04/28/how-many-...

> population to have topped 23 million by now

Assuming an error rate of about 4%, this means that about 900,000 Americans have been wrongly convicted -- about the population of San Francisco.

You're assuming all the questions are being presented to the user at once. Imagine a UI that presents questions to a user one-by-one. If the user bails out of the survey early, the rest of the survey answers can be null.

It's the difference between "this value is unknown" and "this value is known and empty". It's similar to why JavaScript has both null and undefined.

Here's an example. Let's say a user is taking a survey and the last question is: "Please share any additional thoughts if you have them." A null could mean the user did not answer this question, probably because they haven't gotten to it yet. An empty string could mean the user was asked this question and actually didn't have anything to say.

> prevents, to some extent, them taking part in a normal life

> In a way, it is kind of like blood pressure. Everyone has blood pressure, some higher than others.

Isn't this defining mental health as distance from societal mean rather than fitness for a purpose?

> The current practice of "move fast and break things" very well could be a better approach.

It's all about context. What's the cost of "breaking things"? Does your not-yet-monetized social network startup go down for a couple of hours? Or does someone die?

Also, I have witnessed first-hand the slowdown in productivity that a "move fast and break things" approach has when what you are breaking is your team's ability to work quickly and confidently with the code base.

Great tool for this: http://downforeveryoneorjustme.com/

Well, sometimes you have to hit a problem both at the source and where it manifests.

> it is very easy to anthropomorphize animal behaviour

It is also easy to assume that an animal's internal life is dumb and uninteresting.

> I find that I often have a 2 week ramp up for any given programming language.

I agree that a competent, experienced developer can do this. What's worth noting, however, is that it takes two weeks to cross the bar of "can contribute code in this language that produces deliverable results". But two weeks cannot get you across the bar of "can contribute robust, maintainable code in this language".

Even though you are not a beginner to programming, you are a beginner to the language and its ecosystem and so will still make some significant newbie mistakes. Ruby on Rails is a good example of this: half of being good at RoR is being a good programmer, the other half is memorized knowledge of the idioms and patterns of the framework and community.

Agreed. Some health problems are reversed by making healthy diet and lifestyle changes.

If your body is unhealthy because you eat too much sugar and refined carbs, and you take a pill for that, you now have two problems.

> Children wouldn't mind taking medicines so much.

This assumes children can only tolerate maximally-sweet foods like fruit juices, soda, cookies and candy. This fundamental assumption that kids won't eat healthy foods is very dangerous.

I came here to say this. It's not fair to criticize Go as not optimal for web services if it wasn't designed to be optimal for web services.

I think this oversimplifies it. I didn't grow up Amish, but I grew up in a tiny Anabaptist denomination that had a lot of cultural similarities with the Amish (but technology was allowed).

While it could be true that "those values are very dearly held by those people" you are not counting those who grew up Amish and left (or were expelled) because the values were not dearly held.

Speaking of my own experience growing up Anabaptist, I witnessed misogyny (women were not allowed to teach men) and a forced social cohesion that bordered on cult-like (people had to vow to follow very serious rules, including never to visit any other denomination, and pledge themselves to the denomination, and if they committed a "sin unto death" they were excommunicated from the community with no chance for reconciliation).

I can say with confidence that although there were some aspects of my religious upbringing that I appreciated, overall it was a bad religion that did not bring the best out of people.

Yes, exactly! Thank you for expounding. Yes, this post was indirectly inspired by LEAN, as I picked up this idea from a conversation I had with someone who used to manage manufacturing.

Thank you. I think the sociopath meme is getting a bit tired.

> You can also compare yourself to other developers, aka a leaderboard.

That's a feature with negative value. Top developers, at least in a business context, are those that help business realize their goals for their web product. One way top developers do this is to find solutions that involve writing less code, since code is a liability.

Yes, as a matter of style you could just use let everywhere, and know that var is there for legacy compatibility reasons.

True, I see your point, but you also can't just hand-wave away our results. I've been on many development teams that did not have a strong technical screen like this, and those teams suffered from having some technically weak members (people would would always be breaking the build, would write unmaintainable code, or would just plod along and always need help). Our team of six has none of those problems: every one of us is a strong and disciplined programmer.

The other benefit of the coding exercise is that it might filter out a certain level of impatience. We don't have coders who can't be bothered to follow [insert team process convention here].

Our exercise can't be cheated on because we discuss it with the candidate during the in-person interview and even ask them to change the code in a simple way.

Also, the exercise is designed to be original and so a solution can't be Googled.

I've had a different experience on the hiring side of the table. The coding exercise that we provide as part of the interview has been very successful in surfacing the skill and talent of the programmer. By using that screening device, we have assembled a team of very sharp programmers. It's totally worth filtering out people who choose not to spend the time. Even though we end up losing some potential candidates, it's worth it for a 0% chance of a mishire for technical reasons.

I disagree. If you look at what happens to the brain when it gets angry, nuance is lost in favor of over-simplified black-and-white thinking. I do agree with you that sharing conflicting points of view is good. Too much passion, however, can cloud reason.