Over the past year, I’ve worked on and off documentation for WordPress. I started contributing during a freeze around launch to help developers transition to the new platform. I found writing documentation is something I enjoy, plus rewarding to help and educate people. Though it’s not a primary part of my job, I’ve continued to find time here and there to keep contributing.

In this time, I’ve read various resources on technical writing and documentation. These are my notes, both to help me remember later, but also as a tool to help me think about writing now.

In a world of evolving and targeted cyber threats understanding your attacker’s intentions and tools has never been more crucial. By deliberately maintaining vulnerable systems, or Honey Pots, and letting the attackers in you can analyse their activity and gather intelligence so you can be ahead of the game if you ever have a compromise. When running an SSH Honey Pot you can gain a full log of the commands an attacker attempts to run on your system and any files which they attempt to download and can be a great way to obtain samples of malicious software for analysis or understand the techniques used by an attacker to scour your data.

A few ones:

• To Jeff Dean, "NP" means "No Problemo"
• Jeff Dean's IDE doesn't do code analysis, it does code appreciation
• Jeff Dean's PIN is the last 4 digits of pi
• Google Search was Jeff Dean's Noogler Project
• Jeff Dean invented MapReduce so he could sort his fan mail
• Emacs' preferred editor is Jeff Dean
• Jeff Dean doesn't exist, he's actually an advanced AI created by Jeff Dean
• Jeff Dean compiles and runs his code before submitting, but only to check for compiler and CPU bugs
• Jeff Dean can instantiate abstract classes
• gcc -O4 sends your code to Jeff Dean for a complete rewrite
• When Jeff Dean listens to mp3s, he just cats them to /dev/dsp and does the decoding in his head
• Jeff Dean's resume lists the things he hasn't done; it's shorter that way
• Jeff Dean once implemented a web server in a single printf() call. Other engineers added thousands of lines of explanatory comments but still don't understand exactly how it works. Today that program is known as GWS
• When your code has undefined behavior, you get a seg fault and corrupted data. When Jeff Dean's code has undefined behavior, a unicorn rides in on a rainbow and gives everybody free ice cream
• When Jeff Dean says "Hello World", the world says "Hello Jeff"
• Jeff Dean traps the KILL signal
• Jeff Dean programs don't SEGFAULT. The memory rearranges itself in order to put data and code where it belongs.

Detection and attribution typically aims to find long-term climate signals in internal, often short-term variability. Here, common methods are extended to high-frequency temperature and humidity data, detecting instantaneous, global-scale climate change since 1999 for any year and 2012 for any day.

There is often the desire to start "standard" or pre-configured workspaces in tmux.
For example, run tail on two log files in a pane, or to start both vim and mysql in a pane, etc.

If you try to find information about starting tmux workspaces, you typically get advised to use wrapper programs such as tmuxinator, tmux-resurrect, or tmux-continuum. These programs may be great, but the article proposes a simpler approach.

I personally like this approach.