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.
Multi-threading at Business-logic Level is Considered Harmful
September 7, 2015 by • “No Bugs” Bunny
Quote:
However, the window for triviality is very narrow: for example, even going into two interrelated mutexes instead of one, can easily make multi-threading non-trivial
Another Quote:
Technically you are able to jump to any point of your program, but the variables you see may (and if you have a multi-threaded bug – will) differ every time you jump there.
Filed under: On.System ArchitectureDesign decisionsOn.ProgrammingDebugging
Read moreIf they wrote it in a book, it MUST BE GOOD CODE! Or How many mistakes can fit into 100 lines of book tutorial code? Part 2
August 31, 2015 by • “No Bugs” Bunny
Quote:
Throwing away 1400 bytes for no reason for every single network message is an outrageous waste
Another Quote:
Having this kind of stuff in your code is like having a time bomb: it will explode, and for any sizeable project if will usually happen sooner rather than later (unless, of course, “later” is the worst possible time for the explosion to happen)
Filed under: On.ProgrammingNetwork Programming
Read moreIf they wrote it in a book, it MUST BE GOOD CODE! Or How many mistakes can fit into 100 lines of book tutorial code. Part 1
August 24, 2015 by • “No Bugs” Bunny
Quote:
Throwing away 1400 bytes for no reason for every single network message is an outrageous waste
Another Quote:
Having this kind of stuff in your code is like having a time bomb: it will explode, and for any sizeable project if will usually happen sooner rather than later (unless, of course, “later” is the worst possible time for the explosion to happen)
Filed under: On.ProgrammingNetwork Programming
Read moreInvented a Security Feature and Is Very Proud of It!
August 17, 2015 by • “No Bugs” Bunny
Abstract:
If you're very proud of some feature - think twice if it will really work.
Quote:
One thing nobody realised for a while is that the system with the least possible amount of chargebacks is the system which rejects all transactions outright
Filed under: On.DevelopmentDevelopment Processes
Read more
Six Impossible Things Before Breakfast Ltd. © 2026. All rights reserved.
