![]() ![]() It’s more important to grasp the idea of clean code than to follow these rules blindly. For now, these topics, which we will get into here, are more like guidelines. Maybe when software architecture is as old as architecture itself is today, there will be rules and set-in-stone principles. ![]() So, the more time we spend making our code readable, the better.Īs Ryan McDermott insightfully points out, the craft of Software Engineering is just a bit over 50 years old. You will read other people’s code and read your own, beyond writing it. Another way of thinking about it is: You will never write more code than you will read. Not only that, you write clean code as a way of passing that way of thinking forward, which will facilitate the job of other developers who read your code. I believe the comic strip above sums it well: You write clean code mainly to understand yourself in the future.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2023
Categories |