Comments for DanNorth.net

Comment on The perils of estimation by Quora

Quora — Thu, 23 Feb 2012 01:36:55 +0000

Is there a standard rating system for estimation of software development tasks?…

There are different methods of achieving something like you described. Methods as COCOMO, Function Points (FP), Use Case Points (UCP) and other similar ones rely on specifying different parts of a task and then add their estimates to come with an overa…

Comment on What’s so hard about Event-Driven Programming? by Delicious Bookmarks for February 22nd from 13:27 to 14:00 « Lâmôlabs

Delicious Bookmarks for February 22nd from 13:27 to 14:00 « Lâmôlabs — Wed, 22 Feb 2012 19:02:11 +0000

Comment on Introducing Deliberate Discovery by Liz Keogh's blog » It’s about the examples you can’t find, not the ones you can

Mon, 20 Feb 2012 17:50:31 +0000

[...] about uncovering the parts you don’t understand; the parts that are hard, and the gaps. Dan’s post introducing “Deliberate Discovery” takes this idea even further, but it started here: replacing the word “test” with the [...]

Comment on The rise and rise of JavaScript by exortech

exortech — Mon, 20 Feb 2012 00:59:27 +0000

great summary, dan!

Comment on The rise and rise of JavaScript by Matt

Matt — Sun, 19 Feb 2012 11:27:59 +0000

Excellent history! Maybe discuss how moving the battle from the ghetto to github was another game changer.

Comment on The rise and rise of JavaScript by Dan North

Dan North — Tue, 14 Feb 2012 16:57:41 +0000

I’m not criticising the performance of the JVM. Far from it: these days the JVM is bonkers fast. Also netty is another evented web server so it doesn’t have the same limitations of a traditional servlet container. Your coding model for netty will be similar to that of node: you respond to inbound events (requests) and ask your 10 year old JSP – which is effectively just a big print function – to produce your output.

I don’t know your specific app, but I’d be surprised if you couldn’t get the JavaScript and Java versions a lot closer in performance by understanding more about node.js and JavaScript’s performance characteristics. It’s extremely easy to write poorly-performing JavaScript, and not too hard to speed it up by orders of magnitude.

Eric Corry, one of the core V8 developers, did a talk at JAOO a couple of years ago describing some of its optimisations and how to avoid writing poorly-performing JavaScript. It might even be online somewhere.

Comment on The rise and rise of JavaScript by Tim Stokes

Tim Stokes — Tue, 14 Feb 2012 00:20:35 +0000

OK but how do I reconcile that with my test results. And I’m not arguing against the patterns, just the Node.js implementation as having a monopoly on the goodness. I’m getting 3 times the throughput with Netty v Node. Who cares if the runtime is the JVM?

Tim

Comment on The rise and rise of JavaScript by Dan North

Dan North — Thu, 09 Feb 2012 09:29:16 +0000

In that case it was probably The Goal by Eli Goldratt. It's one of the best management and organisational books I've ever read.

Comment on The rise and rise of JavaScript by The future smells like JavaScript | FreeShareHere

The future smells like JavaScript | FreeShareHere — Wed, 08 Feb 2012 11:42:44 +0000

[...] Of course I am only repeating what others are preaching about the recent rise of JavaScript. [...]

Comment on Let your examples flow by thurston

thurston — Wed, 08 Feb 2012 04:34:23 +0000

This is an interesting point of view and i largely agree with you. But the point is a larger one, i.e. it’s not only confined to tests (although tests are definitely a ripe target for this kind of thinking).
There are too many developers who subscribe to the “DRY-Dogma” as felix puts it above (apparently without irony). It’s part of a larger morbid epidemic-developers who can’t think for themselves