Very confusing, at first I thought this was about https://github.com/kvz/phpjs

I volunteered for when they come to Detroit!

First step to making it better might be fixing the awful scrolling. Chrome on iOS is slick but it stutters like hell when scrolling large vertical pages. Safari has no problem.

May not even be fixable, if it's just calling out to an Apple webview component.

Seriously, it's tiring!

I want a link titled "Is Betteridge's Law Ever Correct?" to wind up on HN some day.

hahahahahahaha +10 internets

I haven't had a chance to really read it yet but it looks like it describes thread locals well.

That would make it a lot easier to maintain thread state, e.g. an open database connection, without having to use a singleton.

I prefer the "getting shit done" methodology.

Find the least amount of process necessary to get your work done and make sure everyone knows what's going on and has reasonable expectations.

It's honestly not hard to do this, and you don't need a crazy methodology to do it.

Er, that's pretty much Scrum in a nutshell :)

Not in my experience, no. In fact, it's pretty nearly the farthest thing from the getting shit done thing I've actually dealt with.

Just getting shit done doesn't mean bullshit arbitrary time-slices, half-day postmortems at the end of said timeslices, insertion of "project managers" who know little to nothing of either the actual business problem being address or the technical means used to address it, people working on a parallel svd implementation having to explain their work daily to web designers, blah blah blah.

The whole thing is a money making cult for the people who invented it, and a means of empowering a class of employees (project managers) who should exist only in very small numbers, if at all.

The claim seems to be that if you don't use scrum, you will just end up doing some horrible waterfall. This is a false dichotomy.

As naive as this comment seems, it's mostly true. Scrum is just a packaged set of practices intended to ease adoption of the agile philosophy. The end goal is to minimize process and maximize communication, which is exactly the same as "get shit done".

Thanks - I think...

That's the end goal, unfortunately there are plenty of cargo cultists that don't really understand it and think the process is the important part.

I've worked on scrum teams before, it can be done well if no one takes it too seriously IMO. Once you start guilting the team over the artifacts of scrum, it's fallen apart and become a detriment to your goal of Getting Shit Done.

This is the no-true scotsman argument. I have yet to see scrum implemented in a way that wasn't taken too seriously, that didn't make the team's life harder, etc, etc. It's just too easy to say they're all doing it wrong, if it's almost always done wrong.

Maybe the reality is that it only works for some kinds of programming, when not taken too seriously. But then why bother at all?

> And the non-judgmental, you're all special snowflakes, do whatever, is also.

Oh? How are you so sure?

~3,000 years of recorded history point to it.

Is that so?

I wonder if this same argument was made when computers first had mouses and GUIs introduced...

It's a silly, pointless argument. Absolutely without merit.

> I've never seen a plumber upset that not everyone they meet knows how to do basic plumbing. Chefs don't get mad that people they meet can't cook a fancy souffle. Why is it that so many programmers expect the world to understand computers?

You haven't? Man, every "car person" I know gets pissed off whenever someone goes to a mechanic for an oil change or tire change...

Touche.

MBSR is becoming increasingly common in cognitive behavioral therapy as well -- it's interesting (to me) to see how much intersection there is between meditative practice and what cognitive behavioral therapy is discovering. Different paths to the same conclusions.