Friday, December 21, 2007

Moving to France (part 1)

I'm moving to France (Nice area) and I think I should publish some pieces of advice here for other people moving there. I'm Pole (citizen of Poland) and unfortunately I'm not allowed to work in France without work permit (that's crazy stupid! we've been in the EU for almost 4 years now!). The amount of things I had to do is huge - french immigration and work bureaucracy is horrible.

You have to prepare at least 15 (make 20 to be sure :) color photos of your face (looking straight in the camera).

You have to arrange 3 original international birth certificate (to be sure arrange one original birth certificate in your mother language).

You have to make copies of:

  • your passport

  • your ID card

  • your wedding contract (if you're married)


You have to scan:

  • 3 last payslips from your current (previous) employer

  • your passport

  • your spouse passport

  • some stuff sent to you by hiring company (that's optional I think)


I also had to pass medical examination and go to the nearest ANAEM (Agence Nationale d'Accueil des Etrangers et des Migrations) office (the only one in Poland is in Warsaw - that sucks!!! 10 hours in a train and 15 mins in the office to get a stamp and a signature).

I'm married and to be sure I translated our wedding certificate - you should do the same if you're married. If your wife/husband wants to study in France you have to arrange 3 original international birth certificate (to be sure arrange one original birth certificate in your mother language). You should also translate your secondary school certificate to French.

Last but not least you have to pack yourself and go :)

One conclusion - it takes a lot of effort and money - I hope it will pay off.

I will continue the story when I arrive to France - that could be an interesting post ;)

Friday, December 07, 2007

UML is useless (not to say sucks ;)?

Take a look at following UML class diagrams generated using Enterprise Architect:

Diagram I:


Diagram II:


I intentionally removed class names because they could disclose design patterns' names in question. But if you are medium intelligent monkey you can see that these diagrams are almost identical, nevertheless the first diagram represents State while second represents Strategy GoF design pattern.

Even if you are experienced developer who knows and uses design patterns everyday you probably don't see any difference in those diagrams, don't differentiate them and most probably don't understand them. But when you see the code everything will be clear and obvious and you'll know what's going on.

I'm asking here why should anybody use class diagrams? Maybe I generalize the problem but I really don't see any value in at UML's class diagrams. If I don't see the code I don't know the real dependencies, associations, implementations and so on, and so forth. More so when I look at class diagrams it makes the project obfuscated and unintelligible - I don't think that was the reason to invent and use class diagrams.

What are your experiences with UML?