
Long Absence - Design Patterns
Originally published on my old blog at cumps.be on June 24, 2008.
It’s been a while again. Real-life issues managed to take over all my time… But I’m regaining ground and winning back some of it ;)
For the first time in years, I’ve managed to get around to reading a real book again. Last week I picked up a copy of Head First Design Patterns and started on it yesterday. As far as I can tell, having only read the first chapter so far, it’s a great book!
It’s not like the usual learning books, which tend to be pretty dull when it comes to formatting or the type of language used. This book reads like a great story, filled with images to clarify and explain concepts. The images aren’t even optional: when you really want to learn, you have to read them to get the full picture.
As a form of learning, I plan to write a blog post about each pattern I finish, explaining it in my own words, so it ‘sticks’ a lot better for myself as well, helping others at the same time. Stay tuned!
You May Also Like

Obfuscation - Making Reverse Engineering Harder
A strong name doesn't stop anyone from decompiling your .NET assemblies. Obfuscation goes a long way towards keeping your code safe.

String Concatenation vs Memory Allocation
Five ways to build the same string in C#, compared on string instances and memory in a profiler: +, +=, String.Concat, StringBuilder and AppendFormat.

Code Signing as Reverse Engineering Protection
Signing a .NET assembly stops casual tampering, but stripping the strong name defeats it; why you should still sign your code.



