Wednesday, November 29, 2017

AI - Intelligence is getting Hybrid

Cooperative learning among networks will lead to hybrid intelligence
Neural networks will evolve from monolithic to distributed co-operative/competitive models. Coupled with evolving neural-fuzzy and generic fuzzy algorithms — reinforced learning models that are more adaptive to the environment and context (i.e., too noisy and time-varying systems) — these neural networks will evolve into hybrid intelligent systems that integrate different learning and adaptation techniques to overcome individual limitations

Tuesday, February 7, 2017

Congrats! CSC Distinguished Engineers & Architects 2017

Yesterday CSC announced Distinguished Engineers & Architects, Batch 2017

Congrats to all the distinguished folks. Welcome on board...

Distinguished Architects 
Randy Arthur (Americas) serves as product owner for CSC’s IaaS offerings and as a lead solutions
architect for complex integration projects involving cloud computing technologies. During his 16-year
career with CSC, Randy  has worked successfully in various roles including midrange service delivery,
pre-sales solution development and product management. He was the first CTO of CSC’s Cloud 
technology “incubator.”

Graham Chastney (UKI&N) is a global domain architect experienced in workplace technologies, 
solution strategy and solution governance. He is a global collaborator who is relied upon to provide
thought leadership to solution teams and to build and development teams. Graham is the founder 
and lead author of the Technology Perspectives blog, which he regards as part of a broader ambition
to enhance CSC productivity and collaboration.

Ged Cunliffe (UKI&N) is the industry chief architect for CSC’s UK manufacturing business. With over
30 years of experience, he has directed and delivered solutions for clients in aerospace, defense and
manufacturing. He has a passion for technology that encourages him to uncover new and emerging
technologies and introduce them to CSC and its clients.

Max Hemingway (UKI&N) is an enterprise architect with over 29 years of industry experience, currently
working as chief architect on CSC’s BAE Systems account. He has led several multimillion dollar transitions
and digital transformation projects for our clients and has specific expertise in the areas of IoT, cloud, and 
design and deployment of applications, systems and network architectures. He is a Fellow of the British 
Computer Society and a Chartered IT Professional, holds the TOGAF (The Open Group Architecture 
Framework) Certification and is a STEM Ambassador.  He is also an active tech blogger

Distinguished Engineers
Stu Downes (UKI&N) is a solution lead within the CSC MyWorkStyle offering group. Stu’s role working 
with product management, industry analysts, key clients and partners gives him a unique view of market
trends and client needs. Since joining CSC in 1999, Stu has had a number of roles delivering, designing
and leading solutions and products. Stu won a 2016 CSC Sales Excellence award for the workplace 
solution for the UK Metropolitan Police Service.  An author of the digital shifts position paper 
The New Digital Workplace is Contextual,” Stu focuses on shaping workplace products that
enable the hyper productive digital workplace. He blogs at

Dr. Greg Kelaart-Courtney (AMEA) is a global senior principal and business and technical thought leader
with over 30 years of  expertise guiding large complex programs throughout the Middle East, Africa, Central
and Eastern Europe, Latin America, and Asia Pacific. Greg is known as a skilled consultant and subject matter
expert who possesses in-depth knowledge of the public sector, travel and transport, healthcare and life sciences,
financial services and telecommunications industries. He demonstrates continued success in aligning customers’ 
strategic vision to viable business and IT strategies, with a passion to lead these programs from inception to

Andrew Lee (UKI&N) is a performance engineer in CSC’s Global Business Services division in the United
Kingdom. He has over 26 years of experience creating performance models for application and system 
architectures of many types, from avionics to healthcare to law enforcement. He has a deep understanding
of the performance life cycle and the implications of design decisions across all technologies. He regularly 
blogs about performance engineering and modeling on his website at

Meganen Naidoo (ANZ), a solution architect in CSC’s Sales Solutions and Delivery Architecture team, is 
deeply involved in defining architecture, roadmaps and solution designs, and undertaking projects in line 
with business goals and strategy. An industry expert with 32 years of experience on IBM zSeries, he is 
often called upon by IBM to assist with IBM Redbooks and client presentations. He has authored three
books on the IBM z/OS operating system, and his certifications are responsible for CSC Australia being
compliant with the IBM zSeries, pSeries and Storage Reseller Partner program initiative.

Sunday, November 13, 2016

Infra Store - IT Marketplace

We all are familiar with Apple AppStore or Google Play Store we visit every day to download apps, games and necessary updates for our phones and tablets. AppStore model revolutionize the market place idea making it easy for both the software vendors and consumers to publish and install the software without the hassles of software building, distribution and deployment.

This success encouraged organizations to adopt the same market place model for distribution of enterprise software through enterprise app stores. Through these stores IT could deliver the software and updates with improved OLAs while realising true IT charge back models

