First of all, find an english speaking company. There's many out there in Europe, where everyone will speak English in the office, even between French, or Italian, or Dutch. That's a good start.
You can pick up a new language while you're there.
Also, note that the salaries over there are nowhere near what you make in the US. You'll earn half or (a lot) less for the same work. Of course, the cost of living is lower as well, but keep it in mind if you have payments to make in the US.
Also, the culture is different in Europe: contracts are more binding than in the US: you'll have to tell them you're moving on months in advance instead of not returning from lunch (as you could do in the US). The benefits are different as well. You may get coverage from the company for the first three months as you're 'in you trial period'.
Taxes get messy if you have both US and European income.
But it's worth it. I worked in London for three months and it was great. Rome would be even better...
Just wondering if anyone know if this device (or any other car mp3 player!) can be controlled by the on-steer volume controls. I have a BMW, don't know how standard those controls are.
After three years of merely Coding Cool Stuff, I've also had to make the transition to management. The first project that I lead was horible. I mean it went well, but instead of coding (and I was promised only 20% management -- but it was more like 95%) you spend all your time
1) Talking to your managers and other stakeholders of the project. Because they did not give you what they promised.
2) CYA: Cover Your Ass. Since you didn't get what you needed, you better make sure that everyone knows that you're not holding things up, but someone else is. Otherwise it means trouble later on.
3) Trying to figure out what The Right Thing to do is. You can do what your manager tells you, but if he doesn't have a clue what he's talking about, then you (if you're good) have to figure out a way to both please him AND make the project something useful for the client/stakeholders.
4) And luckily, if you're merely a squad leader, you get to deal with your team. Which is wonderful: real techies like you think you are. You can direct them, and help them solve problems. The key here is Delegate. You won't have time to dive into The Good Stuff yourself. But you'll have to TRUST your team members, let them do it and check up on them once in a while. I you have a relaxed attitude and are able to teach them your Wisdom, they'll love you.
I've found my interest (at work) shifting towards Things That Stay. Programming languages and tools tend to evolve, but things like Extreme Programming, Unified Process and UML are/will be around much longer. So I'm trying to get experience in those areas. Which actually is fun. And being a manager you get to say (more or less) how things will be done, so you can actually try out stuff.
Here's some books:
Booch, Jacobson, Rumbaugh: The Unfied Software Development Process
Kent Beck: Extreme Programming explained
Betrand Meyer: OO Software construction
Craig Larman: Applying UML and Patterns
There's many more, but these are a good start. They'll tell you all about managing a software project, without the management stuff...
Of course, there is always the itchy fingers when you get home. That's why you need a good PC and internet connection, as some friends. Together you'll lauch a new SourceForge project to stay in touch with the latest technologies. Basically coding like you always did. The tech stuff. The real you.
Hey, H1b-ers you just gotta be smart about. You know this is coming. So if you want to stay, pick a good company. (This also works for changing companies -- H1b transfers take close to three months these days)
The company must
1) Sponsor green cards, get started asap.
2) Have international offices.
I just worked in Europe for my new company while waiting for my H1b transfer to come in. I got my US salary, and my housing was paid for. Got to hang out with my old friends, too. Now I'm back in the US. When my H1 runs out in about three years, I have no problem working in Europe again, on the same terms, if my green card hasn't come through yet. While in Europe you can vacation in your US home for up to three months. What a deal!
Anyone know how long a `business trip` can be: ie. work for european office/company but travel to US and do some work.
Off topic Question: at some point in the green card process you are allowed to stay, even though you have not received the green card yet. Anyone know when this is?
Slashdot Mirror
First of all, find an english speaking company. There's many out there in Europe, where everyone will speak English in the office, even between French, or Italian, or Dutch. That's a good start.
You can pick up a new language while you're there.
Also, note that the salaries over there are nowhere near what you make in the US. You'll earn half or (a lot) less for the same work. Of course, the cost of living is lower as well, but keep it in mind if you have payments to make in the US.
Also, the culture is different in Europe: contracts are more binding than in the US: you'll have to tell them you're moving on months in advance instead of not returning from lunch (as you could do in the US). The benefits are different as well. You may get coverage from the company for the first three months as you're 'in you trial period'.
Taxes get messy if you have both US and European income.
But it's worth it. I worked in London for three months and it was great. Rome would be even better...
Good luck.
Just wondering if anyone know if this device (or any other car mp3 player!) can be controlled by the on-steer volume controls. I have a BMW, don't know how standard those controls are.
After three years of merely Coding Cool Stuff, I've also had to make the transition to management. The first project that I lead was horible. I mean it went well, but instead of coding (and I was promised only 20% management -- but it was more like 95%) you spend all your time
1) Talking to your managers and other stakeholders of the project. Because they did not give you what they promised.
2) CYA: Cover Your Ass. Since you didn't get what you needed, you better make sure that everyone knows that you're not holding things up, but someone else is. Otherwise it means trouble later on.
3) Trying to figure out what The Right Thing to do is. You can do what your manager tells you, but if he doesn't have a clue what he's talking about, then you (if you're good) have to figure out a way to both please him AND make the project something useful for the client/stakeholders.
4) And luckily, if you're merely a squad leader, you get to deal with your team. Which is wonderful: real techies like you think you are. You can direct them, and help them solve problems. The key here is Delegate. You won't have time to dive into The Good Stuff yourself. But you'll have to TRUST your team members, let them do it and check up on them once in a while. I you have a relaxed attitude and are able to teach them your Wisdom, they'll love you.
I've found my interest (at work) shifting towards Things That Stay. Programming languages and tools tend to evolve, but things like Extreme Programming, Unified Process and UML are/will be around much longer. So I'm trying to get experience in those areas. Which actually is fun. And being a manager you get to say (more or less) how things will be done, so you can actually try out stuff.
Here's some books:
Booch, Jacobson, Rumbaugh: The Unfied Software Development Process
Kent Beck: Extreme Programming explained
Betrand Meyer: OO Software construction
Craig Larman: Applying UML and Patterns
There's many more, but these are a good start. They'll tell you all about managing a software project, without the management stuff...
Of course, there is always the itchy fingers when you get home. That's why you need a good PC and internet connection, as some friends. Together you'll lauch a new SourceForge project to stay in touch with the latest technologies. Basically coding like you always did. The tech stuff. The real you.
Go for it!
Hey, H1b-ers you just gotta be smart about. You know this is coming. So if you want to stay, pick a good company. (This also works for changing companies -- H1b transfers take close to three months these days)
The company must
1) Sponsor green cards, get started asap.
2) Have international offices.
I just worked in Europe for my new company while waiting for my H1b transfer to come in. I got my US salary, and my housing was paid for. Got to hang out with my old friends, too. Now I'm back in the US. When my H1 runs out in about three years, I have no problem working in Europe again, on the same terms, if my green card hasn't come through yet. While in Europe you can vacation in your US home for up to three months. What a deal!
Anyone know how long a `business trip` can be: ie. work for european office/company but travel to US and do some work.
Off topic Question: at some point in the green card process you are allowed to stay, even though you have not received the green card yet. Anyone know when this is?
Hope this helps...