My name is Juri Strumpflohner and this is my technical blog. I'm a kind of jun. software architect, .Net, Android, Web and Java dev, TDD and best practices promoter and martial arts practitioner.

Recent Posts Subscribe

Eclipse: Importing existing project: "Invalid project description"

Monday morning, 07:30 AM. Me, starting the computer after the weekend, executing a git pull from my repository to fetch the latest src. Then I opened my freshly installed Eclipse JavaScript version followed by a nice "Import existing project" (I pushed the project on my Mac previously) on the just fetched git repository. Fail.

Don't Fall into the IEnumerable<T> Trap

Recently I upgraded some code of our company-internal class library and observed a plausible but still tricky problem. See yourself.

Help, Ubuntu 11.10 won't boot!!

Today I tried to start the new Ubuntu 11.10 from the live CD on the old desktop computer of my girlfriend. Her computer is quite slow and the old WinXP installation broken. So why not take the occasion and try Ubuntu :).

2011 Retrospective and a New Look

I know it's a bit late for a 2011 year recap, but I didn't manage to write one earlier. Actually, I just noted that I didn't publish one last year at all. Anyway, here just a couple of lines to 2011, the new look of this blog and maybe some outlook to 2012?

Writing IoC Supported Integration Tests using AutoFac

Using a dependency injection framework can greatly facilitate your code's testability in that you don't have any "glue" code for managing a classes' dependency that needs to be mocked (if even possible) when writing unit tests. But what about when writing integration tests? In such case you'd probably want to use your IoC container's configuration for resolving types in order to also verify the proper integration of your components, frankly your dependency injection configuration, right?

Exploring JavaScript: Scope Pollution when instantiating JavaScript Objects

John Resig has written a very interesting article (I'm not able to find just now) on how the current scope might get polluted if you're accidentally invoking a function intended as an object constructor function without using the "new" keyword in front. Here's a simple example that illustrates the issue.