I got this video randomly on my recommended fee and clicked on it without checking the length. I expected this to be a 15min video essay on the topic because that's how most recent videos are. But it was super concise and clear, love it!
Short, straight forward, and simple. Good concrete advice, which basically boils down to clearly communicating the required information when asking the question. Communicating more information means there's less back-and-forth, which minimizes opportunities for communication mistakes. Very nice. Asking clear and direct questions has another bonus, which is that by asking very specific questions, you must understand what you're struggling with. Asking better questions often leads you to the correct answer, because you've taken more time to think about the problem.
Its a good tip for sure! Can also help you with your confidence its like: "I don't need help with the whole code, just this one damn line! I promise!" Thats what I tell myself at least xD
On the video. Great advice. Its always best to be clear, concise and tick off possible fixes to narrow down the problem. Chances are the co worker has been down that same road before.
Excellent guide for specific questions. On similar note, when doing code reviews, asking questions are more effective then throwing opinions at the submitter. Being curious will inspire collaboration were dictating will put people on the defensive.
I have a video on PRs on my list! I share the same sentiment there and that senior engineers should use PRs for mentorship opportunities! I just need to record the dang video :)
I got this video randomly on my recommended fee and clicked on it without checking the length. I expected this to be a 15min video essay on the topic because that's how most recent videos are. But it was super concise and clear, love it!
Thank you for the feedback! Time is precious and I’m not looking to waste anyone’s!
Short, straight forward, and simple. Good concrete advice, which basically boils down to clearly communicating the required information when asking the question. Communicating more information means there's less back-and-forth, which minimizes opportunities for communication mistakes. Very nice.
Asking clear and direct questions has another bonus, which is that by asking very specific questions, you must understand what you're struggling with. Asking better questions often leads you to the correct answer, because you've taken more time to think about the problem.
That’s a really great insight, Alex! I should have mentioned that, too.
Great video. Clear and easy to understand, just like you recommended in the video.
I’m glad you found it helpful!
Its a good tip for sure! Can also help you with your confidence its like: "I don't need help with the whole code, just this one damn line! I promise!" Thats what I tell myself at least xD
That’s a good point too! I hadn’t thought of the impact on confidence
On the video. Great advice. Its always best to be clear, concise and tick off possible fixes to narrow down the problem. Chances are the co worker has been down that same road before.
Thank you! I agree with you!
Excellent guide for specific questions. On similar note, when doing code reviews, asking questions are more effective then throwing opinions at the submitter. Being curious will inspire collaboration were dictating will put people on the defensive.
I have a video on PRs on my list! I share the same sentiment there and that senior engineers should use PRs for mentorship opportunities! I just need to record the dang video :)
I have that same vacuum
How do you like it? I loved it at first but we’ve had it for many years and the battery doesn’t last long anymore.
i wonder if this would work on chat gpt
I think specifics are pretty helpful for LLMs too