Focusing on the human element of remote software engineer productivity.

This guide describes how to tune your AMD64/x86_64 hardware and Linux system for running real-time or low latency workloads.

This is a story of how a software company was able to start a conversation with 8x more of their users by cutting the length of their emails by 90%. You could set up a test of this method in less than an hour.

So you want to learn how to secure WordPress. Congratulations! You are in good company and this post will show you all the right steps!

Having access to source code makes it possible to analyze the security and safety of applications. But if nobody actually looks at the code, the issues won’t get caught, and even when people are actively looking at code, there’s usually quite a lot to look at. Fortunately, GitHub has an active security team, and recently, they revealed a Trojan that had been committed into several Git repositories, having snuck past even the repo owners.

With zero trust, you assume everything on the network is unsafe. You have to check trust explicitly. This stance improves security throughout the SDLC.

Worried about the security of your Linux server? Learn some easy to implement tips on securing SSH and make your Linux server more secure.

This HN thread contains several tips and hints regarding methods, approaches and tools to share secrets across people and systems.

Saying no is hard, but it's also essential for your sanity.

Here are some templates for how to say no - so you can take back your life.

How to SSH properly and easily improve the security of your SSH model without needing to deploy a new application or make any huge changes to UX.

Timo Zimmermann about software engineering, leading teams, consulting and start ups.

When polarizing topics are discussed in meetings, passions can run high and cloud our judgment. Learn how mental models can help you see clearly from this real-life scenario.

I long ago stopped reading books on note-taking.

They were always too vague and boring, full of platitudes that had little to do with the world outside academia.

I especially avoided “how-to” style books on the subject.

They would often list dozens of tips and tricks that had little to do with each other. There was never an overarching system for turning notes into concrete results.

But recently I picked up How To Take Smart Notes (affiliate link) by Sönke Ahrens. Ahrens is a Lecturer in Philosophy of Education at the University of Duisburg-Essen and also coaches students, academics, and professionals with a focus on time management, decision-making, and personal growth.

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.

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.