# Ninety Days of Commits

DevFeed: [Ninety Days of Commits](<https://devfeed.tech/articles/ninety-days-of-commits-21034.md>)

Original publisher: [Read original article](<https://jakeyesbeck.com/2015/07/26/ninety-days-of-commits/>)

Published: 2015-07-26T12:00:00Z

Content type: opinion

Language: en

Sources: [Jake Yesbeck](<https://devfeed.tech/sources/jake-yesbeck.md>)

Topics: [Development](<https://devfeed.tech/topics/development.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [coding](<https://devfeed.tech/topics/coding.md>)

Tags: [developers](<https://devfeed.tech/tags/developers.md>), [development](<https://devfeed.tech/tags/development.md>), [github](<https://devfeed.tech/tags/github.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [side-project](<https://devfeed.tech/tags/side-project.md>)

## AI overview

The author reflects on ninety days of making daily commits to a public GitHub repository, averaging three to four substantial commits per day. They describe how daily software development improves focus, confidence, and familiarity with projects, while frequent iteration helps immature software gradually develop better structure.

## Source excerpt

It has been ninety days since I started the Year of Commits initiative. The criteria behind this challenge was to make a commit to a public Github repository every day. Technically, a commit like the following satisfies that criteria: However, if I allowed this commit to be my sole contribution for a day, I would be cheating no one except myself. In reality, I have been averaging 3 to 4 decent size commits a day. Spending around an hour or two total per night. Github is an awesome piece of software that tells a visual tale of when I am most productive: Over this quarter of a year, I have accrued some interesting learnings about developing open source software. 1. Writing software every day just feels good. Not missing a single day of writing software has made a significant improvement in my confidence and attitude. In the same way exercising daily makes your body feel more sturdy, developing software daily keeps my mind focused and clear. Like warming up a car before a drive, writing software every day makes it very easy for me to jump into a new project or build a new feature. I think most of my fellow software artisans have been in this situation: You go on vacation or maybe just a very relaxing weekend, then the next day at work or when you open that side project again, you end up spending a lot of time getting familiar with the software. Even if you just wrote it a few days ago, the break has made some tiny details less sharp. Writing software every single day helps eliminate this. 2. Immature software is expected While writing software, there are a total of 0 people that look at what they just wrote and say: "This software is already bad and I have only just written it". However, this statement can be more true than we would like. The potential in a new project is always the best part, right? Developers around the world usually jump at a change to do green field development. After all, with no legacy software around we can make what ever our heart desires. It c