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.
How Blockchains Get Attacked and How Bitcoin Got Hacked, Part I
August 28, 2018 by • “Bitcoin” Hare
Quote:
Security is often cited as the foremost advantage of choosing blockchain technology over centralized systems.
Another Quote:
There are recorded cases of hackers either compromising or taking advantage of loopholes in self- executing contracts on the blockchain
Filed under: On.SecurityBest Practices
Read moreToo Much Unit Testing Is Detrimental for Code Quality?
August 3, 2018 by • “No Bugs” Bunny
Quote:
Code quality tends to be Quite Bad(tm) when there is no unit testing at all, reaching maximum when there are 0 to 10% of the unit testing methods, and degrading afterwards
Another Quote:
It is quite easy to get past the optimum amount of unit testing for your project. And whenever your unit testing starts to affect your code in a negative way – you should stop
Filed under: On.DevelopmentDevelopment Processes
Read moreCAS (Re)Actor for Non-Blocking Multithreaded Primitives
July 23, 2018 by • “No Bugs” Bunny
Quote:
in 2017, I started to feel that the Dark Ages of mutex-based thread sync were over
Another Quote:
Another issue which almost universally rears its ugly head when speaking about not-so-trivial uses of CAS is the so-called ABA problem.
Filed under: On.System Architecture(Re)ActorsOn.ProgrammingTips and Tricks
Read moreTesting Memory Allocators: ptmalloc2 vs tcmalloc vs hoard vs jemalloc While Trying to Simulate Real-World Loads
July 4, 2018 by • “No Bugs” Bunny
Quote:
if you DO want to get performance from changing mallocs, make sure to test them with your own app
Another Quote:
in our humble opinion, overall winner so far (by a nose) is jemalloc.
Filed under: On.ProgrammingOptimizations
Read more

