GithubHelp home page GithubHelp logo

Submitting incrementally about 2122-s2 HOT 5 CLOSED

nus-cs2030 avatar nus-cs2030 commented on August 11, 2024
Submitting incrementally

from 2122-s2.

Comments (5)

eesung00 avatar eesung00 commented on August 11, 2024 2

For me I submit the code only after I code for all level as I didn't look at the announcement clearly. I have some time wasting experience after I did this as I didn't pass all test cases as I expected, and accidentally change my code to fail more test cases. Hence, I guess by submiting your work incrementally will allow you to make sure your code so far is correct and avoid changing it for the next few level.

from 2122-s2.

yongchein-o avatar yongchein-o commented on August 11, 2024

Really depends on personal preference. Usually its good to commit every so often and especially before you make any significant changes to your code. Any case, submitting allows you to keep a history of your work.

There's always a possibility that you:

  • accidentally delete your file: in which case there is no recycling bin in Ubuntu
  • accidentally delete your code in vim and reflexively exit using :wq

On that note it's good to set up the backup folder as well. (refer to the .vimrc file)

from 2122-s2.

tanweiming00 avatar tanweiming00 commented on August 11, 2024

I submit incrementally whenever I am confident that I passed that particular level.

from 2122-s2.

heeeyi avatar heeeyi commented on August 11, 2024

Personally I prefer submitting the code only after I feel I passed ALL the level requirements...In that sense, when we find that the final score is not A we know there is some style issues in the code, and thus I can focus on correcting for the styles. Anyway if you pass each level but later edit the code, you are prone to make mistakes in styles

from 2122-s2.

yangyee-hub avatar yangyee-hub commented on August 11, 2024

I feel you should test your code incrementally in the vim first before submitting as it takes shorter time to test in jshell compared to the codecrunch. Codecurnch is normally used for testing hidden test cases.

from 2122-s2.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.