My favorite notebook is the JetPens Kanso Noto. They have 160 sheets (320 pages) of Tomoe River paper with a 5mm dot grid. Tomoe River paper is a premium fountain pen friendly paper that should solve your feathering problems.
https://www.jetpens.com/JetPens-Tomoe-River-52-gsm-Kanso-Noto-Notebook-A5-Dot-Grid-Black/pd/29704
JetPens offers free shipping in the US for order of $35 or more. I don’t know what options are available outside of the US.
The notebook is currently out of stock. I expect more to be back soon. Tomoe River paper was sold from one paper company to another. I think JetPens just cleared out their stock with paper from the original company and I anticipate they’ll bring the notebook back soon with paper from the new company (Sanzen). In the past, the notebooks sold for $19.50, which is a great price for a premium paper notebook (seriously, I think only the Nanami Seven Seas notebooks have a better price per page for premium paper) . However, to keep the price low, the notebook doesn’t have bells and whistles like an elastic closure or page marker ribbons.
I’m a hobbyist, I don’t use common lisp professionally, but it has become my go-to tool for little personal projects and puzzles (like Project Euler or Advent of Code). The interactive development (mentioned in the article) is one of the primary reasons.
I find it so fun to build with. You can write functions and immediately test and interact with them in the repl, and then build on them from there. You can compile code at a granular level - for example you can recompile a function rather than the entire source file. This is helpful if some stuff is still being worked out and would produce compile time errors.
Occasionally I’ve gotten into a weird place because of the evolution of my code and incremental changes along the way while running a program. When I stop and completely reload a program, it behaves differently from what I previously experienced. It is something additional to keep in mind when interactively modifying a program.
The debugger experience with Emacs/Slime is the best I’ve experienced (professionally I’ve used various versions of Visual Studio, and as a hobbyist, various open source IDEs.)
The programs I have written are simple. Some day I would like to grok CLOS and the condition system.