4 ms·
"We could do physical Code Review sessions, but it's difficult because I've a very chaotic schedule" Aren't you a developer? You're not a manager? Can you expl
by debt 7y ago
"We could do physical Code Review sessions, but it's difficult because I've a very chaotic schedule"
Aren't you a developer? You're not a manager? Can you explain why you have a chaotic schedule? If you don't code, why are you doing code reviews then?
Seems like that's the fundamental problem right there. You said so yourself, physical code reviews would solve it. So that's the solution, the problem is your schedule, fix your schedule.
You're making this person accommodate your schedule(in addition to their own), because you don't want to do your job. Again, unless I'm missing something.
- jrockway 7y agoProgramming is to software engineering as telescopes are to astronomy. It's one tool that you use, but is not the only tool you use. Planning what you're going to make is as important as making something; as you move higher up in your career development, you will realize that a few hours of talking can save months of work. It seems "productive" to spend months at a time programming, but if nobody uses what you produced, how productive is it really?
- deleted 7y ago[deleted]
- keufran 7y agoYou're absolutly right, and I'm looking to improve this. However this is not the only pain point. The amount of remarks you can do in a code review can be huge, and I don't expect my coworker to be able to remind all what I say. So I also need a "place" where to put the remarks that he could refer to at his own pace.
- traviscj 7y agoMaybe a digital voice recorder thing (like [1]) so neither of you has to take explicit notes but can still capture all the discussion? [1]: https://www.amazon.com/Sony-ICDPX370-Digital-Recorder-Built/dp/B06XFTWCBJ https://www.amazon.com/Sony-ICDPX370-Digital-Recorder-Built/...
- keufran 7y agoNice and simple idea ! Thank you