We secured our first away point of the season in a match which neither team deserved to lose (if you're being generous) or win (if you're being realistic). Lots of long ball punting, some poor finishing (I headed over from 6 yards, but I wasn't the worst culprit), a few nice moves, one great save from our keeper, and two hittings of the woodwork.
I wasn't sure if people still say that they hit the woodwork (germans say that they scored an Aluminium goal, Alu Treffer), but apparently the bbc do.
Skip this bit if you neither know nor care what Matlab is
I've cheered up since yesterday, and had quite a useful day at work. For a while I have been trying to work out what to do with Matlab. There are two major problems with this program: it costs a lot of money and lends itself to terrible programming.
I know that if I was to program something well, and document it well, then the main beneficiary would be the mathworks, for my successors would be doomed to keep buying Matlab licenses in order to use my program. This combination of vendor lock-in and awful programming caused me to question what the point of it all was, but now I understand that the two problems cancel each other out. By writing awful (but quick) Matlab code I can positively encourage my successors to use anything but Matlab. I will therefore do my best to confuse imaginary numbers with loop variables (i=1), to assign floats as numbers (sin = 3) and to find further ways of making fast but unreliable code.
Skip this bit if you don't care about my toenails
Yesterday I cut off two toenails. On one toe. The outer layer was about to fall off, so I gave it a good tug, only to find a second shrivelled toenail beneath. This I cut off too, leaving a small toenail which is growing slowly upwards and outwards and some hard skin. I had to vent the room for a few minutes to remove the cheesy smell of mouldy toenail, but now things are fine, and the toe stood up to a full game of football.
Subscribe to:
Post Comments (Atom)
1 comment:
You should know from experience that badly written code will only result in frustrated and depressed PhD students who will continue to work with it, because "Why reinvent the wheel, we have good code. Fortran was good enough for me, so it should be good enough for you. And comments, why comments, just look in the code!" Where your response should be "Listen! I don't sit in code!"...
Post a Comment