|
|
|
|
|
|
by saagarjha
2262 days ago
|
|
|
> The only time you need to write malleable software is when the problem needs a malleable solution. The point is that it’s very difficult to account for this beforehand, especially as the author of the software. (“What do you mean we should make this an option? 5 works for me, and I’ll change it in the code if it doesn’t!”) When designing software, it’s always nice to give a thought to “if I were using this and I wanted to change it, how would I do so?” and seeing if there’s anything you can do to improve that. |
|
|