IT Hare on Soft.ware

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 on all the aspects of software development (from UI to scalability, reliability and security) for all kinds of systems (from large-scale systems to embedded ones), the reasoning behind those opinions, and tons of practical observations, which may help you to choose what you really need for your specific task.

Your mileage may vary. Batteries not included.

 

Knowledge-Sharing Architects As An Alternative to Coding Architects

BB_part083_Overload132_apr2016_v2
Quote: “Yes, a coding architect might work (and is indeed orders of magnitude better than an architect who has no clue about the code), but a knowledge-sharing architect will generally work better.”
Another Quote: “As a nice side effect, the very same knowledge sharing weakens a dependency on the architect (and reducing any dependency on a specific person is a Universally Good Thing™).”
[]

Even Bigger Brother, or Governments using Social Engineering to Circumvent Crypto

BB_part100_LockMe_v1
Quote: “Unless our Joe Average is a security specialist, he’ll install the certificate for sure”
Another Quote: “On the other hand, it is Very Clear that such a system IS a wet dream of a pretty much ANY government out there.”
[]

Random Number Generation

BB_part098_BookChapter015_v1
Quote: “even if your RNG is statistically perfect, people will still complain :-(
Another Quote: “On modern x86 CPUs, single core can generate 150M+ random bytes/second this way (and this is a Damn Lot).”
[]

Implementing Queues for Event-Driven Programs

BB_part097_BookChapter013d_v1
Quote: “full queues SHOULD NOT happen during normal operation”
Another Quote: “With queues-implemented-over-mutexes like the ones we’ve written above, the most annoying thing performance-wise is that there is a chance that the OS’s scheduler can force the preemptive context switch right when the thread-being-preempted-is-owning-our-mutex.”
[]