Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack InternalOne of the methods that I commonly use in our codebase is misspelled (and it predated me).
This really irritates me not simply because it is mispelled but more importantly it makes me ALWAYS get the method name wrong the first time I type it (and then I have to remember "Oh, right, it should be mispelled to this...")
I'm making a few changes around the original method. Should I take the opportunity to just rename the freaking method?
One of the methods that I commonly use in our codebase is misspelled (and it predated me).
This really irritates me not simply because it is mispelled but more importantly it makes me ALWAYS get the method name wrong the first time I type it (and then I have to remember "Oh, right, it should be mispelled to this...")
I'm making a few changes around the original method. Should I take the opportunity to just rename the freaking method?
One of the methods that I commonly use in our codebase is misspelled (and it predated me).
This really irritates me not simply because it is mispelled but more importantly it makes me ALWAYS get the name wrong the first time I type it (and then I have to remember "Oh, right, it should be mispelled to this...")
I'm making a few changes around the original method. Should I take the opportunity to just rename the freaking method?
One of the methods that I commonly use in our codebase is misspelled (and it predated me).
This really irritates me not simply because it is mispelled but more importantly it makes me ALWAYS get the method name wrong the first time I type it (and then I have to remember "Oh, right, it should be mispelled to this...")
I'm making a few changes around the original method. Should Should I take the opportunity to just rename the freaking method?
One of the methods that I commonly use in our codebase is misspelled (and it predated me).
This really irritates me not simply because it is mispelled but more importantly it makes me ALWAYS get the method name wrong the first time I type it (and then I have to remember "Oh, right, it should be mispelled to this...")
I'm making a few changes around the original method. Should I take the opportunity to just rename the freaking method?
One of the methods that I commonly use in our codebase is misspelled (and it predated me).
This really irritates me not simply because it is mispelled but more importantly it makes me ALWAYS get the method name wrong the first time I type it (and then I have to remember "Oh, right, it should be mispelled to this...")
I'm making a few changes around the original method. Should I take the opportunity to just rename the freaking method?
One of the methods that I commonly use in our codebase is mispelledmisspelled (and it predated me).
This really irritates me not simply because it is mispelled but more importantly it makes me ALWAYS get the method name wrong the first time I type it (and then I have to remember "Oh, right, it should be mispelled to this...")
I'm making a few changes around the original method. Should I take the opportunity to just rename the freaking method?
One of the methods that I commonly use in our codebase is mispelled (and it predated me).
This really irritates me not simply because it is mispelled but more importantly it makes me ALWAYS get the method name wrong the first time I type it (and then I have to remember "Oh, right, it should be mispelled to this...")
I'm making a few changes around the original method. Should I take the opportunity to just rename the freaking method?
One of the methods that I commonly use in our codebase is misspelled (and it predated me).
This really irritates me not simply because it is mispelled but more importantly it makes me ALWAYS get the method name wrong the first time I type it (and then I have to remember "Oh, right, it should be mispelled to this...")
I'm making a few changes around the original method. Should I take the opportunity to just rename the freaking method?
