![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Mar. 24th, 2010
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif){kind=small}
наука Приуса
Mar. 24th, 2010 03:05 pm1. Научили меня плохому хорошему; теперь езжу на своём приусе в правом ряду, на 56, всем мешаю, зато мне никто не мешает (еду впереди пачки, наслаждаюсь музыкою Шопена и Бетховена); на данный момент приборы показывают 55.7 (что приборы? миль на галлон; хотите перевести в литры на 100 км, разделите 222 на это число, получите примерно 4).
2. Сегодня на заправке, сажусь в машину, включаю; включается, но никуда не едет. Задний ход, передний ход - нету. Отмахиваю мужику в очереди, чтоб не ждал. Рефлексирую, комплексую. Выключаю, включаю - как винду. То же самое. Потом доходит: при включении я держу ногу не на тормозе, а на газе. Помянул матерком придурка из Сан Диего, завёлся и поехал.
Такие дела.
2. Сегодня на заправке, сажусь в машину, включаю; включается, но никуда не едет. Задний ход, передний ход - нету. Отмахиваю мужику в очереди, чтоб не ждал. Рефлексирую, комплексую. Выключаю, включаю - как винду. То же самое. Потом доходит: при включении я держу ногу не на тормозе, а на газе. Помянул матерком придурка из Сан Диего, завёлся и поехал.
Такие дела.
peer code review and ascii art
Mar. 24th, 2010 03:22 pmWhile at Google, I believed in two things: peer code review and unacceptability of ascii art in the code.
Peer code review means you are supposed to show your stuff to somebody in your team before submitting it. So, when you want to submit the stuff in the end of the day (yes, all unittests pass), you are supposed to hold on, wait for half a day (the next day), not touching the code, get into a discussion, and then, eventually get through with it. Which means the code should be pretty solid. No way you would go ahead submitting something working but halfway through, or something that is in the process of being formed, in transition, work in progress.
That's bad. I found myself spending several days forming my ideas regarding how I can possibly specify binary output format in JSON, so that the format can be sent From Above to the client when requirements change (say, a new format is eventually implemented by busy/lazy server guys). If I had to submit a fully-implemented, fully thought-out, neat-looking code, it would take a couple of weeks. Thinking, prototyping, discussing, including three days of explaining how the stuff works and what JSON is, and why it is okay to use strings as keys, etc.
That's about pair programming too. Imagine pair theorem proving. Two guys are placed together by a senior mathematician, say, Grisha and Misha, and told to prove a theorem by the end of the week.
What I want to say: get the fuck off programmers' backs. If they want to work together, let them work together. If they want to work alone, let them work alone. If they want to be agile, let them be agile; if they want to be locally-convex, let them be locally-convex. On the other hand, if you, the manager, know better how to write code, how come you cannot produce in a week anything comparable to what a junior programmer can easily concoct in 30 minutes? Just kidding.
Now ascii art. Programming is art. Ascii art is a part of programming art. If a programmer thinks that his or her code reads better formatted the way the programmer formatted it, challenge this, the fact that it is, not the fact that it does not follow Coding Style Guide Laws.
Peer code review means you are supposed to show your stuff to somebody in your team before submitting it. So, when you want to submit the stuff in the end of the day (yes, all unittests pass), you are supposed to hold on, wait for half a day (the next day), not touching the code, get into a discussion, and then, eventually get through with it. Which means the code should be pretty solid. No way you would go ahead submitting something working but halfway through, or something that is in the process of being formed, in transition, work in progress.
That's bad. I found myself spending several days forming my ideas regarding how I can possibly specify binary output format in JSON, so that the format can be sent From Above to the client when requirements change (say, a new format is eventually implemented by busy/lazy server guys). If I had to submit a fully-implemented, fully thought-out, neat-looking code, it would take a couple of weeks. Thinking, prototyping, discussing, including three days of explaining how the stuff works and what JSON is, and why it is okay to use strings as keys, etc.
That's about pair programming too. Imagine pair theorem proving. Two guys are placed together by a senior mathematician, say, Grisha and Misha, and told to prove a theorem by the end of the week.
What I want to say: get the fuck off programmers' backs. If they want to work together, let them work together. If they want to work alone, let them work alone. If they want to be agile, let them be agile; if they want to be locally-convex, let them be locally-convex. On the other hand, if you, the manager, know better how to write code, how come you cannot produce in a week anything comparable to what a junior programmer can easily concoct in 30 minutes? Just kidding.
Now ascii art. Programming is art. Ascii art is a part of programming art. If a programmer thinks that his or her code reads better formatted the way the programmer formatted it, challenge this, the fact that it is, not the fact that it does not follow Coding Style Guide Laws.