The Infamous Bx Codes Are Merely Diagnostic Tools
Tuesday, March 17, 2020
Edit
One bailiwick of mystery, inwards Blogger lore, concerns the infamous "bX" codes.
One forum personality, long ago, compiled a weblog listing several hundred known codes, too their supposed "diagnoses" - too would afterwards role the weblog equally a reference, when advising how to solve a given "bX problem". That same someone showed consummate lack of understanding, inwards a unmarried sentence.
In many cases, a "bX" code is only a illustration of a Blogger Engineer trying to sympathise why 1 department of code is now, magically, causing about other department of code to boot the bucket active.
One of the nearly intriguing organization problems, that I e'er worked on, long ago, involved a infirmary medical ordering organization - too a MD from Eastern Europe, who instinctively typed a "," when a "." was needed, when he was ordering medications for patients. Computer processes are real syntax sensitive - too a calculator organization that uses "," to form out sections of information from other sections of data, is going to conduct maintain a work alongside an unexpected ",", where a "." is expected.
To diagnose the problem, I had to boot the bucket along the entire organization (for a 1,000 bed hospital) offline for an hour, spell I scanned the "console log", graphic symbol past times character, analysing the transaction that caused the problem. Discovering the crusade of the work required identifying this 1 doctor, of late arrived from Eastern Europe - too an obscure detail, knowing that people inwards Eastern Europe write numbers alongside "," too "." interchanged.
Blogger code is real complex, past times necessity - from having to back upward people using different browsers alongside out of appointment versions - to having to back upward people who "confuse" syntactically essential "." too "," characters, too may write dates differently. And, Blogger code is inwards role on a lx x lx x 24 x seven x 56 basis.
There is non 1 minute inwards a 24 hr day, of a 365 (or 366) twenty-four hr menses year, that the Blogger service could e'er survive taken offline, worldwide, to diagnose 1 unmarried "bX" related problem - allow lonely an entire hour, equally was how the unexpected "," was diagnosed, then long ago.
That existence the case, diagnosis of many Blogger problems starts alongside a real distributed too structured "console log", too "bX" diagnostic details. And that is all that many "bX" codes are - structured indexes into the Blogger code base, which are referenced past times entries inwards the diagnostic logs.
There is no magic or mystery here, really. Just touchstone information technology manufacture practice.
One forum personality, long ago, compiled a weblog listing several hundred known codes, too their supposed "diagnoses" - too would afterwards role the weblog equally a reference, when advising how to solve a given "bX problem". That same someone showed consummate lack of understanding, inwards a unmarried sentence.
It's disheartening to run into that the bx mistake code problems are all the same existing.The "bX" codes are non problems - they are only symptoms of problems, identified using a canonical code structure.
In many cases, a "bX" code is only a illustration of a Blogger Engineer trying to sympathise why 1 department of code is now, magically, causing about other department of code to boot the bucket active.
One of the nearly intriguing organization problems, that I e'er worked on, long ago, involved a infirmary medical ordering organization - too a MD from Eastern Europe, who instinctively typed a "," when a "." was needed, when he was ordering medications for patients. Computer processes are real syntax sensitive - too a calculator organization that uses "," to form out sections of information from other sections of data, is going to conduct maintain a work alongside an unexpected ",", where a "." is expected.
To diagnose the problem, I had to boot the bucket along the entire organization (for a 1,000 bed hospital) offline for an hour, spell I scanned the "console log", graphic symbol past times character, analysing the transaction that caused the problem. Discovering the crusade of the work required identifying this 1 doctor, of late arrived from Eastern Europe - too an obscure detail, knowing that people inwards Eastern Europe write numbers alongside "," too "." interchanged.
Blogger code is real complex, past times necessity - from having to back upward people using different browsers alongside out of appointment versions - to having to back upward people who "confuse" syntactically essential "." too "," characters, too may write dates differently. And, Blogger code is inwards role on a lx x lx x 24 x seven x 56 basis.
There is non 1 minute inwards a 24 hr day, of a 365 (or 366) twenty-four hr menses year, that the Blogger service could e'er survive taken offline, worldwide, to diagnose 1 unmarried "bX" related problem - allow lonely an entire hour, equally was how the unexpected "," was diagnosed, then long ago.
That existence the case, diagnosis of many Blogger problems starts alongside a real distributed too structured "console log", too "bX" diagnostic details. And that is all that many "bX" codes are - structured indexes into the Blogger code base, which are referenced past times entries inwards the diagnostic logs.
There is no magic or mystery here, really. Just touchstone information technology manufacture practice.