LATEST CHATTY HEADER
Subscribe to Shacknews Mercury starting at $1/month!
Chrome Shack Community Guidelines Chatty Search
Scroll down to join the conversation.
New to Shacknews? Signup for a Free Account
Already have an account? Login Now
Subscribe to Shacknews Mercury starting at $1/month!
Chrome Shack Community Guidelines Chatty Search
Scroll down to join the conversation.
Example #1:
This guy writes all of his properties like this. Every single time he checks a boolean value he uses at least 10 lines of code. Every line of code has at least one blank line underneath it (usually more) What the fuck? If you need more than 3 lines of code for this you're a fucking retard. WHY????
Example #2:
This guy doesn't bother to use the private/protected/public access modifiers for anything at all. He also addss "return" to the end of every single void method and //end function after the end bracket of each function. Every single variable name is at least half-ambiguous (oh you might know it's a button, but there's no way to tell which one... WTF)
Is there a reason for this kind of crap code? Is it a leftover from AS1 or something? I'm having a hard time understanding why anyone would adopt conventions like these.
Thread Truncated. Click to see all 59 replies.
We have a new release coming up that adds a significant amount of functionality to our software. Our net LOC will be negative by a few thousand, because one of the first things I did after they cut a new tree was build a framework and set of tools for the software and refactor much of the redundant code out. I cut the size of the codebase down by something like 75% doing this. Everything's cleaner, faster, and easier to maintain.
I'm not talking about rewriting stuff like #1, either.
The post has been reported. Thank you!
You must be logged in to post.
You must be logged in to post.