188 reputation
5
bio website paulhadfield.net
location Worthing, United Kingdom
age 41
visits member for 3 years, 3 months
seen Aug 6 '12 at 14:55

.NET developer, based out of Worthing and an active member of Brighton ALT.NET Group.

Check out my blog at blog.paulhadfield.net


Apr
3
comment Letting go of a project
Without knowing more of the details, is it time to completely re-evaluate your career. Is this a good time/point to move onto something completely new. It would certainly force the "transition" and might be good for you too!
Jun
8
answered Best way to break down overwhelming code into manageable chunks?
Jun
7
awarded  Student
Jun
7
awarded  Scholar
Jun
7
accepted Does a License Change for OSS cover all versions, including previous releases?
Jun
7
comment Does a License Change for OSS cover all versions, including previous releases?
OK, thanks for the link to the book - looks well worth a read and the second link for the short answer.
Jun
7
asked Does a License Change for OSS cover all versions, including previous releases?
May
31
comment Any tips how to successfully job hunt?
Another reason they don't like non-word CV's is that it's harder for agencies to edit. Why? Because when they send your CV over to employers, it is (1) branded with their logo, etc. and (2) your address/contact details have been removed so the company can't contact you directly. Point 2 can actually mean that any blog/website links you have to show off your work are removed if they again open up a "contact directly" approach.
Apr
15
answered What are the most cost effective ways of increasing your marketability to employers
Apr
15
comment How to represent an agile project to people focused on waterfall
Good luck with your efforts, hopefully you can get people on board.
Apr
14
comment How to Identify Bugs
You can do two things, accept, find another way and carry on. Or you could slice and dice your tests and eliminate the uncertainity. Try several different ways to replicate the problem and make sure there is no external influence causing the problem. If you can really isolate and replicate the problem then first, give youself a pat on the back because it doesn't happen very often! Then if there is a process for reporting the bug, then check it's not already been reported and post your findings and isolated tests. If it's actually an OSS project you could even post a fix!
Apr
13
awarded  Teacher
Apr
13
answered How to represent an agile project to people focused on waterfall
Apr
13
answered How to Identify Bugs
Apr
13
awarded  Supporter
Apr
13
answered Learning Test Driven Development
Apr
13
awarded  Autobiographer