📨 new blogpost! "why i like small commits"
Signed-off-by: SindreKjelsrud <sindre@kjelsrud.dev>
This commit is contained in:
		
							parent
							
								
									61e58a5731
								
							
						
					
					
						commit
						cef8ca41ff
					
				
					 1 changed files with 13 additions and 0 deletions
				
			
		
							
								
								
									
										13
									
								
								src/content/blog/why-i-like-small-commits.md
									
										
									
									
									
										Normal file
									
								
							
							
						
						
									
										13
									
								
								src/content/blog/why-i-like-small-commits.md
									
										
									
									
									
										Normal file
									
								
							|  | @ -0,0 +1,13 @@ | ||||||
|  | --- | ||||||
|  | title: "why i like small commits" | ||||||
|  | pubDate: 'July 16 2024' | ||||||
|  | description: "" | ||||||
|  | draft: false | ||||||
|  | --- | ||||||
|  | I like small commits. Why? Well first of all they make it easier to take over code from others, since it shows a coherent thought by simply having code split into smaller fragments. | ||||||
|  | 
 | ||||||
|  | A benefit of this is that you continuosly scope the task at hand, which in return gives you a better overview of the project. You'll minimize the time the codebase is in a non-functioning state, as well as not getting distracted by *just solving one more thing*. | ||||||
|  | 
 | ||||||
|  | A bonus for having small commits is that the commit message will be small and easily to describe. Additionally, I like using [**Gitmojis**](https://gitmoji.dev) as a way to identify the purpose of the commit. | ||||||
|  | 
 | ||||||
|  | This is why I like small commits. | ||||||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue