The code-style tag has no wiki summary.
68
votes
25answers
5k views
Is fewer lines of code always better?
Which of these programming styles is better?
var result = methodOne(methodTwo(a, methodThree(b)), c, d);
or
var result3 = methodThree(b);
var result2 = methodTwo(a, result3);
var result = ...
42
votes
8answers
3k views
What's the right balance between code consistency and code improvement?
Recently I had a discussion with a colleague regarding code style. He was arguing that your usage of APIs and the general patterns you are using should be as similar as possible with the surrounding ...
25
votes
16answers
2k views
Are short identifiers bad?
Are short identifiers bad? How does identifier length correlate with code comprehension? What other factors (besides code comprehension) might be of consideration when it comes to naming identifiers?
...
16
votes
9answers
1k views
Hiding away complexity with sub functions
I am having a discussion on code style, and it's starting to sound like a "matter of taste". I strongly believe otherwise, so I'm writing this to get your opinion and learn from your arguments for and ...
16
votes
3answers
620 views
How to camel-case where consecutive words have numbers?
Just wondering if anybody has a good convention to follow in this corner-corner-corner case. I really use Java but figured the C# folks might have some good insight too.
Say I am trying to name a ...
13
votes
4answers
523 views
Is there justification for leaving conflict markers in checked-in code?
Consider conflict markers. i.e.:
<<<<<<< branch
blah blah this
=======
blah blah that
>>>>>>> HEAD
In the particular case which has motivated me to post ...
10
votes
6answers
703 views
Struggling with the Single Responsibility Principle
Consider this example:
I have a website. It allows users to make posts (can be anything) and add tags that describe the post. In the code, I have two classes that represent the post and tags. Lets ...
7
votes
3answers
580 views
“how bad” is unrelated code in try-catch-finally block?
This is a related Q:
Is use of finally clause for doing work after return bad style/dangerous?
In the referenced Q, the finally code is related to the structure used and the necessity of ...
6
votes
3answers
319 views
What is your approach to multi-paradigm programming?
I have been learning some Ruby recently and I had the following experience.
I had written a small tool of about 200 lines of code and, as an inexperienced Ruby programmer, I had used several loops to ...
6
votes
3answers
198 views
“static” as a semantic clue about statelessness?
this might be a little philosophical but I hope someone can help me find a good way to think about this.
I've recently undertaken a refactoring of a medium sized project in Java to go back and add ...
6
votes
1answer
144 views
Is deep nesting of control flow in code a studied problem?
I made the case to coworkers that deep levels of control flow was harmful to the readability of code.
Example, taken from the relevant stack overflow question If you need more than 3 levels of ...
5
votes
5answers
291 views
Static functions question
Something came to my mind today. I have been doing a lot of the following
new Object().doSomething();
I create an object and call on of its functions, then forget about the object. I don't need it ...
4
votes
5answers
402 views
What happened to the this type of naming convention?
I have read so many docs about naming conventions, most recommending both Pascal and Camel naming conventions. Well, I agree to this, it's ok. This might not be pleasing to some, but I am just trying ...
3
votes
1answer
152 views
Using T[1] instead of T for functions overloaded for T(&)[N]
The asio::buffer function has (void*, size_t) and (PodType(&)[N]) overloads.
I didn't want to write ugly C-style (&x, sizeof(x)) code, so I wrote this:
SomePacket packet[1]; // SomePacket is ...
3
votes
1answer
185 views
Should methods always return from one place? [duplicate]
Possible Duplicate:
Where did the notion of “one return only” come from?
I got into a little argument with a coworker about whether a method should be written like this:
public Thing ...
