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 Software Herecies about Programming, page 1:

BDT – Automating Your Application Testing in Behavior-Driven Way

Quote: “Descriptive style takes its roots from the «chain» pattern, in which the methods enclosed in classes return some reference on themselves.”
Another Quote: “Business-driven testing or BDT allows non-technical members of any development team a stronger involvement in the development process by allowing them to comprehend test cases and even create their own. “
[]

OLTP Database Optimization 102 – DIY Heterogeneous Replication (Part II)

Quote: “The point of Super-Replica is that it is a replica Slave DB which is larger than original Master DB”
Another Quote: “this “don’t write some HISTORICAL data to Master DB” approach can easily allow to reduce the load on the Master OLTP DB by a factor of 2x-3x”
[]

OLTP Optimization 102: DYI Heterogeneous Replication. Part I (Basics)

Quote: “there are still several Big Fat Reasons™ to use DIY replicas”
Another Quote: “With the Replication Messages described above, it is ok to apply Replication Messages to Slave DB which is newer than exactly necessary.”
[]

OLTP DB Optimizations 102 – Group Commits

Quote: “if we can commit several transactions at the same time – RDBMS needs to fsync() our DB logs to physical disks only once”
Another Quote: “if going our preferred way of single-writing-DB connection – make sure NOT to use RDBMS-level Group Commit”
[]

OLTP DB Optimizations 102 –100% Coherent App-Level Cache for Single-writing-DB-connection

Quote: “with our app-level cache, we’re guaranteed to get exactly the same results as if we’d be querying the underlying database.”
Another Quote: “why settle for invalidation when we can modify cache accordingly, saving on the extra DB request when we’re dealing with the same USER again?”
[]