It can be any type of data – values, structured or serialized data, path to file to parse or a socket to connect – the main idea is to put the data at the interface call. Otherwise, you will lose the contract details and sooner or later you will be fooled.Īny interface also has to have a single entry point, that means you pass the whole amount of data that the interface requires at once, by passing it explicitly. you will be able to pass the data from hand to hand.
But you always should be able to interact clearly and fair, that means all interactions have to be visible and legitimate, i.e. They shouldn’t send your stuff after a week or two if you agreed on an immediate transaction. They shouldn’t take anything from your pocket when you turn away. That means, that they have to take exactly what they are asking you for and give you exactly what they promise. The contract between you and the other side should be explicit, rightful and without any notes in small text at the bottom of the page. Any of your interfaces, whether public or internal, API or object interface, a class method or module facade – they have to cooperate fair. Let me be honest, I really dislike any implicitness in interfaces.
And don’t forget about CLI arguments! Am I missing something? env and, of course, container environment. There are many concurrent approaches to organize application configuration nowadays.Ĭlassic. I welcome new readers and will be happy to discuss what I'm writing about
0 kommentar(er)