While on the other hand, SDN (Software Defined Networks) changed the IT infrastructure paradigm replacing dedicated hardware devices with software components wherein a set of virtualized machines can play the role of routers, switches, gateways (even more than one at a time). This created new possibility in the form of spinning components dynamically to respond to demand of the hour which by traditional means was not possible. Still better, now these software driven virtual devices are apps making it simpler to build, deploy in a dev-ops ways while interact with the other apps to form part of the MeshApp schema of things.

Now imagine a situation wherein we can bring the best of both the worlds and create a new marketplace, a marketplace of IT infrastructure where IT devices are available off the shelf for an IT admin to select and add to the the dynamic network layout on the fly (device on demand model). This type of device store marketplace can delivery all the advantages of enterprise app store like workflow driven approval mechanisms, on demand chargeback models etc., which eases the cost of implementing and maintaining IT governance. These type of Infra Stores can create more and more possibilities which we have not thought through at this point.

Sounds interesting, write to me if you have more thoughts to share on this or to discuss how to implement these models

Wednesday, August 31, 2016

Building MicroServices! Real Fun...

I have been coding for more than 25 years and used more than 18 different programming languages (and the framework each is good and strong at) spanning every programming style from simple scripting, procedural to objected oriented to dynamic, functional (more attractive to Software Engineering community these days). Let me confess, every time I switched to new language or style I always felt “Oh, hope I also had that”. Trust me no language is complete; no style is perfect. So only way to feast your programming appetite is try something different which gives the flexibility. I honestly think, MicroServices style of application is the one that gives the needed flexibility.

It is not said and done. We need a more pragmatic answer to the question “Why it is fun?” In my experience, the biggest challenge in designing & building software systems is that of the identification of all the bit and pieces of the jigsaw puzzle. As we know, it is never easy to identify the position of any piece when we start. We get more clarity as we start putting the bits together. But still we do the mistake of attempting to design a software system upfront in a big piece (most of the core and add additional functionality to the core which is not expandable incurring more and more technical debt). Ideally what we need is a model or mechanism through which we can identify and build smaller components and put them together with great ease. This is why we use lean agile process. But what is the use of an agile process when our engineering approach is monolithic. This is where microservices approach rocks.

microservices are small building blocks of the application which can be put together to build the complete application functionality. Keep building smaller components and weave them together. Need a new functionality? Build and deploy a new microservice. This simple change in perception of developing application provides the flexibility of evolving the application architecture and design as we find more and more pieces of the jigsaw. This helps us in practicing the true agility in software engineering right from design and architecture, not just code development cycles.

Developing smaller blocks eases the pressure of coding and maintaining application modules. Smaller code footprints reduces dev/test/release cycles. Helps in quickly identify and fix bugs. Quickly address business process changes as we can quickly build and deploy a new service without having to fiddle with existing code.

Also, microservices are completely independent of each of other interfacing through messages. This improves application cohesion and helps in scalability. This not only means each can have their dev and ops cycles but also they can have their own technical stack providing completely technical freedom. No challenge of deciding the completely technical stack upfront, application design dictated by technology, tech stack lock downs, challenges in getting right and enough technical resources to dev and maintain etc.,

Moreover, microservices also help in controlling the technical debt.

Wednesday, May 18, 2016

TensorFlow at heart of more AI Research Projects for Google

Since it is open sourced, Google TensorFlow is becoming a more and more popular choice for AI enthusiast and researchers. With its recent announcement of DeepMind using TensorFlow for all its future research activities Google is reiterating its confidence on TensorFlow.

Other google AI research projects using TensorFlow includes

  • DeepDream, Google's visual AI that could transform photos into psychedelic art
  • Magenta - Google's quest to find "Can machines make music and art? If so, how? If not, why not?". To be officially launched on June 1st 

Tuesday, April 12, 2016

Your code on Github - What itz worth?

I am an open source proponent and contributor. As a hobbist I build lot of cool tools and apps which I keep posting onto my GitHub handle. However, to be frank with you so far I never posted any license agreement along with my code. May be I am bit lazy to spare time and research on the open source license models and identifying one which is suitable for me.

Recently while searching in Open Source Licensing models and implications I came across Steven Burnap  answer on stack exchange thread "Open source code with no license… can I fork it?". Further exploration of GitHub opensource license page  I found...

What happens if I don't choose a license?

You're under no obligation to choose a license. It's your right not to include one with your code or project, but please be aware of the implications. Generally speaking, the absence of a license means that the default copyright laws apply. This means that you retain all rights to your source code and that nobody else may reproduce, distribute, or create derivative works from your work. This might not be what you intend.

Even if this is what you intend, if you publish your source code in a public repository on GitHub, you have accepted the Terms of Service which do allow other GitHub users some rights. Specifically, you allow others to view and fork your repository within the GitHub site.

If you want others to use, copy, modify, or contribute back to your project, we strongly encourage you to include an open source license.

This made me realize the code I was posting on GitHub with the intent of attracting tech enthusiast to use it in the best interest of technical community was not serving the purpose.