{
  "id": 97754,
  "title": "Why no use of utility scripts? ",
  "url": "/competitions/generative-dog-images/discussion/97754",
  "author_name": "",
  "post_date": "2019-06-28T18:16:06.778219Z",
  "votes": 1,
  "comment_count": 3,
  "views": 0,
  "content": "<p>This page <a href=\"https://www.kaggle.com/c/generative-dog-images/overview/kernels-requirements\">https://www.kaggle.com/c/generative-dog-images/overview/kernels-requirements</a> says \n\"No use of other kernels (or utility scripts) as inputs into your submission kernel\".</p>\n\n<p>Why? ((( </p>\n\n<p>Trying to include all code in one huge script is a pain and leads to very ugly code and bad programming practices. Moreover it makes much much harder to maintain correspondence between your local code and kernel submission, because locally you won't write all your code in one huge ugly script (I hope :). I was so happy when utility scripts were introduced..</p>",
  "messages": [
    {
      "id": "563836",
      "postDate": "06/28/2019 18:16:06",
      "content": "<p>This page <a href=\"https://www.kaggle.com/c/generative-dog-images/overview/kernels-requirements\">https://www.kaggle.com/c/generative-dog-images/overview/kernels-requirements</a> says \n\"No use of other kernels (or utility scripts) as inputs into your submission kernel\".</p>\n\n<p>Why? ((( </p>\n\n<p>Trying to include all code in one huge script is a pain and leads to very ugly code and bad programming practices. Moreover it makes much much harder to maintain correspondence between your local code and kernel submission, because locally you won't write all your code in one huge ugly script (I hope :). I was so happy when utility scripts were introduced..</p>",
      "rawMarkdown": "This page https://www.kaggle.com/c/generative-dog-images/overview/kernels-requirements says \n\"No use of other kernels (or utility scripts) as inputs into your submission kernel\".\n\nWhy? ((( \n\nTrying to include all code in one huge script is a pain and leads to very ugly code and bad programming practices. Moreover it makes much much harder to maintain correspondence between your local code and kernel submission, because locally you won't write all your code in one huge ugly script (I hope :). I was so happy when utility scripts were introduced..",
      "votes": null
    },
    {
      "id": "563837",
      "postDate": "06/28/2019 18:18:55",
      "content": "<p>Sorry - we had to turn quite a few things off to prevent cheating. Utility scripts is one of those things that could introduce loopholes. </p>",
      "rawMarkdown": "Sorry - we had to turn quite a few things off to prevent cheating. Utility scripts is one of those things that could introduce loopholes.",
      "votes": null
    },
    {
      "id": "563921",
      "postDate": "06/28/2019 19:28:00",
      "content": "<p>Fortunately there's \"hide input/ouput\" and collapse feature on Kaggle's kernel!</p>",
      "rawMarkdown": "Fortunately there's \"hide input/ouput\" and collapse feature on Kaggle's kernel!",
      "votes": null
    },
    {
      "id": "565360",
      "postDate": "06/30/2019 20:15:14",
      "content": "<p>Well, it's a pity but I can understand the reason, of course prevention of cheating is of primary importance. Thank you for response.</p>",
      "rawMarkdown": "Well, it's a pity but I can understand the reason, of course prevention of cheating is of primary importance. Thank you for response.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 563837,
      "author_name": "wendykan",
      "author_url": "",
      "post_date": "06/28/2019 18:18:55",
      "content": "<p>Sorry - we had to turn quite a few things off to prevent cheating. Utility scripts is one of those things that could introduce loopholes. </p>",
      "votes": null,
      "replies": [
        {
          "id": 565360,
          "author_name": "antklen",
          "author_url": "",
          "post_date": "06/30/2019 20:15:14",
          "content": "<p>Well, it's a pity but I can understand the reason, of course prevention of cheating is of primary importance. Thank you for response.</p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 563921,
      "author_name": "ilhamfp31",
      "author_url": "",
      "post_date": "06/28/2019 19:28:00",
      "content": "<p>Fortunately there's \"hide input/ouput\" and collapse feature on Kaggle's kernel!</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "563836": "This page https://www.kaggle.com/c/generative-dog-images/overview/kernels-requirements says \n\"No use of other kernels (or utility scripts) as inputs into your submission kernel\".\n\nWhy? ((( \n\nTrying to include all code in one huge script is a pain and leads to very ugly code and bad programming practices. Moreover it makes much much harder to maintain correspondence between your local code and kernel submission, because locally you won't write all your code in one huge ugly script (I hope :). I was so happy when utility scripts were introduced..",
    "563837": "Sorry - we had to turn quite a few things off to prevent cheating. Utility scripts is one of those things that could introduce loopholes.",
    "563921": "Fortunately there's \"hide input/ouput\" and collapse feature on Kaggle's kernel!",
    "565360": "Well, it's a pity but I can understand the reason, of course prevention of cheating is of primary importance. Thank you for response."
  },
  "source": "meta"
}