--- title: "Good software development habits" url: https://daily.dev/posts/good-software-development-habits-afpsvblj1 source_url: https://zarar.dev/good-software-development-habits/ type: article source: "Community Picks" published: 2024-09-11T15:55:17.703Z updated: 2024-12-12T09:45:00.068Z tags: ["agile", "tdd"] reading_time: 5 upvotes: 260 comments: 13 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Good software development habits **[Community Picks](https://daily.dev/sources/community)** · 5 min read · 260 upvotes · 13 comments ## Summary Forming good software development habits can significantly enhance speed and maintain quality. Key practices include making small commits, continuous refactoring, prioritizing working software, creating new modules for disparate functions, and focusing on test-driven development (TDD) to anticipate edge cases. Avoid duplications, accept that designs evolve, and understand different types of technical debt. Lastly, ensure that testability is a priority to indicate good design. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@jsnelders** · 3 upvotes > Based on my own experience, I think all-in-all it's a good and well balanced list, and I have to agree with pretty much everything said. I might push back a little on the first point about commits, but only at a practical level where the needs and size of the organisation you work in can dictate the size of commits (philosophically I can't disagree though). > > I get the impression the author is someone with a bit of experience and has some hard learnt, real world lessons under their belt. **@anmolbaranwal** · 2 upvotes > Copy-paste is OK once... Never heard of this line and it has a deep meaning tbh. **@sprezzatura** · 2 upvotes > I want to believe. Been writing code since 1965. But I can’t help thinking that TDD is 3 months of writing tests and 1 month of writing code, versus 1 month of writing code and 2 months of debugging. **@henryooi0077** · 2 upvotes > Just done reading the article, > I feel as though the author has given a lot of thought into almost everything there is. It opened my eyes regarding, "think of the testing before the code". If the code is not testable, the code needs improvement. As well as always commit smaller. > > Minimalization is key here and a lot of businesses seem to think more is better. In the direction the world is moving currently, there is simply too much information given, so in my opinion, less is better. > > Overall great article! **@jamiecarl** · 2 upvotes > Pretty good list, although like others, I have issue with 7. In my opinion, it's never OK to copy-paste. If you have even one duplicate then it should be a function. But that's just me. ## Similar posts on daily.dev - [Don’t just attend KubeCon \+ CloudNativeCon, Merge Forward your experience\!](https://daily.dev/posts/don-t-just-attend-kubecon-cloudnativecon-merge-forward-your-experience--l0rpp73x8) · CNCF · 0 upvotes · 0 comments - [Announcing H2 2026 KCDs](https://daily.dev/posts/announcing-h2-2026-kcds-m96goajm1) · CNCF · 1 upvotes · 0 comments - [Two months of Open Community Groups](https://daily.dev/posts/two-months-of-open-community-groups-asf52zhbs) · CNCF · 0 upvotes · 0 comments - [CNCF Unveils Schedule for KubeCon \+ CloudNativeCon Europe 2026](https://daily.dev/posts/cncf-unveils-schedule-for-kubecon-cloudnativecon-europe-2026-ikhcoa5cb) · CNCF · 2 upvotes · 0 comments - [CNCF Debuts KubeCon \+ CloudNativeCon Japan 2026 Schedule](https://daily.dev/posts/cncf-debuts-kubecon-cloudnativecon-japan-2026-schedule-xp5pyudub) · CNCF · 1 upvotes · 0 comments --- Tags: [#agile](https://daily.dev/tags/agile), [#tdd](https://daily.dev/tags/tdd) [View this post on daily.dev](https://daily.dev/posts/good-software-development-habits-afpsvblj1)