Tag Archives: TechDays

Techdays

Rounding up last month – Pex, Mocks, NSK, CHESS, Linq, Silverlight, TechDays

It has been a while since I wrote anything, but that’s mainly because we have a new family member… Romée, a beautifull daughter, six weeks old!

dsc_0220

Back to the usual stuff. What have I been doing the last month. Well, there were Techdays, on which I wrote a few things but I still need to round that up. I also went looking for best practises to build a .NET layered application. The Northwind Starters Kit was most usefull for this. And there were also the Mocking frameworks, which seemed very complex at first (like everything in it it appears to be very simple afterwards…).

Pex & Chess

Very inspiring talk on Techdays about automated White box Testing and finding and reproducing Heisenbugs in concurrent programs. There was an example of a team that got a report of a bug that had to do with concurrency they just couldn’t reproduce. They let CHESS do its thing and in less than a minute they found the bug. Very impressive.

Mocking frameworks

In my Flex projects I had already used mocks, but they weren’t exactly mocks… Now that I began exploring .NET architecture, I really found out what these mocking frameworks are about. And they impressed me. Certainly the fact that if you want to use mocking frameworks you need good design, is interesting. To me it seems that a mocking framework is very good to test your base design (framework), if it’s done using principles described in books like Patterns of Enterprise Application Architecture or Domain driven Design (or others).

Northwind Starters Kit

This Kit has helped me a lot in having a good example of how you could implement a good .NET layered architecture. I also checked out DinnerNow, but things went wrong when installing (and I just hate that — if you’re limited in time, you don’t want to go looking why this or that doesn’t install properly. If I have to make installers for cd-roms, they need to work…). I’m now implementing a very small part of a product of ours with this NSK example. I will also try to check out a few mocking frameworks and a few IoC frameworks and integrate them in this small part. The best way to check out this NSK is to checkout the svn repo.

SilverLight

A few good presentations on SilverLight at TechDays. I certainly think they got a lot of advantages over Flex, but it will still take a lot of time. What really annoys me a lot is the arrogance by which some presentators present SilverLight. Anyway, their CLR seems a lot more robust that the Flash Player, but so far I haven’t seen business solutions being created with SilverLight. So I’m actually waiting a little bit on such examples. Now it’s always very simple examples or interactive sites that really don’t have to deal with a lot of data. There was a neat example of a Chess Game where they let a Javascript engine play against an .NET engine (SilverLight). SilverLight always won and could precess a lot more paths/second. A colleague of mine ported the engine to Flash, and could then compare Flash against .NET. The original game can be found here. The blog post from my colleague here. After the presentation on this, I asked a Microsoft guy how Flash would compare to this. He told me you couldn’t do this in Flash. Mmmm.

Linq

Very good presentation on Linq! Now I now what Monads are (look them up in Wikipedia). I haven’t used Linq all that much, but loving maths I’m interested in how this is implemented. The presentator quickly went deep into the subject which was fantastic (but also sometimes a labyrinth). Also the possibility to extend Linq to any other sort of data is great.

Oslo

Seemed very interesting, but I’ll have to check more examples to know how this could be used in every day development. The custom parser seemed very powerfull if you would need to convert data to another format.

Cheers, Lieven Cardoen

TechDays Day I – Architecture: The good, the bad and the ugly

I was a little bit too late for this session, but I did manage to grab the most important things. The presentation began with a lot of antipatterns and then followed with good patterns. Most of the things were rather obvious. A really funny thing was an example of the MSSQL database behind one of the first versions of SharePoint. There were like hundreds of tables with absolutely no relationships between them. Instead they created some 500 stored procedures that needed to take care of the integrity of the database… Guess there are also ‘disaster developers’ working for Microsoft.

Anti patterns

McKinsey Syndrome

  • We know it all, we don’t nee to listen…
  • They don’t know what they really want…
  • Just a cookie-cutting re-delivery…

Opposite Anti-pattern: Obedient Butler

Napkin Doodle

  • It was so straight-forward requirement…
  • We agreed on all req’s during lunch…
  • Light projects don’t need heavy process…

Opposite Anti-pattern: Documentation Overkill

Measure abuse

  • Each req must have success metrics…
  • If you can’t measure it, it is not there…
  • We need binary criteria of achievement…

Opposite Anti-pattern: Softie-softie

Start small, grow fast

  • Just for couple of users first…
  • Prototype, patch-up, deploy…
  • We’ll add scalability later…

Opposite Anti-pattern: Let’s Go Global NOW!

Best-of-breed

  • All the best tools (best database, best webserver, …) but no communications beween them…

Opposite Anti-pattern: Vendor Lock-in

YAGNI (You Ain’t Gonna Need It)

  • I’m sure nobody needs this requirement…
  • I bet this one is totally irelevant…
  • Too low on priority list…

Opposite Anti-pattern: Analysis Paralysis

Reinventing the wheel

  • We can do it better. Much better…
  • It would be boring to re-use the old stuff!
  • I trust my code and my code only.

Opposite Anti-pattern: Golden Hammer (One thing that solves everything… everything must be a nail…)

Sales-driven Design

  • We sold it, you just implement it…
  • Trust me, I’m technical too…
  • Does it work? Shut-up then…

Opposite Anti-pattern: Technological Purity

YAFL (Yet Another Fine Layer)

  • Architecture is simplicity, not intellectual violence

Good patterns

  • Modularity (degrees of freedom)
  • Open-ended systems (specific vs generic). Move from Application-Specific (solution) to General-Purpose (Infrastructure)
  • Build to grow (Wu Wei)
  • Identifier, Format and Protocol (back to the roots)
  • Middle-out Architecture (Wide range of implementations, Minimal Spec and Wide range of uses)
  • Poor-man Application Model
  • Web-Oriented Architecture
  • Lines matter more than boxes (Protocals are inherently stable, applications are not)
  • Dependency Inversion (Fold knowledge into data so program logic can be stupid and robust, What needs to be easy to understand and change goes into data, What will be stable goes into code). Data should depend on code, Code should not depend on data.
  • New-age development with MetaData and Model-Driven Design
  • Virtual worlds, virtual rules