True, I don't usually use Getters and Setters in Go, as you can always do struct.title = x, which is shorter and clean. But it makes sense in interfaces. And yes, it should be unexported (edited)
Hello, when it comes to DIP and: "In simpler terms, DIP advises that your code should depend on interfaces or abstract classes rather than concrete classes or functions."
This is not true, actually. When high- and low-level modules are mentioned they refer to business logic (rules) and infrastructure (e.g. database, web, external interfaces), not just language specific interfaces/abstract classes nor specific class implementations/functions.
If the code syntax highlighting was there it will be more better to read code
Exactly, the biggest limitation of Substack for me. That’s why I always share a repo as well.
Don do `SetTitle`.
title is already exported, so no need to have a setter method on it.
Instead make `title` unexported, then you can provide a setter.
True, I don't usually use Getters and Setters in Go, as you can always do struct.title = x, which is shorter and clean. But it makes sense in interfaces. And yes, it should be unexported (edited)
Hello, when it comes to DIP and: "In simpler terms, DIP advises that your code should depend on interfaces or abstract classes rather than concrete classes or functions."
This is not true, actually. When high- and low-level modules are mentioned they refer to business logic (rules) and infrastructure (e.g. database, web, external interfaces), not just language specific interfaces/abstract classes nor specific class implementations/functions.