Software Engineering is one engineering field where there is always more than one way to solve a problem. Now this can be a blessing or a curse depending on the situation.
There are so many instances I have seen where developers argue to nth degree which is the right way to solve a problem or write code. Should code be centralised or should be near to place where it is used? How do we make sure we dont miss updating the code if the code changes somewhere else in future? How do we make sure if someone else picks up the code and doesn't follow the convention?
It is like as if you are building an extension to your house and the builder will use complete different bricks and not check what colour of bricks were already there even though it is right there in front of his eyes.
So how do we solve the problem? How can we help the team to focus on the solution and not gold plate the solution?
This is where patterns and principles come in. People have solved problems, If you study patterns, you will find a solution. If you know principles like SOLID, DRY, KISS can be handy.
In the end the code should be readable, simple, performant, maintainable and testable.
Is that difficult to achieve?
There are so many instances I have seen where developers argue to nth degree which is the right way to solve a problem or write code. Should code be centralised or should be near to place where it is used? How do we make sure we dont miss updating the code if the code changes somewhere else in future? How do we make sure if someone else picks up the code and doesn't follow the convention?
It is like as if you are building an extension to your house and the builder will use complete different bricks and not check what colour of bricks were already there even though it is right there in front of his eyes.
So how do we solve the problem? How can we help the team to focus on the solution and not gold plate the solution?
This is where patterns and principles come in. People have solved problems, If you study patterns, you will find a solution. If you know principles like SOLID, DRY, KISS can be handy.
In the end the code should be readable, simple, performant, maintainable and testable.
Is that difficult to achieve?
Comments