There is a thread on reddit that claims the answer. TL;DR: Rust is named after a fungus that is robust, distributed, and parallel. It is also a subsequence of “robust”. Found another interesting quote: Also, calling Rust a research language is funny to me because — as its name reflects — we’ve tried hard to … Read more
Here’s some pretty basic reasons. (1) If a query (insert, update, delete) violates a constraint, SQL will generate an error message that will contain the constraint name. If the constraint name is clear and descriptive, the error message will be easier to understand; if the constraint name is a random guid-based name, it’s a lot … Read more
RFC2616 calls it an Exchange. Wireshark and HTTPNetworkSniffer call it a Request/Response. Fiddler calls it a Session. Charles calls it a Sequence. HTTP Scoop calls it a Conversation. Other vocabulary includes: Message, Transaction, Communication. I would go for Exchange or RequestResponse. I also went to name it Operation in my code as I would queue … Read more
This behavior is unfortunate and doesn’t even appear to be documented. .htaccess per-dir context Here’s what appears to happen in .htaccess per-directory (per-dir) context: Assume that Apache processes an .htaccess file that includes rewrite directives. Apache populates its environment variable map with all of the standard CGI / Apache variables Rewriting begins Environment variables are … Read more
Lower camel case is recommended for fields and parameters. Example 1: fileName // for fields, parameters, etc. FileName // for properties, class names, etc. Generally, fileName is used and NOT filename; you can verify that by reading source code of open source stuff created by Microsoft, such as Enterprise Library. Reasons: The main point behind … Read more
The System Under Test (SUT) from a Unit Testing perspective represents all of the actors (i.e one or more classes) in a test that are not mocks or stubs. In your example that would be the controller.
I’ll cite some passages from Implementation Patterns by Kent Beck: Simple Superclass Name “[…] The names should be short and punchy. However, to make the names precise sometimes seems to require several words. A way out of this dilemma is picking a strong metaphor for the computation. With a metaphor in mind, even single words … Read more
flatcase or mumblecase kebab-case. Also called caterpillar-case, dash-case, hyphen-case, lisp-case, spinal-case and css-case camelCase PascalCase or CapitalCamelCase snake_case or c_case MACRO_CASE, UPPER_CASE or SCREAM_CASE COBOL-CASE or TRAIN-CASE
I think the verb you want is ‘compose’.
I think the truth is ambiguous even from Microsoft documentation: In Visual Studio 2012 and the .NET Framework 4.5, any method that is attributed with the async keyword (Async in Visual Basic) is considered an asynchronous method, and the C# and Visual Basic compilers perform the necessary transformations to implement the method asynchronously by using … Read more