I'm a consultant and have only been on one project in which code reviews were done. In theory, at least. When we first started development, we vowed on a code review a week, maybe two. There were two code reviews, both, actually, of my code, which were even useful. The code was printed and distributed to all developers and the QA guy, and everyone looked it over and gave feedback. It was useful. I was impressed. The first time. Then, two days later they picked apart my code again, because one of the larger egos on the team couldn't make it the first time. This was not useful.
It was also the last code review that was done.
Two months later, when the project's deadline was racing toward us at a breakneck speed, it was discovered that another of the developers had hard coded a whole chunk of the EJBs we were using. Needless to say, management demanded to know why we hadn't done more frequent code reviews. The answer? Not enough time.
If you do an hour code review, it takes at least a half an hour to prep, for both the reviewers and the reviewee. When you're on a tight deadline, you don't always have the luxury of a half hour.
I ran across this problem last year. My fiance was British and I was an American student, about to graduate. The aim was to find a job in the UK so that I could move over and be with him. Easier said than done.
I was ready to go over to the UK and look for a job over there, as it's a lot easier doing things in person than searching on monster.co.uk. Unfortunately this is an impossibility, under British law. You must have a work permit BEFORE entering the UK if you plan on working there. You cannot look for and find a job if you're only here on a visitor's permit.
This goes hand in hand with the fact that, in my experience at least, it's really hard to find a job in the UK via the regular avenues if you do not already have a means of working there. I corresponded with several potential employers via email and was turned away each time because I was not already good to work there. It's something of a catch-22.
In the end, we decided the situation was rather hopeless. It didn't look like I was going to be able to find a job as it stood. So we eloped and I got a spousal visa and all was swell. A few weeks after we did this, I got a job with an American company who agreed to send me over to its UK office. Had my husband and I not gotten married beforehand, I still would've had to have messed with a work permit even in this situation, but with a company to sponsor you, half the battle's already done.
Be wary of companies who promise to send you abroad. I very nearly got stuck in the states due to the way business was going both here in Europe and there. If you do try something like this, remember to get everything in writing and keep on those HR people so they don't forget about you.
I have to agree with this. Although I've found Gaiman's graphic novels and shorter works truly captivating, his novels have always left me at a bit of a loss. He is an undeniably gifted storyteller, and, perhaps unlike many of his peers, I think his real strength does not lie in his longer works.
Reading amazon.co.uk's synopsis, I have to admit that I'm less than intrigued. Perhaps it's a bad synopsis but it looks like he followed all sorts of random directions just for the sake of following them. Strangeness for the sake of strangeness. How stale.
Slashdot Mirror
I'm a consultant and have only been on one project in which code reviews were done. In theory, at least. When we first started development, we vowed on a code review a week, maybe two. There were two code reviews, both, actually, of my code, which were even useful. The code was printed and distributed to all developers and the QA guy, and everyone looked it over and gave feedback. It was useful. I was impressed. The first time. Then, two days later they picked apart my code again, because one of the larger egos on the team couldn't make it the first time. This was not useful.
It was also the last code review that was done.
Two months later, when the project's deadline was racing toward us at a breakneck speed, it was discovered that another of the developers had hard coded a whole chunk of the EJBs we were using. Needless to say, management demanded to know why we hadn't done more frequent code reviews. The answer? Not enough time.
If you do an hour code review, it takes at least a half an hour to prep, for both the reviewers and the reviewee. When you're on a tight deadline, you don't always have the luxury of a half hour.
beth
I ran across this problem last year. My fiance was British and I was an American student, about to graduate. The aim was to find a job in the UK so that I could move over and be with him. Easier said than done.
I was ready to go over to the UK and look for a job over there, as it's a lot easier doing things in person than searching on monster.co.uk. Unfortunately this is an impossibility, under British law. You must have a work permit BEFORE entering the UK if you plan on working there. You cannot look for and find a job if you're only here on a visitor's permit.
This goes hand in hand with the fact that, in my experience at least, it's really hard to find a job in the UK via the regular avenues if you do not already have a means of working there. I corresponded with several potential employers via email and was turned away each time because I was not already good to work there. It's something of a catch-22.
In the end, we decided the situation was rather hopeless. It didn't look like I was going to be able to find a job as it stood. So we eloped and I got a spousal visa and all was swell. A few weeks after we did this, I got a job with an American company who agreed to send me over to its UK office. Had my husband and I not gotten married beforehand, I still would've had to have messed with a work permit even in this situation, but with a company to sponsor you, half the battle's already done.
Be wary of companies who promise to send you abroad. I very nearly got stuck in the states due to the way business was going both here in Europe and there. If you do try something like this, remember to get everything in writing and keep on those HR people so they don't forget about you.
I have to agree with this. Although I've found Gaiman's graphic novels and shorter works truly captivating, his novels have always left me at a bit of a loss. He is an undeniably gifted storyteller, and, perhaps unlike many of his peers, I think his real strength does not lie in his longer works.
Reading amazon.co.uk's synopsis, I have to admit that I'm less than intrigued. Perhaps it's a bad synopsis but it looks like he followed all sorts of random directions just for the sake of following them. Strangeness for the sake of strangeness. How stale.