2 ms·
I’m looking for tips around this too, but a couple things that I have noticed helping me are: - Extend your competence at least one layer below where you are w
by caffeine 5y ago
I’m looking for tips around this too, but a couple things that I have noticed helping me are:
- Extend your competence at least one layer below where you are working. So if you’re using Java, read through the code for the SDK data structures, understand the JVM, etc. If you’re using Rust, learn the Nomicon. If you’re using an asynchronous networking framework, read the Linux man pages for epoll.
- Separate speed runs and quality coding into different passes. Write it once as fast as you can with no concern for quality, error handling, maintainability, etc. Just get the functionality right. Then basically just delete that and write it again using what you’ve learned, and doing it “properly”. That is faster “batch mode” than trying to write it perfectly all at once.