In Germany you feel like somebody from today running around in the 1920's telling people that computers are the future while they are still reluctant to use typewriters.

STOP PUTTING TWO SPACES AFTER PUNCTUATION THIS ISN'T 1900 ANYMORE AND YOU WEREN'T EVEN BORN YET IN THE TIME OF TYPEWRITERS

Computers and their peripherals are constantly advancing, but keyboards... keyboards never change, We pretty much just stole the idea from typewriters and moved on.

It's 2017 and every keyboard on Earth still has vertically unaligned keys !
And if you think it's for ergonomic reason, you're wrong ! It's just something we inherited from goddamn typewriters.
It's time to let that go !
Far far away in the past.
Right next to floppy disks, MySpace and Nicolas Cage !

Ah, the little subtle things we have to iron out as we progress from Junior Developer to Medior Developer.. things like:

- knowing the difference between a carriage return and a line feed (although having worked with analog typewriters helps) and later knowing that Unix-based systems and Windows NT-based systems implement it differently..

- knowing that serialization is important because not all computers interpret data the same way and some computers allocate 4 Bytes for a construct, others 16 Bytes.. and then we get the funkiness of transferring character sets between machines..

- knowing that a whitespace character is not only an actual space (as is known in ASCII as code 32). This one can cause even medior developers a headache, as in: why the fuck does this string function say that "hello I am a duck" and "hello I am a duck" are not the same?! Turns out then in the debugger that when you expand every character in the string you see that string1 contains 32 32 32 32 as usual.. but then string2 contains -96 -96 -96 -96 and you're like.. what the fuck..? Then you know you have to throw \\h regex at it. Haha.

- finalizing our objects and streams (although modern languages do that for us).. otherwise we have to do funky shit like trying to find what's locking a file, which is not so easy to figure out.

- figuring out why something won't work often requires you to not only break down the problem in smaller steps, to use a debugger, but sometimes it's even better to just create a proof of concept, slap some minimal code in there and debug that.. much easier.

- etc.

:)

god... why is the stupid "tAbS oR sPaCeS?" still around, it's like some stupid ass HR person got it long ago and it's never gone away. nobody has used tabs to write or format code since like the 1950s when there were mechanical fucking typewriters! and if you use them today in your editor, you're WRONG

I will die on this hill.

Looking up typewriters for my boss. Really???

Receiving content in word littered with carriage returns and double spacing. They haven't figured out paragraph spacing (which will automatically add a desired gap between paragraphs) or that double spacing after a full stop died out after monospaced manual typewriters ceased to exist. For some this is the only Application they use and they still haven't figured out how to do the most basic shit. Useless Cunts.

DOS and Wordstar, I was one of the few kids who submitted assignments on printouts from a dot matrix printer while everyone else was using typewriters. But what really got me hooked on computers? SimEarth and SimCity.