Jürgenized: Spring 리드 개발자의 이름에서 나온 코드 품질 용어

Jürgenization (명사)

당장의 문제를 푸는 데는 충분해 보이는 코드를, 견고하고 품질이 보증되며 완벽하게 문서화되고 확장 가능한 코드로 바꾸는 과정. 이 과정은 원래 코드의 전면 재작성(Karma level 0)부터 사소한 수정(Karma level 10)까지 다양한데, 보통 코드 작성자가 이 과정을 얼마나 자주 통과해 봤는지에 따라 달라진다.

Ed: Who is the most productive programmer you’ve ever worked with? What was it about them that made them that way? Did they just crank out lots of code? Did they get things done faster than everyone else? What do you say about that?

Rod: Jürgen Höller. Undoubtedly.

Ed: And what is it about Jürgen?

Rod: It’s basically all of the above, which is kind of demoralizing. Maybe the difference isn’t that big between Jürgen and other good people, but I’ve worked with some people that I would rate as better overall, but I’ve never worked with or encountered anyone who’s better in every way. For example, if I look at the other people in the Spring team, some are faster [than others], but do higher-quality code. Others do higher-quality code, but are slower. Some of them, other than Jürgen, are probably better overall, but, nevertheless, you can break it down and see differences and weaknesses. Whereas, Jürgen, compared to anyone I’ve ever seen, is faster and his code is better. You asked how does he do it? I don’t know. From what I’ve seen, it’s not just my opinion. Jürgen’s pretty legendary. What I’ve seen is that he works in a very different way from me or anyone else that I know. For example, my way of working is very iterated. If it’s a really complex problem, my first version would be embarrassing to look back on, my second version wouldn’t be too bad, and the third version would be quite good. Jürgen would start with a problem like that, and this would take maybe a lapse time of ten hours' programming if it was a reasonably hard problem. Jürgen would start off by thinking deeply about it for three hours. Then he’d spend two hours writing code, and it’d probably be perfect. I can’t work like that.