big open source players were “cap by hat” @w-jax

I was at winter-jax 2018 in Munich last week. This was my first time I attended this big developer conference.

IMG_1948.JPG

As you can see in the headline picture, two big players in open source area with cap by hat and  IBM, RedHat booths and with Viada  😉

One major topic this week was the potential deal, IBM is planning to buy RedHat for 34 billion US dollars. This potential deal played a big part in Sebastian Meyen´s opening speech on the first day of the winter jax conference in Munich.

He highlighted the history and  Red Hat´s contribution to open source.

If you want to listen his speech in German, you can watch the sessionon youtube here  . His speech is before the keynoteTrust and confidence through chaos” from Russ Miles

By the way, I like Russ Miles´s approach to “chaos engineering” .

My very high-level free interpretation of “chaos engineering” is:

  • “Break the system, before it breaks your business!”

From my point of view “chaos engineering” is more or less comparable with testing. So, I defined more detailed, free interpretations:

  • “Don’t be afraid and learn from testing/failure”
  • Bad news … yes, testers want to break your system, but the good news is: they will do it, before you run it in production 😉 “

Open source contribution

A very good match to the open source topic was the keynote from Christopher Ferris.

He asked the good question: Who pays for open source?  You can watch his session on youtube here

Christopher Ferris reminded us in his speech that IBM is a major player and contributer in open source, with a high involvement in Apache , Eclipse and Linux  during the creation and in development. These three projects are fundamental pillars for the open source business.

There are many other open source projects IBM contributes to, which you can find here  on the  IBM Developer site.

IMG_2057.JPG

Christopher Ferris during his keynote.

Open Source in AI

Also, Niklas Heidloff gave a session “Development of AI Applications without Machine Learning Skills”. In this session, Niklas also highlighted the topic open source with the Model Asset eXchange . The Model Asset eXchange contains free, deployable, and trainable code.

It is also very important to understand that these models on Model Asset eXchange are reusable for production, because they have licenses developers can verify.

IMG_1980.jpg

Image of the session from Niklas Heidloff. Here you can see some impressions from Niklas.

Open Source in Java

Steve Poole highlighted in his session “What’s new for Java in clouds?” that IBM open sourced OpenJ9 (Low memory footprint). Steve also reminded us in his session, that the Java community should be more active and should define the needs for cloud, machine learning and upcoming technologies like Quantum.

By the way Fernando Cejas did a session about Quantum Computing, you can check a sample here  “Quantum computing in action: IBM’s Q experience and the quantum shell game”.

IMG_2002

Moments

If you want to see our favourite moments of this conference, just visit the twitter moments from Miriam Oglesby.

Let’s see what’s next?

Greetings,

Thomas

PS: By the way, you can use the IBM Cloud for free, if you simply create an IBM Lite account. Here you only need an e-mail address.

“code pattern” – my point of view

Today I want to focus on a interesting question I got:  “Why does IBM call something a code pattern and not just sample?” The question was related to my last blog.

Here is my personal point of view

First, there is no existing definition of the word pattern in combination with usage of the word code.

  • Based on the given definition, here is my free interpretation of the word pattern :
    “A pattern is something you can reproduce in different areas, and this interpretation is more less always comparable to a sample.  “
  • The main difference between sample and pattern from my point of view is: 
    “A pattern is always created to reproduce something which worked and will work again and this is not the case with a sample.”

Sure, a code pattern is NO design pattern  😉 . The combination of the words design and pattern has an official definition.

From my understanding, IBM uses the word pattern in combination with code, with the intention of showing you that you can reuse the code in the way you want.

A code pattern does NOT need to be related to IBM products or IBM services, but it should be related to one or more technologies and should contain code, which a developer is able to reuse under an apache license.

Structure of the code pattern

A code pattern should always contain:

  • Clear definition of the used technologies
  • Should contain code which can be used to instantiate an application
  • Should contain the possible deployment models (cloud, local, and so on) of the application

A code pattern should always have the following high level structure:

  • Summary (main objective),
  • Description (what it does)
  • Flow (how it works)
  • Instructions (how to instantiate)
  • … and for sure the code, which is available on github

This was my personal perspective on the definition of a code pattern, based on my experience with code patterns so far.

I hope this was helpful for you and feel free to provide feedback 😉

Let’s see what’s next?

Greetings,

Thomas

PS: By the way, you can use the IBM Cloud for free, if you simply create an IBM Lite account. Here you only need an e-mail address.