#IBMIntegrationBus modern #devops #automation setup – testing, containers, codecoverage

Currently I use the following IIB Tools to automate as much as possible and to be scalable in (multiple 😉 ) seconds, if you have tools I should have a look at please share with me:

#failed to make it to the best 40% at a hackathon. #frustrating #workharder

Today the cognitive hackathon at IBM IoT ended and my personal result was: bad. I did not make it to the top 3 from 8 teams. That was frustrating and I was disappointed with myself. So …

The task was to build a cognitive car concierge services. Our result was a chatbot that had
– an active voice interface (you could have a dialog without clicking all the time to speak),
– predictive notifications (about your fuel) based on your driving target and the real time vehicle data,
– it also would find the nearest Drive Now Vehicle,
– it could turn on your car (simulated by a hue light, but this could be a call to the CAN Bus of a real car)
– it could interact with google maps to find the best route.
– it had JWT based authentication in every micro service.
– it could schedule calls with your personal call center agent (you don’t need to call, but based on your problem and your customer relationship data and the calendar of the agent the best spot would be found) as well as rescheduling

Well in the end I did not perform (to my own expectations), but at least I learned somethings:
reality-check: I am better then 1 year ago, but still mediocre compared to the best in the field. I will have to work harder.
frontend is important: My failure was missing a WOW frontend, I should always keep practicing at least some frontend in the future
i don’t present very well: I did not do this for some time and I seemed totally of my game, like a 4 year old. I have to get this fixed fast. I have to do more public vlogs and learning videos, go to hackthons where I present.
it is all show: Technology does not count, as long as you have a great mockup that seems interactive it is enough. If your forced to use technologies you don’t like, just change the game and present a mockup how you would do it there but focus on the tech you like.
starter kits matter: I definitely have to improve my starter kit to be more extendible and to be better on the eye also the analytics/data component is essential.
only consider jobs where you have people better than you: Even though I failed miserably overall, it seems from a tech perspective I was one of the better ones. And in my job I focus on learning so I would need to be in a team where most of the people are better than me.

  • Now I will just put some EDM on my ears and work hard and next time, which will then be my second hackathon, I will be better.*

Let’s get down to implement the persistent high performance message bus integration (based on the work Blizzard has done) into the starter kit.

#FutureOfWork: The impact of #AI on the workplace and employee engagement

• The digital workplace merges work and life — a virtual space with applications, services and information on demand. For users, this means access to the technology they need, when they need it, on whichever device they prefer to use.

• Employees expect their enterprise systems to be as engaging, exciting and intuitive as consumer devices. Technology research company Gartner calls this a shift from technology-literate people to people-literate technology.

• Companies now have more exquisitely detailed data about how their products and services are used than they ever had before, thanks to a vast network of sensors and advanced analytic tools.

• Cognitive systems can parse all that data and learn what employees need to do their job better — even if they don’t yet know it themselves. Cognitive systems will deliver the ability to visualize vast amounts of data, curated and analyzed, for a unique task and a unique user.

• The workplace of the future will embrace emerging new cognitive and analytic capabilities. These tools can provide insights into how employees engage most effectively, what the best technologies are for each task and for each individual, and help provide a seamless work environment — an environment that will help to attract and retain the best talent.

[Source]

DOING THE REACT TUTORIAL | LIVE CODING #1 | BUILDTHEFUTURE

Modern application are delivered with web technologies – no discussion. Congratulations Javascript you have won. And with React and it’s virtual DOM the performance increased to a level that is close to native. So I decided to get my hands dirty and do the official react tutorial. Hope you enjoy this guys.

NPM vs Gulp – Do I need a build javascript system besides npm scripts

#NPM vs Gulp – Do I need a build javascript system besides npm scripts

First when I look at npm vs gulp I was like, well I can do this with npm scripts, why to learn another tool.
So I tried to make it happen with just npm scripts, this worked great until I tried to automatically create
responsive images with imagemagick. This would have required me to write a complete bash script.

Advantage npm script:
– I just write my build steps as shell commands and I am independent of the lifecycle of certain tools like gulp. As the bash script is portable.
– I minimize the tooling I need to learn. No need to install an additional command-line tool to run your build.
– They don’t have the complexity of a full build tool.

Advantage gulp:
– A tool like Gulp gives you the full power of Node and JavaScript.
– They provide consistent APIs optimized for composing build tasks.
– They offer huge ecosystems of plugins for almost anything you can imagine.
– They avoid cross-platform compatibility problems.
– Gulp is javascript and no additional DSL.
– Gulp increases the performance by doing the build steps in parallel.

So I see that gulp is not so much more to learn as I don’t have to learn a tool with it’s own language. So my decision is I use the best tool for the job if it is in java or javascript.

My solution:

  1. I learn gulp and write my build tasks in javascript.
  2. I include gulp in my npm scripts with the following code into my ‘package.json’:
{
  "scripts": {
    "build:prod": "gulp build --prod",
    "build:dev": "gulp build"
  }
}