“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?



Usage of information sources for implementations in IBM Cloud

Why should I blog about this? Of course, you can just “google” and find the sources by your own.

I write this blog, because I want to share briefly my experience, about the different IBM Cloud information sources: the IBM Cloud Documentation, the IBM Developer and the IBM Cloud Garage, when I did implementations with IBM Cloud.
I hope when you read this blog, you can save time finding the right information in the future.

Let me start this blog, with this following statement:

“Finding the right information, depends on your expectation”

This is a simple and obvious statement, but from my perspective simple knowledge must be repeated, to get the right attention.

What are my expectations on information sources?

When I start searching for implementation topics, I have mainly two different high-level expectation categories, the “content” and the “consumability”.

Here are my three major expectations on the content, when I search for implementation topics in IBM Cloud.

  1. First expectation I want sample source code, which is executable. The best would be, if my finding directly matches to my technical or use case problem.In short words: “I need to get executable code!”


  2. Second, the development process topics are relevant for implementation. Mainly how to organize myself. Today agile is the usual way. How does this work?Short: “I want the right method/tools, which do support my daily “implementation” work!”


  3. Third, I want help in finding the right architecture for my implementation approach inside IBM Cloud.“Which components do I need to implement my application in IBM Cloud?”

My first expectation is fulfilled in each the of given information sources. Each source points to sample code in github, which can be used to build a running applications.

Continue reading