Should HTTP Verbs Be Used Semantically?
If I’m making a web application which integrates with a server-side backend, would it be considered best practice to use HTTP methods semantically? That is, for example, if I’m fetching data (e.g., to populate a menu, etc.), I would use GET, but to update data (e.g., save a record), I would use POST. (I realise there are other methods that may be even more appropriate, but we need to consider browser support.)
Naming methods that do the same thing but return different types
Let’s assume that I’m extending a graphical file chooser class (JFileChooser).
How to sell logistical procedures that require less time to perform but more finesse?
I am working with a group where part of the responsibilities is managing a certain set of configuration files which, of course, have the same skeleton/structure across different environments but different values (like server, user, this setting, that setting etc.). Pretty classic scenario…
Pass structure as an argument in c# method
I want to know if it is possible to pass a Structure as a parameter in c# method and if possible, is it a good practice to do so?
What is the reason behind methods with return values and methods with void?
I want to uderstand why there is a method in C# that could reurn a value, for example:
Wrapping Primitives to Enable Returning null — Bad Practice?
I am frequently tempted to wrap integers, etc, solely for the purpose of writing methods that can return null. Negative 1 can work in many cases, but too often (especially in sound) it’s a valid return value.
How and why to decide between naming methods with “get” and “find” prefixes
I always have trouble figuring out if I should name a certain method starting with getSomething versus findSomething.
Using ref instead of out. Would that be considered a bug?
Given that out and ref parameters have slight different connotations would writing code like below be considered a bug (even though it doesn’t cause an issue at present), or just a lack of understanding on ref and out parameters?
Renaming long named method in C# [closed]
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for […]
addIfNotExist alternative [closed]
Closed 9 years ago.