An essay explaining why engineers tend to use the passive voice, and where it should actually be used.
- I am lazy and I use a hack
- I don’t read documentation properly
- I don’t understand the problem fully before approaching it
- I don’t always uphold the contract of an API, passing a boolean where a string is expected knowing that it’ll get typecasted
- I get invested in a solution and become stubborn
- I don’t read code review properly and don’t do my research right
The amount of email I get has increased since I joined the Wikimedia Foundation a year ago. Along with email, more written communication is expected off me on Phabricator and Gerrit. Looking at the amount of misunderstandings and arguments that happen on these channels I have developed fear and dislike for them. It might be rooted in my own insecurities of being unable to communicate well and so it needs to change.
No more flagging emails and bugs for later. I have finally gotten rid of my backlog, going through my flagged emails I found 3 month old emails that could have used my response. Starting Monday I am going to dedicate 6 hours every week responding to written communication. Rhea pointed out that deferring emails by flagging them for later is the issue. From now on I reply to email when I read it and I don’t read it as often as I do right now.