Talk:Taxicab numbers: Difference between revisions

I certainly don't want to start a tidying up war, when changes (drastic or otherwise) are made to another person's wording, it can be offending, especially if it appears to be less accurate or effective (which is ''very'' subjective, of course, it may just boil down to ego ... my wording is better than your wording, so I'll make a change to your wording ... Ugh). &nbsp; I certainly don't agree with most of the "tidying up" being done to various Rosetta Code task requirements that I've entered, after all, most of us have an idea what is tidy or not, especially if we're entering the task definitions, requirements, links, and other notes and comments. &nbsp; Certainly, I believe that I've some better ideas for other Rosetta Code tasks (wording), but changing someone else's wording, format, links, or whatever could be interpreted as not respecting their opinions or expertise. &nbsp; I discount spelling or typo errors, or some other such finger bloopers. &nbsp; Keeping the same format and adding better (or more) whitespace, more links, more auxiliary definitions (aliases and alternate definitions and such), or other notes/exceptions are welcome. &nbsp; Additions are always welcome. &nbsp; Making it worse in the reading and/or looking-at is a step in the wrong direction. &nbsp; I generally prefer more whitespace, shorter sentences (no compound sentences in definitions if possible), and not a string of many sentences on one line (or long lines in general), especially for definitions, links, and requirements. &nbsp; The intent is to make the wording more readable and perusable. &nbsp; After all, this will be read by everyone, not like specific comments in the various language entries (which are skipped over by most people not interested in most other languages). &nbsp; <strike>Added</strike> Adding a blank line here and there makes the first impression of the task easier to eyeball and to find out what is required. &nbsp; What would be more appreciated if people (who make unannounced changes, and sometimes, unappreciated or unwarranted) would ask first, saying something like, "would you mind reformatting or rewording this and that? &nbsp; Here's what I had in mind: ... &nbsp; and possibly followed (hopefully) with some justification or other thoughts in explaining your thinking. &nbsp; This would make the changing and tidying up much more collaborative and instill a genteel and polite relationship when (maybe drastic) changes are made, even if only "tidying up". &nbsp; In another matter, calling an attempt to flag a task as needing review because a requirement had changed (not knowing the proper template) as "lame", falls short of being polite and respectful. &nbsp; Just replying with the proper template to use (or implementing it yourself) would be much better than just removing it with an offensive comment. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 11:24, 26 March 2014 (UTC)