So this is what I want to spend some time discussing with you this morning.
Interface segregation principle python how to#
This book is a little dated, the languages that it talks about are the ones in use more than a decade ago. But, perhaps there are some aspects of the SOLID principles that may give us a clue about how to talk about a well designed Go programs.
Interface segregation principle python software#
In it he described five principles of reusable software design, which he called the SOLID principles, after the first letters in their names. In 2002 Robert Martin published his book, Agile Software Development, Principles, Patterns, and Practices. Wouldn’t it be great if there were some ways to describe the properties of good design, not just bad design, and to be able to do so in objective terms? SOLID Is it just exhausting to use the code? When you look at it, can you even tell what this code is trying to do?Īre these positive sounding words? Would you be pleased to see these words used in a review of your code?īut this is an improvement, now we can say things like “I don’t like this because it’s too hard to modify”, or “I don’t like this because i cannot tell what the code is trying to do”, but what about leading with the positive? Is there code for the sake of having code, are things over-engineered? Is the code hard to refactor? Is it one keystroke away from an import loop? Is the code fragile? Does the slightest change ripple through the code base causing untold havoc? Is the code rigid? Does it have a straight jacket of overbearing types and parameters, that making modification difficult? What are some of the properties of bad code that you might pick up on in code review? Now it’s fine to say “that code is ugly” or ”wow that source code is beautiful”, just as you might say “this painting is beautiful” or “this room is beautiful” but these are subjective terms, and I’m looking for objective ways to talk about the properties of good or bad code. If code review is there to catch bad code, then how do you know if the code you’re reviewing is good, or bad? Who here does code review as part of their job?. How many Go programmers are there in the world? Think of a number and hold it in your head, we’ll come back to it at the end of this talk. How many Go programmers are there in the world? This post has been translated to Russian by Artem Zinoviev. This post has been translated into Simplified Chinese by Haohao Tian. This post is based on the text of my GolangUK keynote delivered on the 18th of August 2016.Ī recording of the talk is available on YouTube.
0 kommentar(er)
