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

Each and every of successful team leads has their own philosophy. And while there is no “one correct” philosophy (in the very same manner as there is no “one correct” religion), different philosophies lead to different results.

Of course, as successful team leads, IT Hares have their own philosophy, which they’re not ashamed to share.

Development Philosophy, page 1:

Bringing Architecture of Operating Systems to XXI Century – Part I. Changes in IT Over Last 50 Years

posted by

Quote: “we’re using operating systems which were designed whopping 40-50 years from now”
Another Quote: “Do not communicate by sharing memory; instead, share memory by communicating.”
[→]

C++: “model of the hardware” vs “model of the compiler”

posted by

Quote: “we MUST NOT care about compiler internals beyond our task definition (which is based on (a) humans, and (b) hardware, that’s it).”
Another Quote: “My problem with introducing a ‘model of the compiler’ into the picture, is that it can be used to justify pretty much anything without any relation to real-world requirements.”
[→]

Unchecked Exceptions for C++

posted by

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

Knowledge-Sharing Architects As An Alternative to Coding Architects

posted by

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

DIY vs Re-Use: In Search of Balance from upcoming book “Design&Development of MMOG”

posted by

Quote: “The biggest problem with building your game around 3rd-party game engine is that in this case, the game engine becomes your Absolute Dependency”
Another Quote: “In future chapters we will keep in mind three specific game/network engines, and will discuss their pros and cons with relation to the issues we are raising. These engines are Unity 5, Unreal Engine 4, and Photon Server”
[→]
Copyright © 2014-2016 ITHare.com