The Cocktail Pattern

 AS-IS --> TO-BE 

Migration of software projects and rollout could take time for big business systems.

Legacy and new Designed Systems have been worked together for years.

OR

Somehow, some parts of legacy system continues to work together and If it works, not change rule brings good luck. 

So, this can be called as Cocktail Architecture that we need works together old and new. 

Look Mom! No developer

 Data -- information -- knowledge 

If a tool makes code review autonomously, do not hesitate as it can code. 

Belady's impossibleness

GPU is like a milk in AI coffee :) AI as a service in software engineering is becoming an inevitable part 

andddddddddd 

Now, my new interest is on cache structures inspired from Belady's Cache.  

So; Enjoy!

Learning et al.

TL;DR 

 

Rule Based Software Development: do not code same flow twice!

To be honest, If I code in similar projects and I prefer to code for code generation automatically. It's not full automation but definition based source code generation is exciting. Of course, If your customer needs are well shaped with certain metrics, the development process becomes easier.

20 years ago, I was thinking about software automation, I had been estimated to see quite improvements in software automation tools in 10 years. Now when I look back, some enhancements occurred such programs,  frameworks etc. But not too much that I estimated.

Actually, change is only constant but automation needs time but not too much.