Also, keeping process/logic independent of specific input/output type is useful beyond just the ability to Unit Test. It's as old as the COBOL days of Jackson Diagrams, and its the underpinning of multiple "layers". The same pattern is useful at the lower-level of a specific program or class.
Definitely, I think software engineers have developed many technic to keep process/logic independent.
MVC, DI, layered architectures(Maybe OSI reference model is the most famous) and so on.
It's not special things, but it's important in any era.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Also, keeping process/logic independent of specific input/output type is useful beyond just the ability to Unit Test. It's as old as the COBOL days of Jackson Diagrams, and its the underpinning of multiple "layers". The same pattern is useful at the lower-level of a specific program or class.
Definitely, I think software engineers have developed many technic to keep process/logic independent.
MVC, DI, layered architectures(Maybe OSI reference model is the most famous) and so on.
It's not special things, but it's important in any era.