keufran

4 ms·

1.
by keufran 7y ago
Thanks for sharing. I'll do my best to do a follow-up.
2.
by keufran 7y ago
Nice and simple idea ! Thank you
3.
by keufran 7y ago
Yes, I clearly need to understand his actual workflow to know where (and how) to "hook" the review process. Thank you for the feedback.
4.
by keufran 7y ago
I wasn't aware of these tools. I will have a look on them, thank you very much.
5.
by keufran 7y ago
Thank You @lbotos; I will email you as soon as I'm back to work.
6.
by keufran 7y ago
I hope Gitlab will fix this (it really should) but I need a solution in the meantime...
7.
by keufran 7y ago
You'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 s
8.
by keufran 7y ago
You're welcome. It's great if just raising the question help other people :)
9.
by keufran 7y ago
No I didn't. I even don't check for myself if accessibility is really bad, but I trust my coworker on this.
10.
by keufran 7y ago
No, I don't review all team's code. A point is that he will work alone on a very specific piece of code. He is junior on the technology, so I'll review mostly for educational purpose.
11.
by keufran 7y ago
OK. Thank for the tip, we will try.
12.
by keufran 7y ago
Yes, of course he will be involded by suggesting, trying and validating the solutions.
13.
Ask HN: How to handle code reviews with a visually impaired coworker?
74 points by keufran 7y ago|58 comments
14.
by keufran 9y ago
Software Craftsmanship from mancuso helped me a lot to find meaning in my work as a software devloper
15.
Quantum experiments designed by machines(phys.org)
1 points by keufran 11y ago|0 comments
16.
Exploring gambles reveals foundational difficulty behind economic ttheory(phys.org)
2 points by keufran 11y ago|0 comments