6 ms·
I don't use the "I owe a thing" method. I put the closing bracket/quote in when put the opening one in, and then hop left a space and fill in the content. I fin
by marcus_holmes 9y ago
I don't use the "I owe a thing" method. I put the closing bracket/quote in when put the opening one in, and then hop left a space and fill in the content. I find it too confusing otherwise. For exactly the reason the author describes.
- kazinator 9y agoIt must be that neither of you use an editor which knows how to match parentheses. Then the choice of habit is largely moot. Also, that little leftward jump can be automated by the editor, which is useful if you want it more often than not.
- spatley 9y agoAgreed. And for that matter there is a tremendous amount of context a programmer must keep in her head. If your bracket stack is top of mind I fear for your users. I am a pedant at heart and have had many in depth conversations about semantic naming, structure and idiomatic code. But leave bracket matching to the IDE.
- tmcw 9y agoAuthor here. I've used plenty of editors that 'know' how to manage parenthesis. And editors that did even more than that, like auto-completing snippets and moving around the cursor. It's all great, and I too think paredit is great! But these are all techniques for improving the "writing new code" experience, which is the minority of work that anyone does. Nobody writes perfect code the first time. And these conveniences for writing new code don't help much with the majority of my time, which is spent editing, deleting, and refactoring code - and understanding at first glance the structure of a program from its punctuation. So, sure - editors can do more and I'm hopeful about them. But I don't think that 'automatic bracket insertion' actually fixes this problem. I think it makes the task of writing code seem easier but doesn't help at all with the hard parts.
- deleted 9y ago[deleted]