4 ms·
It seems Ariadne hasn't yet come across a code maintenance situation that she couldn't overcome by expenditure of keystrokes into a typewriter-like program. Th
by kazinator 4y ago
It seems Ariadne hasn't yet come across a code maintenance situation that she couldn't overcome by expenditure of keystrokes into a typewriter-like program.
There is an illusion that it is all you need because using such a thing you can certainly crank out volumes of brand new content. If you have a clear idea of what you're writing, maybe just backspacing over the odd typo is all you need to forge ahead. And you can easily make small fixes to existing content with Nano, Notepad and whatnot. The more you have to think to make those fixes and the smaller is the actual textual change, the less of an impediment is it to use a "nonprogrammer's editor". If it took you 180 minutes to figure out it, shortening the editing from 30 seconds to 5 seconds succumbs to Amdah'ls Law; the speedup is virtually nil.
There can be a range of editing needs in between these use cases, in the context of development.
From Ariadne's experience I don't have the sense that she's worked in a software organization in a team, working on big changes to a big, existing code base and such and under pressure. Moreover, even in such an environment, there are those who survive somehow with goofy non-programmers' editors. You know the types; they announce themselves with their tattle-tale trail of wrong formatting (e.g. tabs where there should be spaces, incorrect indentation, ^M carriage returns in Unix-formatted files ...) spurious blank lines, or else trailing newline at the end of the file, trailing whitespace in lines and such. The times when raw editing is really the bottleneck are rare; and in all the other times, Amdahl's is ever present. Someone who has somehow figured out what needs to be changed where (with no help from any code navigation features in their glorified typewriter) can just crank it out. If what should take 5 minutes takes 45, it's not a big deal in the big picture. The assiduous Turtle armed with Notepad will beat the Hare who aptly uses a programmer's editor, but is unable to settle down to work.
I can see how a developer could convince themselves that all they need is a glorified typewriter program for coding, and easily brush aside any evidence to the contrary. What you Get Done with that typewriter is your direct, personal experience, whereas how other people work is just anecdotes, not hard data.