Talk:Range modifications: Difference between revisions

Line 18:
On algorithm restriction: RC tasks must be succinct. I can't show huge extensive input but try and restrict this algorithm so it may work with such. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 04:17, 24 October 2020 (UTC)
 
:These formulations are charmingly ProcrusteanProcustean and intemperate:
had to look those up. You should check the spelling of procustean - did you mean procrustean with another r? Intemperate isn't usually applied to someone's work, and both words have conflicting meanings wrt control. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 05:11, 24 October 2020 (UTC)
 
Line 27:
::(There is a risk here of appearing more preoccupied with control than with Rosetta quality and value).
:: Set a new problem (this one seems mainly a rehash of two existing problems) and let everyone else stretch their own limbs, and enjoy and learn from the variety of responses. [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 06:34, 24 October 2020 (UTC)
 
:Your not stating that you don't understand the requested format. You want to ignore it. If the task asks for JSON, don't produce XML. If it states the sequence format should be produced as part of the task and a solution instead gives something else with a glib comment that the requested format could be produced with a slight change then why not complete the task?
 
:Coding does tend to need precision. Finding wriggle-room often takes experience and interpersonal skills, and might not materialise. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 07:32, 24 October 2020 (UTC)
Anonymous user