Comments for in two places at once

Comment on multiple return values and refactoring javascript by DCam

DCam — Thu, 29 Apr 2010 02:33:06 +0000

That’s very true! I think I’m pretty deep in to a habit of only removing duplication once I have at least about 3 example of it in front of me. It’s a bit more typing up front, but typing is not in the bottleneck in software development. Or so I’ve heard.

Once I do get around to eliminating the duplication, it’s usually a single regex to get all the call sites sorted out. I think that micro-automation makes the approach efficient enough to be viable. Not to mention the efficiency of getting the code done well.

Comment on multiple return values and refactoring javascript by Mark Needham

Mark Needham — Wed, 28 Apr 2010 23:09:54 +0000

Another thing you seem to have done quite well with this example is to not try and pull out the duplication too early but to instead let it stay there until a more obvious pattern of duplication emerges.

Pulling the duplication out too early as you point out seems to make the code way less ‘malleable’ and it’s then much more difficult to drive it to where you want to go.

Interesting post though, good stuff.

Comment on remote desktop connection to localhost: a regression in Windows 7? by Mario Gluščić

Mario Gluščić — Tue, 27 Apr 2010 15:02:14 +0000

Thank you so much.
On Windows 7 Ultimate this is true, you must have these settings you’ve mentioned (that’s OS on my desktop computer), but it actually works with localhost:3389 on my laptop (HP DV7) with Windows 7 Home Premium, both 64-bit. No idea why is like that. But even so, you really helped me and I thank you very much.

Comment on in C# 3.5: interface + extension methods = mixin by DCam

DCam — Mon, 07 Dec 2009 22:17:01 +0000

The classes are generated by svcutil to deserialize xml documents that have similar or identical structures but live in different namespaces. svcutil can’t seem to handle this situation without generating multiple classes. Perhaps the same documents in different namespaces is the root of the problem, but that decision is outside of our control.

If the classes had slightly different method names an object mapper might make good sense. We don’t have that problem though. A couple of teammates spiked out the use of AutoMapper. Looking at the spikes, we decided there was enough extra code being written for special cases that AutoMapper wasn’t of benefit.

We’ve done some of our mapping in a similar way to the examples I showed above. I might write another post about it, as it is even more surprisingly elegant.

Comment on in C# 3.5: interface + extension methods = mixin by John Sonmez

John Sonmez — Mon, 07 Dec 2009 15:29:07 +0000

Very nice! I like how simple that solution is. I am still scratching my head at classes that are almost exactly the same, but I really like your solution to the problem. What if the classes have slightly different method names though? Have you considering looking at an object mapper to solve that problem?

Comment on compiler created modules in F# by Real World Functional Programming: Book Review at Mark Needham

Real World Functional Programming: Book Review at Mark Needham — Sun, 24 May 2009 09:30:15 +0000

[...] Dave Cameron has written more about this. [...]