> have "too many" commits on something simple ... it looks "bad" to employers
Really??
I have frequently, in the line of my consulting work, advised my clients (those self-same employers) to worry when they stop seeing a healthy flow of commits from a developer. (Not necessarily to github, rather to whatever VCS they're using.) One friend - like myself an experience dev. - wired ctrl-S in his IDE to his VCS commit command!
Mistakes, meandering explorations and wandering up entirely wrong paths is all part of software development, and is precisely what your VCS is there to help you manage. The notion that some (potential) employer might consider using it to the hilt as a "bad" thing sounds profoundly worrying to me. Probably not someone I'd want to work for.
Really??
I have frequently, in the line of my consulting work, advised my clients (those self-same employers) to worry when they stop seeing a healthy flow of commits from a developer. (Not necessarily to github, rather to whatever VCS they're using.) One friend - like myself an experience dev. - wired ctrl-S in his IDE to his VCS commit command!
Mistakes, meandering explorations and wandering up entirely wrong paths is all part of software development, and is precisely what your VCS is there to help you manage. The notion that some (potential) employer might consider using it to the hilt as a "bad" thing sounds profoundly worrying to me. Probably not someone I'd want to work for.