If you have a consistent UOM for things, then your DBA’s policy is OK. For example, if timespans are ALWAYS in minutes, etc. If the UOM could change, then you should store it in another column, alongside the qty. That said, I tend to side with you on this. Clarity trumps most things, including this. … Read more
.dist files are often configuration files which do not contain the real-world deploy-specific parameters (e.g. Database Passwords, etc.), and are there to help you get started with the application/framework faster. So, to get started with such frameworks, you should remove the .dist extension, and customize your configuration file with your personal parameters. One purpose I … Read more
In a functional programming paradigm, people usually construct abstractions not only top-down, but also bottom-up. That means you basically enhance the host language. In this kind of situations I see terse naming as appropriate. The Haskell language is already terse and expressive, so you should be kind of used to it. However, when trying to … Read more
Interesting question, but it seems to me that some developers just take it by their own worldview. It also depends on the project: Some projects are built with smaller components, which are just little pieces of the main functionality: lib. lib/independent-pieces.js Other projects are monolithic, the components depend on each other: src. src/this-is-all-for-this-project-and-depend-on-each-other.js For third-party … Read more
A link to the official design guidelines might help. Specifically, read the section on Capitalization styles. In the grand scheme of things, Pascal vs Camel doesn’t matter that much and you’re not likely to convince anyone to go back over an existing code base just to change the case of names. What’s really important is … Read more
All method names in C# start with an upper-case letter by convention. All property names do so too. Only private fields, local variables and parameters to methods start with a lower-case letter (AFAIR). It’s a convention so asking for a »why« is a little misplaced. It’s probably akin to asking »Why does the Java coding … Read more
Id is an abbreviation, not an acronym, so I case it “Id.” UI is an acronym, and acronyms–short ones, anyway–get capitalized: “UI.”
No doubt, it’s essential for understanding code to give member variables a prefix so that they can easily be distinguished from “normal” variables. I dispute this claim. It’s not the least bit necessary if you have half-decent syntax highlighting. A good IDE can let you write your code in readable English, and can show you … Read more
My standard is always PascalCase, also spell out the full word. I don’t like abbreviations as they can have multiple meanings. So, in your PascalCase scenario, I would spell out the ‘Calc’ word to be the following: public static int Factorial(int n) { return CalculateFactorial(n); int CalculateFactorial(int number) => (number < 2) ? 1 : … Read more
Emacs doesn’t have any support for namespaces, packages, libraries or modules. Emacs sources therefore use foo- as a prefix for a foo library, and in some cases foo– is used for bindings that are supposed to be internal.