Kenji Rikitake‎ > ‎


List of my rules of thumb (mostly coming from my Twitter timeline):
  • Fix bugs while you whine on NetNews. If you don't write code, pay for support. (circa 1994)
  • Dealing with prima donnas is simply a waste of time. (December 2010)
  • Don't sudo when you're drunk. (December 2010)
  • The worst enemies are those within the borders; always keep this in your mind. (March 2011)
  • Long-distance commuting is inhumane. (May 2011)
  • The morning rush-hour trains in Tokyo instill the rules of corporate robots in the workers. (May 2011, originally by Tatsuya Kurosaka)
  • Ops don't always make great developers; devs don't always make great ops. (May 2011, by Tim Dysinger)
  • Only those tackle with the problem and solve it deserve the honor. (May 2011)
  • Distributed version control systems such as Git are not only for the programmers; it's also for the marketing and sales people. (May 2011, originally from @voluntas on Twitter)
  • English is the Linux of human languages. Open source, fully remixable, endlessly rich. (June 2011, by Pieter Hintjens)
  • Burnout is passion unbalanced by pragmatism. (July 2011, by Dave "Dizzyd" Smith)
  • Descartes had good intentions, just wrong. Reductionism and linearity is the new smoking. (July 2011, by John Allspaw)
  • The worst bureaucratic rule is one that does not exist: there is no way it can be denounced. (August 2011, by Daniel Lemire)
  • When we give up synchronization, we of necessity give up determinism. (August 2011, by David Unger, from ACM SPLASH 2011 Invited Talk Abstract)
  • 10#53 =:= 16#35. #dns #erlang (November 2011, from one of my tweets)
  • 1st rule of Erlang Fight Club: Monitor your message queues. 2nd rule of EFC: MONITOR YOUR MESSAGE QUEUES!! (November 2011, by Dave "Dizzyd" Smith)
  • Working overtime is like shopping with a credit card. And interest is paid in productivity currency. (December 2011, by Steffan Nöteborg)
  • Check your socket options in #erlang if you don't receive the msgs you are expecting. #protip #facepalm (December 2011, by Jay Nelson)
  • Benchmarks! Numbers! Real Engineering! (February 2012, by Richard O'Keefe)
  • When you praise a technology, you express your insecurity. When you can critique a technology, you express your strengths. (February 2012, by Peter Hintjens)
  • If you use an open source product and it doesn't do what you want, don't complain. It makes you look cheap. Send a patch, or money. (March 2012, by Peter Hintjens)
  • Do something good if you want to be alive and famous, do something great if you don't mind waiting until you're dead (March 2012, by Jonathan Gray)
  • 20 yrs ago people didn't believe Internet would become an infrastructure - and I thought sequential programming was enough. I was wrong too. (June 2012)
  • If your complaints about a piece of open source software doesn't come with at least ticket/issue or a patch, I'm never going to listen. (July 2012, by John Allspaw)
  • Engineering advice: find a rich ecosystem you enjoy and live in it for a decade. Learn other things, but choose one deep dive. (July 2012, by Jay Nelson)
  • It is good if you don't understand the blogs about a programming language. It means you stand to gain something profound by learning it. (October 2012, by Alain O'Dea)