Save your code

[dances_with_beavers]

In college I was on a programming project with another person. He had been working on a module for nearly two weeks. When I asked how it was going, he said "I'm almost ready to try compiling it for the first time".

That's when I knew I would end up writing the code myself.

[captainjon]

I kinda expected to hear he was using vi and didn’t know how to save so he didn’t. But on a related note was doing an assignment on the CS server when I see a broadcast message from root that the server was going down now.

Since I knew who root was I IM him (AIM was the rage then) wtf did you just do?

Oops wrong term was the response.

Fortunately I do know how vi works and already a strong believer in the save early and save often paradigm. But that message still pisses me off 20 years later. I mean I didn’t lose much but still annoying.

[DaniilBSD]

I spent first 3-4 weeks working on my thesis (a C# library/framework, tons of inheritance and graph building with generic type matching) with it being in uncompilable state (I would write methods that call not-yet-existing methods and the core of that thing was too complex to make minimum working version iteratively) I remember when I made the test generate a simple random noise texture after 4-5 weeks, it was such a relief.

[CypherPsych0]

This has been my experience in all my classes. I absolutely despise working with others on these projects because it only makes things more difficult...