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.
IDE: Use IntelliJ Community Edition (or whatever Jetbrains IDE matches your project). Print out a keystrokes cheat sheet and tape it on your desk. Try to do stuff as a series of snippets, autocorrects, autocompletes and refactorings rather than pounding out the code (this is especially relevant in Java where it can save you like 90% keystrokes).
Example: don't start a new method by writing the new method. Start it by calling it somewhere with arguments, then alt-enter (auto-correct) to create the method, with the types and arguments already filled in.
Chair: get Herman Miller Aeron or Mirra (cheaper), second hand
Standing desk: I use cardboard boxes on a regular desk. I take sitting breaks when I'm thinking but not actively typing. Pomodoros also work (stand 20, sit 5 or 10). Don't use your phone when you sit.
- 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.