> When you can't predict what your program is going to do, you also have a hard time debugging your own code (debugging, after all, is finding out how the program works different in reality from what it should be doing).
This also spoke to me. It seems like half the time I see a bug, I know exactly what it is. I haven't started an actual debugger in months, maybe longer. On other occasions I'll know exactly where a print statement goes.
I think it's because, sure, I know what I want, but I still keep track of exactly what I've written as well. I understand how the program works to achieve that goal.
> they are constantly asked to write a short piece of code and then run it to confirm you are still in sync with the tutorial.
When I first started learning Rust, I opened the Book and Ray Tracing In One Weekend side by side, and implemented an interactive multithreaded path tracer. :)
Sometimes I feel bad about how impressive that sounds when in reality I'm a total ADHD mess. But I guess at least I know what I'm doing.
This also spoke to me. It seems like half the time I see a bug, I know exactly what it is. I haven't started an actual debugger in months, maybe longer. On other occasions I'll know exactly where a print statement goes.
I think it's because, sure, I know what I want, but I still keep track of exactly what I've written as well. I understand how the program works to achieve that goal.
> they are constantly asked to write a short piece of code and then run it to confirm you are still in sync with the tutorial.
When I first started learning Rust, I opened the Book and Ray Tracing In One Weekend side by side, and implemented an interactive multithreaded path tracer. :)
Sometimes I feel bad about how impressive that sounds when in reality I'm a total ADHD mess. But I guess at least I know what I'm doing.
BTW: Are you hiring remote? :)