CODING
I write code with vi, compile and run on the command line, debug with gdb, and so on. I avoid auto-indent, syntax highlighting, auto-completion. It’s not that I want to code like a caveman – I’ll use C or Java or Python instead of assembly language; I may match parenthesis or brackets with the “%” key in vi – but I want to stay as engaged with the process as I can, across multiple levels.
WRITING
I try to disable auto-correct, syntax highlighting, and grammar suggestions. I usually leave spell-checking enabled, because I do make a lot of typos :) (and proofreading is not something I particularly enjoy). If I misspell something though, I’ll try to correct the spelling myself. If I can’t figure it out, I’ll go to dictionary.com
MUSIC COMPOSITION
I use MuseScore to let me enter music, note by note, into a score. I like this because (a) it lets me turn the score into a PDF; and (b) it will render an audio file from the score, so I can hear what it sounds like. I use this as part of the composition process itself, but not until later. Usually, I start by playing notes on my violin or piano, writing them down on paper (ideally with a dip pen!), playing it back myself, listening, changing, adding. I’ll do this for 1 or 2 voices, then I’ll enter it into MuseScore, so I can hear multiple voices. While listening to it, I’ll continue the process, adding more voices, either playing them myself, or, at some point, typing them in directly (usually once I have a good feel for what the whole piece should sound like). I definitely don’t want anything in the process that suggests notes or rhythms, fills in details for me, etc. The tool is a great help, but I use it for conveying what is inside me into a form where others can hear it or play it.