... and also why stop.

Things I hoped to get out of contracting when I started in late 2013:

  • Choose the work I'm doing. This is important to being able to show success and useful past work experience.
  • Choose the fail points/ cost rates. I dislike the “cheaply shove it together quick” attitude of most PHP. Yes, cheap has its place, but I am specialising in being a software engineer, not in being a webdesigner.
  • Demonstratable experience with SF2. The company I was working for (earlier in 2013) was investing heavily in ZF2, at the point it was much older than SF2, and less good OO. Today I could use ZF3 which has less compatibility with ZF1 and PHP4. At non-director level, I never get paid more on a company investing as little as possible in technology; but I can achieve pay-rises via high quality engineering (which for example reduces running costs by a noticeable margin).
  • Due to the networking required, know more technical people in London. This is harder on a permanent role as you have less control on your schedule.
  • Better at interviews (contractors do lots of them to start with).
  • Better at tech English, when spoken, see previous (most of my earlier experience, paid and as a student, was written). This is combined with this site that is designed at improving my written skills, and being able to express multiple linguistic registers.

None of these things are money, which is why most people do contracting.

Why is am I applying to perm roles?

  • I would like to be able to get a mortgage close to where I work. This is much simpler with a perm role.
  • I was contracting to get the above practice, and now with it; there it less benefit in keeping contracting.

why contracting?

RSS. Share: Share this resource on your twitter account. Share this resource on your linked-in account. G+

why contracting?

RSS. Share: Share this resource on your linked-in account. Share this resource on your twitter account. G+ ­ Follow edited