Item #: SCP-000B0E1F-0000-0000-C000-000000000046
Object Class: Euclid
Special Contained Procedures: API proposals known to be written by personnel infected with SCP-000B0E1F-0000-0000-C000-000000000046 are to be re-written by uninfected software architects. Personnel known to be infected with SCP-000B0E1F-0000-0000-C000-000000000046 are to be treated with counter-memetic therapy and removed from duty until they show no further signs of infection. They are to afterwards be monitored for signs of relapse. Individuals outside the Foundation found to be carrying SCP-000B0E1F-0000-0000-C000-000000000046 are to be treated with Class-A amnestics if practical, or otherwise removed from positions where they can potentially infect others.
Denoscription: SCP-000B0E1F-0000-0000-C000-000000000046 is a memetic compulsion to switch endianess in data structures or otherwise enforce compatibility with random standards when writing API proposals. It is most prevalent in those dealing with database engines.
Infected subjects will, when writing API proposals, find that apparently random parts of data structures having certain endianess will seem disproportionately important. This thought will be treated as though it is at the highest level of impact on distributed systems the writer is familiar with. They will do so even after it has been shown that endianess isn't particulary important and that it's possible to switch the on-the-wire encoding format at will.
SCP-000B0E1F-0000-0000-C000-000000000046 is spread by reading infected material or discussion with infected individuals. Those most at risk are those participating in .NET user groups and .NET-related discussions. Infection can be easily prevented by maintaining a solid grounding in the rules and regulations governing usage of data structures and serialization within the organization.
SCP-000B0E1F-0000-0000-C000-000000000046 was discovered in 2010-s at [DATA EXPUNGED] when a discrepancy was noticed by [DATA EXPUNGED], a Foundation operative embedded
Object Class: Euclid
Special Contained Procedures: API proposals known to be written by personnel infected with SCP-000B0E1F-0000-0000-C000-000000000046 are to be re-written by uninfected software architects. Personnel known to be infected with SCP-000B0E1F-0000-0000-C000-000000000046 are to be treated with counter-memetic therapy and removed from duty until they show no further signs of infection. They are to afterwards be monitored for signs of relapse. Individuals outside the Foundation found to be carrying SCP-000B0E1F-0000-0000-C000-000000000046 are to be treated with Class-A amnestics if practical, or otherwise removed from positions where they can potentially infect others.
Denoscription: SCP-000B0E1F-0000-0000-C000-000000000046 is a memetic compulsion to switch endianess in data structures or otherwise enforce compatibility with random standards when writing API proposals. It is most prevalent in those dealing with database engines.
Infected subjects will, when writing API proposals, find that apparently random parts of data structures having certain endianess will seem disproportionately important. This thought will be treated as though it is at the highest level of impact on distributed systems the writer is familiar with. They will do so even after it has been shown that endianess isn't particulary important and that it's possible to switch the on-the-wire encoding format at will.
SCP-000B0E1F-0000-0000-C000-000000000046 is spread by reading infected material or discussion with infected individuals. Those most at risk are those participating in .NET user groups and .NET-related discussions. Infection can be easily prevented by maintaining a solid grounding in the rules and regulations governing usage of data structures and serialization within the organization.
SCP-000B0E1F-0000-0000-C000-000000000046 was discovered in 2010-s at [DATA EXPUNGED] when a discrepancy was noticed by [DATA EXPUNGED], a Foundation operative embedded
😁31❤16👍3🐳3👎1