In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n
Thanks for reading.<\/p>\n\n\n\n
Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
<\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\nFinally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\nhttps:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n![\"\"](\"https:\/\/i2.wp.com\/pm-powerconsulting.com\/wp-content\/uploads\/2019\/09\/Screenshot-2019-09-27-at-3.27.39-PM.png?fit=1024%2C616\")
<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
![\"\"](\"https:\/\/i1.wp.com\/pm-powerconsulting.com\/wp-content\/uploads\/2019\/09\/Screenshot-2019-09-27-at-3.25.54-PM.png?fit=1024%2C653\")
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n
Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\nCool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n
Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\nThose Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n
<\/p>\n\n\n\n
I attempted to emphasis<\/p>\n\n\n\n
In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n
Thanks for reading.<\/p>\n\n\n\n
Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n
Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n
<\/p>\n\n\n\n
I attempted to emphasis<\/p>\n\n\n\n
In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n
Thanks for reading.<\/p>\n\n\n\n
I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n
The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n
Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\nCool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n
Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\nThose Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n
<\/p>\n\n\n\n
I attempted to emphasis<\/p>\n\n\n\n
In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n
Thanks for reading.<\/p>\n\n\n\n
Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\nThe Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\nThe Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\nObservations<\/h3>\n\n\n\n
The Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\nObservations<\/h3>\n\n\n\n
The Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\nThe Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
I attempted to emphasis<\/p>\n\n\n\n
In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n
Thanks for reading.<\/p>\n\n\n\n
Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n
The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n
One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n
I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n
The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n
Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\nCool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n
Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\nThose Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n
<\/p>\n\n\n\n
I attempted to emphasis<\/p>\n\n\n\n
In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n
Thanks for reading.<\/p>\n\n\n\n
The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n
One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n
I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n
The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n
Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n
Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n
Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n
Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n
<\/p>\n\n\n\n
I attempted to emphasis<\/p>\n\n\n\n
In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n
Thanks for reading.<\/p>\n\n\n\n
The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n
Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n
The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n
One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n
I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n
The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n
Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\nCool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n
Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\nThose Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n
<\/p>\n\n\n\n
I attempted to emphasis<\/p>\n\n\n\n
In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n
Thanks for reading.<\/p>\n\n\n\n
Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The immediate benefits of translating the requirement into the executable specifications are:<\/p>\n\n\n\n Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The Allocator is the class that is expected to provide the required capability to the user. The immediate benefits of translating the requirement into the executable specifications are:<\/p>\n\n\n\n Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The Allocator is the class that is expected to provide the required capability to the user. The immediate benefits of translating the requirement into the executable specifications are:<\/p>\n\n\n\n Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\nThe First Test<\/h3>\n\n\n\n
Observations<\/h3>\n\n\n\n
The Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\nEvolving the design<\/h3>\n\n\n\n
The First Test<\/h3>\n\n\n\n
Observations<\/h3>\n\n\n\n
The Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n
\n\n\n\nEvolving the design<\/h3>\n\n\n\n
The First Test<\/h3>\n\n\n\n
Observations<\/h3>\n\n\n\n
The Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n
\n\n\n\nEvolving the design<\/h3>\n\n\n\n
The First Test<\/h3>\n\n\n\n
Observations<\/h3>\n\n\n\n
The Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n
\n\n\n\nEvolving the design<\/h3>\n\n\n\n
The First Test<\/h3>\n\n\n\n
Observations<\/h3>\n\n\n\n
The Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n
<\/p>\n\n\n\n
\n\n\n\nEvolving the design<\/h3>\n\n\n\n
The First Test<\/h3>\n\n\n\n
Observations<\/h3>\n\n\n\n
The Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n
<\/p>\n\n\n\n
\n\n\n\nEvolving the design<\/h3>\n\n\n\n
The First Test<\/h3>\n\n\n\n
Observations<\/h3>\n\n\n\n
The Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\nEvolving the design<\/h3>\n\n\n\n
The First Test<\/h3>\n\n\n\n
Observations<\/h3>\n\n\n\n
The Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
I attempted to emphasis<\/p>\n\n\n\n
In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n
Thanks for reading.<\/p>\n\n\n\n
The StubbedTaskRepository is the implementation of the TaskRepository.
<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/6c75c02c795add7a7cea83f798b39b21 \/]\n\n\n\n
The Allocator is the class that is expected to provide the required capability to the user.
<\/p>\n\n\n\n
The immediate benefits of translating the requirement into the executable specifications are:<\/p>\n\n\n\n
Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n
The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n
Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n
The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n
One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n
I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n
The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n
Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\nCool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n
Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\nThose Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n
<\/p>\n\n\n\n
I attempted to emphasis<\/p>\n\n\n\n
In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n
Thanks for reading.<\/p>\n\n\n\n
Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n
The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n
Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n
The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n
One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n
I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n
The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n
Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n
Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n
Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n
Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n
<\/p>\n\n\n\n
I attempted to emphasis<\/p>\n\n\n\n
In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n
Thanks for reading.<\/p>\n\n\n\n
I started by stubbing the external TaskRepository by carving out the two functional capabilities.<\/p>\n\n\n
\n[gist https:\/\/gist.github.com\/krsmanian1972\/dc23bd26ba0953e12aa1a034658f0396 \/]\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1f9c288a35e187ed47c931635eeed7b3 \/]\n\n\n\n
The StubbedTaskRepository is the implementation of the TaskRepository.
<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/6c75c02c795add7a7cea83f798b39b21 \/]\n\n\n\n
The Allocator is the class that is expected to provide the required capability to the user.
<\/p>\n\n\n\n
The immediate benefits of translating the requirement into the executable specifications are:<\/p>\n\n\n\n
Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n
The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n
Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n
The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n
One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n
I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n
The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n
Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n
Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n
Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n
Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n
<\/p>\n\n\n\n
I attempted to emphasis<\/p>\n\n\n\n
In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n
Thanks for reading.<\/p>\n\n\n\n
Later I wrote the companion fixture for the specification.
<\/p>\n\n\n\n
I started by stubbing the external TaskRepository by carving out the two functional capabilities.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/dc23bd26ba0953e12aa1a034658f0396 \/]\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1f9c288a35e187ed47c931635eeed7b3 \/]\n\n\n\n
The StubbedTaskRepository is the implementation of the TaskRepository.
<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/6c75c02c795add7a7cea83f798b39b21 \/]\n\n\n\n
The Allocator is the class that is expected to provide the required capability to the user.
<\/p>\n\n\n\n
The immediate benefits of translating the requirement into the executable specifications are:<\/p>\n\n\n\n
Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n
The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n
Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n
The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n
One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n
I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n
The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n
Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\nCool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n
Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\nThose Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n
<\/p>\n\n\n\n
I attempted to emphasis<\/p>\n\n\n\n
In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n
Thanks for reading.<\/p>\n\n\n\n
Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Later I wrote the companion fixture for the specification. I started by stubbing the external TaskRepository by carving out the two functional capabilities.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/dc23bd26ba0953e12aa1a034658f0396 \/]\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1f9c288a35e187ed47c931635eeed7b3 \/]\n\n\n\n The StubbedTaskRepository is the implementation of the TaskRepository. The Allocator is the class that is expected to provide the required capability to the user. The immediate benefits of translating the requirement into the executable specifications are:<\/p>\n\n\n\n Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Later I wrote the companion fixture for the specification. I started by stubbing the external TaskRepository by carving out the two functional capabilities.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/dc23bd26ba0953e12aa1a034658f0396 \/]\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1f9c288a35e187ed47c931635eeed7b3 \/]\n\n\n\n The StubbedTaskRepository is the implementation of the TaskRepository. The Allocator is the class that is expected to provide the required capability to the user. The immediate benefits of translating the requirement into the executable specifications are:<\/p>\n\n\n\n Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
I captured the context and requirement as an executable specification with Concordion.<\/p>\n\n\n\n Later I wrote the companion fixture for the specification. I started by stubbing the external TaskRepository by carving out the two functional capabilities.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/dc23bd26ba0953e12aa1a034658f0396 \/]\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1f9c288a35e187ed47c931635eeed7b3 \/]\n\n\n\n The StubbedTaskRepository is the implementation of the TaskRepository. The Allocator is the class that is expected to provide the required capability to the user. The immediate benefits of translating the requirement into the executable specifications are:<\/p>\n\n\n\n Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The requirement is that when a user requests for a task, we need to offer the task that is in an Assignable state to the user. We should never give the user the task in a hold state. Meaning we should help the user to overcome the constraint.<\/p>\n\n\n\n I captured the context and requirement as an executable specification with Concordion.<\/p>\n\n\n\n Later I wrote the companion fixture for the specification. I started by stubbing the external TaskRepository by carving out the two functional capabilities.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/dc23bd26ba0953e12aa1a034658f0396 \/]\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1f9c288a35e187ed47c931635eeed7b3 \/]\n\n\n\n The StubbedTaskRepository is the implementation of the TaskRepository. The Allocator is the class that is expected to provide the required capability to the user. The immediate benefits of translating the requirement into the executable specifications are:<\/p>\n\n\n\n Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\n In my next article I will show you how I further improvised the Allocator by adopting a Preferential Producer and Consumer strategy by leveraging the LinkedBlockingQueue.<\/p>\n\n\n\n Thanks for reading.<\/p>\n\n\n\n Raja Subramanian<\/a><\/p>\n","post_title":"Safe transformation of the design - Part I","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"safe-transformation-of-the-design-part-i","to_ping":"","pinged":"","post_modified":"2024-01-23 11:55:42","post_modified_gmt":"2024-01-23 11:55:42","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13412","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The requirement is that when a user requests for a task, we need to offer the task that is in an Assignable state to the user. We should never give the user the task in a hold state. Meaning we should help the user to overcome the constraint.<\/p>\n\n\n\n I captured the context and requirement as an executable specification with Concordion.<\/p>\n\n\n\n Later I wrote the companion fixture for the specification. I started by stubbing the external TaskRepository by carving out the two functional capabilities.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/dc23bd26ba0953e12aa1a034658f0396 \/]\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1f9c288a35e187ed47c931635eeed7b3 \/]\n\n\n\n The StubbedTaskRepository is the implementation of the TaskRepository. The Allocator is the class that is expected to provide the required capability to the user. The immediate benefits of translating the requirement into the executable specifications are:<\/p>\n\n\n\n Unit tests are my favourite to unravel the design.<\/p>\n\n\n\n The first step of my approach was maintaining a buffer to keep the preferred tasks \u2014 Assignable Tasks.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/7197ecd5661f273e7e99d32a055232e3 \/]\n\n\n\n Then I would make the code to pass the test with minimal design elements and tried my best to avoid over-engineering.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/1438c4db4a64086492e3b49af1592347 \/]\n\n\n\n The process of coding to the test created waves of ideas and memoirs to relish. Of course, it is a side-effect of coding to a test.<\/p>\n\n\n\n One of them is the hint of a bounded buffer problem that can be leveraged and the other is the memory of my childhood; when elders used to pamper me by giving the items I like from their plate. Now as a father; it is my turn to offer the items my daughter is fond of.<\/p>\n\n\n\n I proceeded to the next unit test to evolve the allocation logic.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/75cc8dd0e05a3e64727c3f6c69a41004 \/]\n\n\n\n The code-snippet that captures the allocation logic should:<\/p>\n\n\n\n Let me check if the refactored code meets the expectation of the Unit test.<\/p>\n\n\n\n Cool, Now it is time to revisit the fixture of the executable specification that I wrote before \u2014 The PreferredTasksFeature.java.<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/e45f04212c8153214949eed286c2bfbf \/]\n\n\n\n Let me execute the specification to see if the definition of done is really done.<\/p>\n\n\n\n Those Happy greens are indicating that our allocator is meeting the specification.<\/p>\n\n\n\n <\/p>\n\n\n\n I attempted to emphasis<\/p>\n\n\n\nIdentification of Nouns<\/strong><\/h3>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/6c75c02c795add7a7cea83f798b39b21 \/]\n\n\n\n
<\/p>\n\n\n\n
\n\n\n\nEvolving the design<\/h3>\n\n\n\n
The First Test<\/h3>\n\n\n\n
Observations<\/h3>\n\n\n\n
The Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n![\"\"](\"https:\/\/i2.wp.com\/pm-powerconsulting.com\/wp-content\/uploads\/2019\/09\/Screenshot-2019-09-27-at-3.09.22-PM.png?fit=1024%2C637\")
<\/figure>\n\n\n\nIdentification of Nouns<\/strong><\/h3>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/6c75c02c795add7a7cea83f798b39b21 \/]\n\n\n\n
<\/p>\n\n\n\n
\n\n\n\nEvolving the design<\/h3>\n\n\n\n
The First Test<\/h3>\n\n\n\n
Observations<\/h3>\n\n\n\n
The Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n<\/figure>\n\n\n\nIdentification of Nouns<\/strong><\/h3>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/6c75c02c795add7a7cea83f798b39b21 \/]\n\n\n\n
<\/p>\n\n\n\n
\n\n\n\nEvolving the design<\/h3>\n\n\n\n
The First Test<\/h3>\n\n\n\n
Observations<\/h3>\n\n\n\n
The Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\n<\/figure>\n\n\n\nIdentification of Nouns<\/strong><\/h3>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/6c75c02c795add7a7cea83f798b39b21 \/]\n\n\n\n
<\/p>\n\n\n\n
\n\n\n\nEvolving the design<\/h3>\n\n\n\n
The First Test<\/h3>\n\n\n\n
Observations<\/h3>\n\n\n\n
The Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
<\/li>
<\/li>
<\/li><\/ol>\n\n\n\nThe requirement<\/h3>\n\n\n\n
<\/figure>\n\n\n\nIdentification of Nouns<\/strong><\/h3>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n\n\n\n[gist https:\/\/gist.github.com\/krsmanian1972\/6c75c02c795add7a7cea83f798b39b21 \/]\n\n\n\n
<\/p>\n\n\n\n
\n\n\n\nEvolving the design<\/h3>\n\n\n\n
The First Test<\/h3>\n\n\n\n
Observations<\/h3>\n\n\n\n
The Second Test<\/h3>\n\n\n\n
<\/figure><\/li><\/ul>\n\n\n\n<\/figure><\/li><\/ul>\n\n\n\nCode for the Article<\/h4>\n\n\n\n
https:\/\/github.com\/krsmanian1972\/TaskAllocation<\/a><\/h4>\n\n\n\n
Finally<\/h3>\n\n\n\n
