No Return Value Driven Development
As a programmer, you most likely have written some functions which return a value, right? Do you know how to write code without any return value? Do you know what kind of design problem will come with the code which returns some value?
This topic will show you the value of no return value code via some real code sample. It will show you the benefit about such no return value design as well as something deep in the object oriented design.
If you're a programmer who wants to write better code, this is topic for you. Your development mindset might be stroke in this talk, please keep calm. :)
Outline/structure of the Session
Here is the outline:
- Library and Warehouse Demo
- Why we must return some value? How about the implementation with no return value code?
- Another example with common transaction code
- Every time when your code needs to return something, often there is a design problem within your code.
- Is no-return-value code style more like functional style?
You may recognise that this talk is referring to the "Tell, don't ask" OO principle. By the end of this talk, you will see a very fundamental idea of object oriented design. It actually has very little relationship to the functional programming thoughts as well as I understand, and I will give a shot on this in the talk.
Understand why "No return value" is important to a good design and OO code.