filpen
I know what it means to feel isolated, but as you noticed you are only isolated "locally", online you can find plenty of like-minded people. Keep applying in the US if you wish, but you should know we have a lot of opportunities here in Europe as well.
I have no concrete lead for you, my professional network in Germany is limited and the companies I know require some knowledge of German, but feel free to contact me on twitter, would love to have a chat (username is the same as here).
I recently watched a TV show from a relatively old series about underground cities where they showed the underground of Istanbul. Very interesting, but I can't remember the name of the show.
From http://en.wikipedia.org/wiki/Hippodrome_of_Constantinople for instance:
"The course of the old racetrack has been indicated with paving, although the actual track is some 2 m (6.6 ft) below the present surface. The surviving monuments of the Spina (the middle barrier of the racecourse), the two obelisks and the Serpentine Column, now sit in holes in a landscaped garden."
It's cool because I think we need to bring developers together and share the knowledge, and I am convinced that pair programming is a powerful way to do it. There is much we can learn from working with people from different backgrounds.
Right now there is only a landing page with some copy, I work on the code when I find time. It's taking a while since I use this project to teach myself node.js (I am a .NET backend guy in my day job) but it's a fun side project.
It was the result of automatically porting a codebase written with a RAD system called Gupta Team Developer / SQLWindows[1]. The original language supported multiple inheritance and the converted code was a huge mess of tangled interfaces trying to reproduce that. The tool generated lots of duplicated code and some monster constructs like a static class with 140.000 lines of code, with all public methods.
I still weep for my colleagues who were left to tame that mess.
For clueless people like me, if the images used in her posts look familiar it's because she is the co-creator of the Head First book series: http://www.headfirstlabs.com/kathy.php
I see at least two problems: the leverage that the other party actually has (GEMA, DT) and the willingness of the citizens to do something about it.
[1] http://en.wikipedia.org/wiki/Blocking_of_YouTube_videos_in_G...
The Start-Up Trap
I also noticed that most of the time the container tends to be used as a Service Locator indiscriminately around the code base, which tends to create more problems than it solves. On the other hand, I think it is a good refactoring step if your plan is to eventually move all the composition logic at the entry point of the application.
Coming from .NET, I tend to do the wiring as close as possible to the entry point as well, but I still use a container because it makes object lifecycle management much easier, and with convention over configuration it is trivial to associate interfaces to implementations: this not only reduces wiring up code for complex applications to a few lines, it also makes the rest of the application container-agnostic, which is quite cool.