Frustrations: Testing networked code

I hate testing network related code. Mostly because there is far too many moving parts in it.
For example you can't really unittest the actual socket itself. Because what happens if something wonky happens with the network stack? Or a process dies suddenly. How do you handle that? You can't really.

CTFE where can it go?

Over the past five months I've been working quite a lot on Compile Time Function Execution (CTFE) and what I keep seeing is at the current point in time, a lot of crazy stuff can be done. But netherless very very neat.

Compile Time Function Execution, a pattern to go by

I've been working quite heavily with Compile Time Function Execution (CTFE) and D's meta programming (templates). Each of these being quite innovative. But paired together they are quite useful.
From generation of code, to handling of UDA's.