On 10/12/2022 22:00, Uwe Brauer wrote: >> The great thing was I >> could save (to Git) snippets (hunks) of my code out of sequence and have >> instant replay of those bits of quick trial code that would recreate >> figures and tables that became useful in retrospect. Sort of a 'commit a >> minute' speed. > Never heard of this > > That is a literal, 'I would make a simple commit about once every one or two minutes' while doing some Matlab coding development while investigating some broader problem or issue that I was modelling.
So every time I updated a graph / chart / figure I'd do a quick commit so if it turned out that the graph, three revisions ago, was useful (in retrospect) I could leap back to it. Theses problems are especially common in engineering trade-offs where resources are limited, so lots of resource trade off curves are developed, most of which end up useless, but one or two, if you can remember where they are, are very useful (hence "commit early, commit often" to misquote..) Example, a local/personal issue at the moment is: when does condensation happen on the windows because we've turned the heating down, and the outside temperature has dropped, and we aren't sure if relative humidity, absolute humidity, perceived humidity are the best way of representing the curves that show just when and where the condensation will happen, or where it came from. Lots of opinions on the inter-web, but lacking in clear modelling. A fun project, but no idea which way [which simple graph] is best for explaining to spouse why (a bit more exactly) dark cold corners are now getting damp and mouldy. It's a 'no right answer' problem [1], so record lots of potential answers and steps toward them.. If the student is in a 'hack and hope' mode, then they will get very confused if [when] they don't have a bread crumb trail to get back to some point of halfway success to branch off in a different direction, cherry picking little bits that are useful from the trail of failures.. Git's ability to "commit early, commit often" is the saviour here. It's fast, requires no permissions, minimal storage, doesn't need to be shown to anyone. Git let's you tidy up the working and make it look pristine before submission. What's not to like. It's worth having a look at Git's 'SubmittingPatches' [2] doc for some of the "Cheats" that the Git team use to look good ;-) Aside: for appealing to students better nature for using "version recovery" see [3] ! Philip [1] https://en.wikipedia.org/wiki/Wicked_problem [2] https://github.com/git/git/blob/master/Documentation/SubmittingPatches [3] https://www.interviewbit.com/git-interview-questions -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/7ecb97c8-5f0a-43c0-6162-914a177adecd%40iee.email.
