This post is not advice, it's what's working for me. 

It's easy to pick up bad habits and hard to create good ones. Writing down what's working for me hel...

Primal Skill

George

Privacy

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

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.

Good software development habits

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.

Copy-paste is OK once… Never heard of this line and it has a deep meaning tbh.

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.

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!

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.