I abandoned Twitter some time ago, but sometimes someone will send a link to some comment there. Today such a thing happened and I got this link to a bunch of unnecessarily long twits which are actually all contained in the first one.

The following is my rather stupid and pointless answer.

Things I've learnt

I find that people saying “Over the years” rarely if ever explain if they mean 2, 20, or 200 years. In some cases it doesn't matter much, but sometimes it does. Just a small consideration.

In any case, over the years -and I mean actually over, as in: it has been an ongoing thing where I kept learning and changing my perspective in some amount or quality and that the following is just what I currently believe-, I've learned somewhat different things.


Solving the problem is primordial. Solving the problem sometimes will mean shipping code, and other times won't. Solving the problem is not fulfilled just by shipping.


The leanest the code base, the better.

Lean, n.
  1. That part of flesh which consists principally of muscle without the fat.

I want code that has all the capacity to do what it needs to do, do it in the best way possible and not contain waste. The actual size of the code will not be a goal, but rather a product or result.


Non-biased standards are usually non-existent. But I don't care too much about it.

I'll just add that personally “not caring” about a lot of uninteresting stuff makes you more open to avoiding biases… in most cases.

Alone vs Together

You need to talk. You need to talk to your co-workers, to discuss things, to ask, to answer, to help others. Especially to help others. Sure, you also need your own time to concentrate. But you shouldn't put that one above the other. So instead of being fuzzy about not talking to others, or noises, etc, try to establish some schedules and/or rules. Seek both “time alone” and “time together”.

One final thing I've learnt is: it doesn't really matter that much what I've learnt. So take all of the above with a grain of salt.