• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Properties Vs Methods (.Net)"

Collapse

  • Drewster
    replied
    Originally posted by NickFitz View Post
    I assumed that was the case, given that it took you an hour to work out that it was causing the problems - if you were the one who'd written it you'd still be trying to work out what was wrong, and probably claiming that it must be a bug in the OS
    Good shot Sir!

    Leave a comment:


  • NickFitz
    replied
    Originally posted by wurzel View Post
    I think I should point out that this monstrosity was not my own handiwork!
    I assumed that was the case, given that it took you an hour to work out that it was causing the problems - if you were the one who'd written it you'd still be trying to work out what was wrong, and probably claiming that it must be a bug in the OS

    Leave a comment:


  • Zippy
    replied
    Originally posted by wurzel View Post
    I think I should point out that this monstrosity was not my own handiwork!
    Of course it wasn't

    Leave a comment:


  • wurzel
    replied
    Originally posted by NickFitz View Post


    Not so much "bad form" as "gross incompetence"
    I think I should point out that this monstrosity was not my own handiwork!

    Leave a comment:


  • HairyArsedBloke
    replied
    You guys have just reminded me of one place where their was someone who hated contractors and would do code evaluations by using a cyclic complexity program he had written at uni. He was always sending stuff back as being too complex. His justification was that contractors code had to be simpler as they will leave and complex code will mean the permies will spend more time understanding the code, etc.

    We got hold of his prog one day and found that simple things like bunching code into artificial functions will drop the complexity. So there were loads of funcs like void complexfunc() { partA(); partB(); partC(); partD(); }

    One other thing, I think this guy was Bob Shawadiwadi's dad or uncle.

    Leave a comment:


  • NickFitz
    replied
    Originally posted by wurzel View Post
    Is it bad form to stick loads of logic in a property getter? I personally think it is because semantically it obfuscates any logic plus the fact my debugger doesn't seem to like stepping into them. I've got one here that's got 200 lines of frikkin code behind it FFS & it's taken me nearly an hour to work out that this damn property is doing so much & is the root of all my problems!


    Not so much "bad form" as "gross incompetence"

    Leave a comment:


  • AtW
    replied
    Originally posted by Spacecadet View Post
    My first commercial dev job - functions had to be less than 1 page long (about 30-40 lines)


    What about maximum file size (in lines)?

    Leave a comment:


  • Spacecadet
    replied
    My first commercial dev job - functions had to be less than 1 page long (about 30-40 lines)

    Leave a comment:


  • wurzel
    started a topic Properties Vs Methods (.Net)

    Properties Vs Methods (.Net)

    Is it bad form to stick loads of logic in a property getter? I personally think it is because semantically it obfuscates any logic plus the fact my debugger doesn't seem to like stepping into them. I've got one here that's got 200 lines of frikkin code behind it FFS & it's taken me nearly an hour to work out that this damn property is doing so much & is the root of all my problems!
Working...
X