akovalenko: (Default)
[personal profile] akovalenko
Imagine you're a tech writer, writing a protocol specification... No, imagine you're a working group designing a network protocol, striving to put as much data as possible into some 140 octets, taking care of predictable and easy decoding and backward compatibility etc.. There are really important things to decide, too, like this one:

3GPP TS 23.040 9.2.3.24.10.3.3

If there be a discussion...
``Who would use that stupid #x01? From my experience, GTFO is to be put in its place!''
``You guys, like, have never been a teena^H^H^H^Hypical SMs user. Where is `depressed'? Who needs this `sceptic' at #x02?''
``Calm down, do we have to illustrate #x0C here?''
``Are we having revenge of the nerds or what? Look what I propose for #x0D''
But apparently there wasn't: debates over code space allocation are impossible when 240 of 255 code points is free.

A phrase to start a sci-fi novel (probably about robots' romantic relationships): ``Of course she loved him too, but in a very manufacturer-specific way.''
From:
Anonymous( )Anonymous This account has disabled anonymous posting.
OpenID( )OpenID You can comment on this post while signed in with an account from many other sites, once you have confirmed your email address. Sign in using OpenID.
User
Account name:
Password:
If you don't have an account you can create one now.
Subject:
HTML doesn't work in the subject.

Message:

 
Notice: This account is set to log the IP addresses of everyone who comments.
Links will be displayed as unclickable URLs to help prevent spam.

January 2017

S M T W T F S
1234567
8910 11121314
15161718192021
22232425262728
293031    

Style Credit

Expand Cut Tags

No cut tags
Page generated Oct. 22nd, 2017 01:37 pm
Powered by Dreamwidth Studios