3 ms·

This raises the question of your "learning workflow". I tried something similar but found I wasn't learning much and he (it happened to be a guy) was doing all

• compacct27 6y ago
  Thankfully, mine's been the opposite. Idk your situation, but I had a well-defined project in hand before I found him. I had done some work on it already, even. When I took him on, my flow's been this: I do as much work as I can, get stuck, then he's there to pull me out of the mess I made. I learn a ton along the way, and he'll point out topics for me to research on my own. 10 hours is a large chunk, but it's lasted a full 2 months with probably a good month left in it. This project edits some PhysX engine code for an Unreal Engine-based game I'm making. The level of technical depth in it is beyond anything I've done before, so I pulled out the stops for it.
  • omarhaneef 6y ago
    Interesting. So you don't sit with him 10 hours at a time. You have him -- more or less -- on call when you get stuck for 30 minutes at a time? Or do you batch all the roadblocks you have, then ask him to schedule something at, say 10am, the next day. He looks at your git repo and the issues you have?
    • compacct27 6y ago
      Oh for sure, I chunked out my payment essentially. Our calls last about an hour at a time, and yeah, I batch all my roadblocks. It's easy to have big c++ roadblocks that take a while to debug and explain, so it's a great fit. We jump on Zoom and screenshare, but he'll look at my github separately sometimes