Could you convince them that writing documentation is a nice way to procrastinate and makes the implementation part easier? I swear I solved an implementation problem (which caused no small amount of headscratching) recently just by carefully specifying the function to be implemented. By doing that I ended up describing the cases correctly which then made the implementation trivial. It was a recursive function so a botched case analysis easily leads to incomprehensible behavior.
source control, etc. as fluff, nice to have, non-productive, etc.
¡Dios mío! I'm glad that I've used source control for very low importance projects so that I can use it without any real effort when it's needed.
The crappy part of programming really is that there are so many useful tools that you have to bring together and tinker with to make them good. Like to write good unit tests you presumably ought to be specifying your functionality in good enough detail, your testing framework presumably has a few knobs to be set, then you have to make testing and documentation work with your build system, for Git you need a .gitignore file and so on, all this upfront work and busy work that makes it all easy to skirt.
Teenage Mutant Ninja Turtles Intro Animated with Mario Paint by Mike Matei
A Most Classic /r/StevenUniverse post
Steven Universe and its gaming influences
hey guys can you make my tweets go viral? I can't afford the Moldovan bot armies
Wikipedians push themselves beyond the bounds of logic
More Than Just a Game: The Mental Techniques of Advanced Melee Players
I Am the Very Model of a New York Times Contrarian
This Galentine's Day, a New Champion Has Emerged
"Seniors: you want hard candy, right? I don't know much about seniors but it's my understanding that you sure do love hard candies! Hah!"
You Reposted In The Wrong Trousers
Moonside wrote
Reply to I'm doing a big programming group project with four other undergrads by twovests
Could you convince them that writing documentation is a nice way to procrastinate and makes the implementation part easier? I swear I solved an implementation problem (which caused no small amount of headscratching) recently just by carefully specifying the function to be implemented. By doing that I ended up describing the cases correctly which then made the implementation trivial. It was a recursive function so a botched case analysis easily leads to incomprehensible behavior.
¡Dios mío! I'm glad that I've used source control for very low importance projects so that I can use it without any real effort when it's needed.
The crappy part of programming really is that there are so many useful tools that you have to bring together and tinker with to make them good. Like to write good unit tests you presumably ought to be specifying your functionality in good enough detail, your testing framework presumably has a few knobs to be set, then you have to make testing and documentation work with your build system, for Git you need a .gitignore file and so on, all this upfront work and busy work that makes it all easy to skirt.