If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...

If you have a not-so-usual solution for your problems but need to justify it to your boss...

If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...

...then 'No Bugs' Hare on Soft.ware might be the right place for you.

Your mileage may vary. Batteries not included

For most of us, programming (or more generally – software development) is all the life is about.

IT Hares are not different. And they have more than just quite a few bits to share about programming…

All Not so Common Wisdoms about Programming, page 2:

CAS (Re)Actor for Non-Blocking Multithreaded Primitives

posted July 23, 2018 by "No Bugs" Hare

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.
	[→]

posted July 4, 2018 by "No Bugs" Hare

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.”
	[→]

posted June 21, 2018 by "No Bugs" Hare

Quote:	“We won’t ever get (almost) any virtual memory back, plain and simple”
Another Quote:	“relocation allows not only to reduce fragmentation, but to eliminate it entirely.”
	[→]

posted June 11, 2018 by "Goose" Hare

Quote:	“Programs are not the self-contained, self-reliant, self-sufficient things they once were.”
Another Quote:	“I highly recommend you log every HTTP request you send and every HTTP response you receive.”
	[→]

posted June 7, 2018 by "No Bugs" Hare

Quote:	“‘unchecked’ std::errors are treated as ‘something which should never ever happen, but in practice MAY occur as a result of potentially-recoverable bug'”
Another Quote:	“Failing-Fast does NOT mean we should necessarily Fail-Hard(!). In certain (production!) cases, Failing-Fast-AND-Soft IS a substantially better alternative.”
	[→]

posted May 30, 2018 by "No Bugs" Hare

Quote:	“having an ability to associate extra information with std::error is important for us – both for our own std::error exceptions, and for conversion from existing C++ exceptions”
Another Quote:	“I think that current C++ standard is Badly Lacking(tm) a concept of ‘segfault’ (which is supported by CPUs on VAST majority of modern systems with modern C++ compilers)”
	[→]

posted May 23, 2018 by "No Bugs" Hare

Quote:	“No single error handling method is good enough for ALL the projects – which in turn leads to segmentation, with some of the projects using exceptions, and some others using error codes”
Another Quote:	“Right above I said that I like the std::error exception proposal a.k.a.[P0709R0]. However, as soon as I look at competing proposals, I begin to love it.”
	[→]