It may be more interesting as a dual host format, where one person is knowledgeable and the other is asking questions. Otherwise it can get monotonous to simply hear someone read a summary.
Crashes are the easiest bugs to self-fix.
I'm sorry, but this seems to be a string of letters and symbols without a clear meaning or context. Can you provide more information or clarify what you're looking for assistance with?
Because IRL you're effectively always in call. Not sure whats hard to understand about the difference.
Your code reviews are doomed regardless if the feedback cycle is 1 day.
"It works" is perhaps the lowest bar you can possibly have for merging code.
Why would you rewrite them as loops?
Your comment implies juniors are only juniors for a temporary amount of time. I've worked with many SWEs (some with years of FAANG experience) who consistently code like juniors. They are aware of things like the…
No linter? Seems like a quick thing to standardize
Did not work for me
No wonder it succeeded.
It may be more interesting as a dual host format, where one person is knowledgeable and the other is asking questions. Otherwise it can get monotonous to simply hear someone read a summary.
Crashes are the easiest bugs to self-fix.
I'm sorry, but this seems to be a string of letters and symbols without a clear meaning or context. Can you provide more information or clarify what you're looking for assistance with?
Because IRL you're effectively always in call. Not sure whats hard to understand about the difference.
Your code reviews are doomed regardless if the feedback cycle is 1 day.
"It works" is perhaps the lowest bar you can possibly have for merging code.
Why would you rewrite them as loops?
Your comment implies juniors are only juniors for a temporary amount of time. I've worked with many SWEs (some with years of FAANG experience) who consistently code like juniors. They are aware of things like the…
No linter? Seems like a quick thing to standardize
Did not work for me
No wonder it succeeded.