AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
YAGNI is a core element of agile programming. If it is code that may be restored, make a ticket and reference the commit hash for the code delete. The same is true for commenting-out code if a block of commented code is going into a release, it shouldn't exist. (You can, and must, design APIs, for example, to permit future use cases, but that's a different issue.) If you put code in for a future use case, I will question it in a code review. This is coding for imaginary future use cases, and inevitably the code will become dead code or need rewriting because the future use case always turns out to work slightly differently from how you imagined it. Don't write code that you think you might need in future, but don't need yet. With that in mind, feel free to disagree with these points, and we can discuss and debate them in the comments. In general, we programmers are an opinionated lot, and strong opinions are often a sign of great passion. eBook: An introduction to programming with Bash.Try for free: Red Hat Learning Subscription.
0 Comments
Read More
Leave a Reply. |