Dear dev bloggers,

If you're going to write a tutorial/example for implementing something, if you find you've done 5 screenshots and umpteen paragraphs then please refrain from using "then simply..." or "it's as simple as that"!

Always include import statements. Always. No excuses. I don't care if you can't be arsed to copy-n-paste an extra bit of code.

Nothing worse than trying to learn something new, copy-n-paste a sample code then your wonderfully helpful IDE asks you which of the 8 matching packages you wish to import.

When someone asks me, "where did you get that", I don't simply say, "a shop"!!

If you don't include your imports in answers then I hate you.

Back in the old days, ie. before facebook, I used to save all my funny email attachments to a folder. I got talking to one of the support guys. Seemed a nice fella. So, I network shared my folder and told him to how to connect. I did suggest that he probably shouldn't share it with everyone else in support as some of the material was a tad risqué.

I realised he hadn't taken notice of this advice when I walked in the office and all the support PC CD drives were randomly opening and closing and the PCs playing farting noises. (Anyone remember that?)

I had to go round all the PCs and kill the process.

I then returned to my own machine and disconnected the shared drive.

Why do people keep saying "kotlin is null safe, oh my god it's so safe, you don't have to worry about null's...". when all you have to do is add a question mark and BAM null-city!