My teachers use the number of commit you do as measure for the quality of your work.

I've the least number of commits this week since I spent most of the week doing encriptions algorthims instead of UIs and unit test as the rest of my team.

But, by their logic, I'm the worst of the group. It's simply stupid.

write a script that will commit something every 2 houers?

@heyheni Or I use NetBeans to generate the JavaDoc and do a commit for each one of the undocummented methods. Should work too!

Touch tmpFile
Git add .
Git commit -m 'adds tmpfile'
Rm tmpFile
Git add .
Git commit -m 'removes tmpfile'

... Put this in a for loop and you are good to go 😂

What a crappy metric.

When you're the boss, use something else.

It's a lazy way of evaluating work. That being said, there's a difference between source code quality and codebase quality. Forcing yourself to write unit tests and commit often (and always) will create muscle memory, and will improve the quality of your codebase. Having granular commits helps other people to understand your code, facilitates remote collaboration and makes it easier to do maintenance later.

School projects probably won't be maintained, but it's rare to see professors making students practice this kind of stuff.

Later in life when you work for a big company with thousands of files and millions of lines of code, you WILL hate the guy that does one commit "add stuff", trust me.

Make commits that only contain comments, grammar corrections and tabs/line breaks. Each file, one commit.

Quality over quantity ANY day!

@thenogs I’m not against unit testing or granular commits. Granular commits do really help, specially if you for some reason have to revert do to some issue. What I’m against is that they use the number of commits and the number of test coverage as 2 of the main evaluation points, instead of (for example) good OOP and OO design practices, and not having those can in fact lower your grade.

@thenogs
In my course (Licenciatura em Engenharia Informática - Informatics Engineering in English - at ISEP) we have 4 weeks of Project each semester plus internship in the last semester. We even have meetings with the “client” (usually the teacher that is in charge of the project). They try to educate us the very best practices for the job market instead of only the theory as most Computer Engineering courses.