- Don’t write code until you need it. This results in less code, which is directly correlated with ease of change.
- If you write lots of separated classes but then use them directly inside other classes, you’ve defeated the point. When you depend on something, pass it in instead of directly referencing, if possible.
- keep methods less than 5 lines, classes less than 100 lines.
Ask HN: How do you write code so it's easy to change?
11–20 of 78 posts
Re: Ask HN: How do you write code so it's easy to change?
#12high test coverage and functional purity as much as possible.
don't get trapped by being "too DRY"
Re: Ask HN: How do you write code so it's easy to change?
#13Start with the absolute most simplistic structure, or no structure. Starting from "Hello world" is OK! (ie. starting in a new programming language)
Keep in mind you can always start over, especially if you componentize your work!
As you prototype, or just design by drawing on whiteboard, learn your domain and gain ideas what would improve your initial lack of design.
Iterate and refine when cost effective to do so, not sooner. If still on whiteboard, you could benefit from implementing rapid no-code solutions before diving into any code at all!
Resist committing to structure, unless your experience and insights into the domain require it and you see clear benefits from doing so. Deconstruct structure you find bring unnecessary complexity, as well as build on structure when doing so clearly brings leverage.
Care for your code.
Re: Ask HN: How do you write code so it's easy to change?
#14I would suggest reading Head first design pattern, apart from design patterns the book also explains how 'change' is inevitable in software development and how to design the software extensible and modular
Re: Ask HN: How do you write code so it's easy to change?
#15Extensible doesn’t mean the code itself gets changed often. It would help to read up on SOLID [1] design principles and books on software development. Actually implementing SOLID would come by reading good code, getting mentored and from experience.
Re: Ask HN: How do you write code so it's easy to change?
#16I'd say write the least amount of code you can.
While you're adding a feature it's always tempting to go down the "what if" route and make some kind of crazy interface that is extensible and able to accept plugins and all that. The problem is you're likely making it extensible in ways that turn out to be useless down the road.
Just code the least amount you have to in order to achieve the current goal. That way down the road it's easy to delete what you did, or code up some changes to it. I personally think the worst thing you can do is write code that is all things to all possible future features.
Re: Ask HN: How do you write code so it's easy to change?
#17Write shallow code, code that is the simplest solution for the problem
If the word "architect" springs to mind then you are doing it wrong
Re: Ask HN: How do you write code so it's easy to change?
#18I used to focus on making my code easy go extend. I still enjoy that style in personal projects, but on large teams, I find it is better to make your code easy to delete.
Re: Ask HN: How do you write code so it's easy to change?
#19Make it easy to delete conceptually
It should be removable in a way that does not break other systems and it should be easy to identify when "it" ends and when something else begins
Re: Ask HN: How do you write code so it's easy to change?
#20Keep files small and use the file system to your advantage: it's much easier to organize information in a tree than in a string. Keep code for components together (e.g. no "controllers" folder). Write twice as much documentation as you think you need.