It has to be clear that I am none of an early adopter when it comes to new technologies. Not so long ago I described my joy of discovering a use of optional and named arguments. Now is the time of dynamic.
I have been using .NET 4 for a while now but I have to admit I never thought well of optional arguments. My impressions gravitated between
- method overloading for lazy people
- hiding hideously designed APIS (Office COM Automation, I am looking at you!)
And so I have not used the feature extensively. But during the last week I have found a couple of usages that I can label as “useful”. Let me tell you about them:
Yesterday, I bumped into an article that mentions a report published by a supposedly reputed analysis firm (and I wonder what sort of company that is, anyway) in which data from a study is interpreted, implying a conclusion which does not leave “Agile” is a good position.
Unfortunately, it is only available to subscribers, so the information I was able to grasp is second-hand one. If that second-hand information is any accurate in its quotes of the original report I feel more than fine not giving my money to such sort of company; if it isn’t accurate, well, it is law-less Internet anyway…
Even if I touch briefly on the report itself, I ask the reader to take the time to read the summary, its comments and the comment from the leading article; they are enlightening, amusing and infuriating in balanced proportions.
I have spent a week heavy on the refactoring side. It’s been a while since I spent so much time on a “virgin” codebase, growing it test first. And I want to share with you, guys and girls, a piece of refactoring that ended up being pretty cool.
Previous to 2.5 came 2.2. But to highlight that changes between the two versions are pretty “dramatic” I chose to bump the version number. Fear not, not everything has been turned upside down.
It is hard to believe the last release was on September. That only means one thing: I was about time!
There are quite a few changes in the release, so I will get straight to the point(s)
2.2 should be a happy release. Why? Well, besides the fact it is the first release in more than 6 months it is the first one that contains code contributed by someone else but me.
Thank you, Berryl, for the feature, let’s hope it’s useful to many.
That is our goal with our latest initiative in the department:
spend quality time with like-minded co-workers when we have finished working. Doing what? One of the things developers like the most: writing code.
When my colleague Thomas mentioned that it could be cool if people could gather some time after work to write more code I was a bit baffled. Why on Earth would someone want to do the same he has been doing for 8-ish hours instead of going home with his family, drink beer and/or knit? The logic of his answer is flawless: “Because it’s fun. And they already do it on their own”.
Con esta expresión danesa quiero dar las gracias a todos los asistentes a mi charla de ayer en el grupo de usuarios de Madrid.NET. Fue un placer y espero que lo hayáis disfrutado casi tanto como yo. Todo el material (código, enlaces y notas) está disponible en https://github.com/dgg/Dgg.Cqrs.Sample.
No, I am not leaving beautiful, cloudy Denmark. Well… I am, but just for some days.
Why anyone cares? Because it is not for (all) pleasure. As a matter of fact I will be doing something that I had liked to do for long time: speaking in a Spanish User Group. And the guys of Madrid .NET gave me the chance to do it (thanks Luis!)
That is an enigmatic title to write about serialization. Well, sort of, as one of the meanings of the word refers to that concept.
But writing about successions is not my intention. My intention is to write about the technique that allows objects to be persisted to another medium different from their native memory space and more specifically on how to test serialization of objects.