At AI safety camp I noticed that people are bad at math and when I look over their shoulder as they code I notice nested for loops that could have been one matrix multiplication.
Therefore I'll try offering this service to the public: You screenshare as you do your daily tinkering, I watch for algorithmic or theoretical squiggles that cost you compute or accuracy or maintainability.
Maybe some people are less effective pair programming than alone. You choose whether we pretend I'm not there, whether you think out loud, or whether we talk theory instead.
We might learn engineering from each other. I have shown multiple people IDE features such as debuggers, and I still don't know a way as elegant as I feel it should be to, say, spin up a minimal transformer implementation for tinkering in a few minutes.
If your workflow is embarassing, that's fine: You are particularly likely to benefit, and I expect this is actually quite common. Edit: For every person so far, I would prefer one like them scheduling a session to not.
I did Java years ago, Haskell less years ago and Python the last few months. Of course, pseudocode is the real language. Here's examples of me rewriting other people's Haskell code: https://codereview.stackexchange.com/users/84131/gurkenglas
Edit: I got 5 meetings from this post out of ~280 views. I'd like that percentage to be higher! My current criteria for accepting people are: If you've found this post, I'm accepting you.
It's not my one trick, of course, but it illustrates my usefulness. It's more maintainable not just because it is shorter but also because it has decades of theory behind it. Drawing the connection unlocks inspiration from entire branches of math. And the speedups from standing on the shoulders of giants go far beyond the constant factors from vectorized instructions.
At AI safety camp I noticed that people are bad at math and when I look over their shoulder as they code I notice nested for loops that could have been one matrix multiplication.
Therefore I'll try offering this service to the public: You screenshare as you do your daily tinkering, I watch for algorithmic or theoretical squiggles that cost you compute or accuracy or maintainability.
Maybe some people are less effective pair programming than alone. You choose whether we pretend I'm not there, whether you think out loud, or whether we talk theory instead.
We might learn engineering from each other. I have shown multiple people IDE features such as debuggers, and I still don't know a way as elegant as I feel it should be to, say, spin up a minimal transformer implementation for tinkering in a few minutes.
If your workflow is embarassing, that's fine: You are particularly likely to benefit, and I expect this is actually quite common. Edit: For every person so far, I would prefer one like them scheduling a session to not.
I did Java years ago, Haskell less years ago and Python the last few months. Of course, pseudocode is the real language. Here's examples of me rewriting other people's Haskell code: https://codereview.stackexchange.com/users/84131/gurkenglas
Edit: I got 5 meetings from this post out of ~280 views. I'd like that percentage to be higher! My current criteria for accepting people are: If you've found this post, I'm accepting you.
Schedule here: https://calendly.com/gurkenglas/consultation