Disclosure: On this site you won’t find specific advice on “how to call function xyz()”. Interpreting C++ ARM and #pragma dwim is also out of scope.

We’re treating our readers as intelligent beings who can use Google and/or StackOverflow, where all such specific questions were answered more than once.

What you will find is opinions, more opinions, and even more opinions on all the aspects of software development - and with a large chunk of them based on real-world experience too.

Your mileage may vary. Batteries not included.

 

Hard Upper Limit on Memory Latency

Abstract: “Speed of light imposes hard limits on possible latencies of high-volume RAM”
Quote: “Even if each bit is implemented by single atom of silicon, 2^90-byte RAM is the largest RAM which can possibly have latencies comparable to modern DDR3 SDRAM.”
[]

A Model for Debug Complexity

Abstract: A humble attempt to make some approximation of debug complexity.
Quote: “Our model shows that coupling is a bad thing for debugging complexity, so we can consider this sanity check to be passed”
[]

‘No Bugs’ Top Five C++ Cooking Recipes

Abstract: When cooking a C++ program, there are a few spices to consider.
Quote: “If strict weak ordering is violated, all kinds of weird things can happen: from identical multiple entries in a supposedly-unique collection, to memory corruption”
[]

640K 2^256 Bytes of Memory is More than Anyone Would Ever Need Get

Abstract: Physics imposes hard limits on amount of memory we will get in foreseeable future.
Quote: “Even if every memory cell can be represented by a single atom, we would need 1 to 10% of all the stars and planets which we can see , to implement 2^256 bytes of memory.”
[]