It was also going fine for me up to that section but for different reasons: I think it makes sense to postpone/avoid externalizing configuration, but in case where a configuration is the default format (e.g. logging), going the extra mile to define that in code is both time-consuming and produces a less readable result. So I think the goal should not be to avoid configuration files, just avoid wasting time in making things configurable which probably never need to be re-configured.
Ditto. Also switching between US for coding and my local layout and I think it's definitely worth it due to the ease of typing the slashes and brackets when coding.
The author preparation feature (#4) could indeed be useful, sometimes it takes quite a bit of time, especially if one is not very familiar with the system, to see how they fit in.
We have implemented this using something we call the overview meeting, or the architecture meeting.
It is an optionally requested meeting at the beginning of the review process. In this meeting, the goal, the general structure of the software and the general structure of the changes are discussed on a high level for about 10 minutes. Afterwards, we decide which classes are focus in the review, which classes are kinda part of the review but boring. Sometimes the review is even removed because the changes are too small.
Overall, it's a very helpful meeting, especially for people new on a project. Confusion changes into understanding and focus with just a few words and a simple informal diagram and from there, very precise and productive code reviews follow.
Yes, this sounds like it is well worth the time. Not that in my current project it would be unthinkable to go and ask the original coder for some extra info but people tend to be busy and it tends to feel a bit like wasting their time.
* minor correction to my original post - "they" refers to the code changes
It really seems to me that in general programmers have such an good life that they (we) have to find something to complain about. I'm not pointing any fingers, since I often have the same thoughts. There was actually a quite nice article on HN lately (I read it on Sunday, but my google-fu is failing me), something along the likes of "Why wouldn't you want to be a programmer?", which arrived to the same conclusion as I usually do after trying to compare it to many other professions in an unbiased way: overall programming is quite a sweet deal.
I have to admit though that I never held any other jobs, so I'm very interested in reading about the opinions of those that have.
Open the door all the way until it hits the wall, throw a towel over it, and start doing pullups. Some people use workout gloves, but it's basically anything that will serve as padding. The door will hold, for sure.
Your point is also very valid though.