The embedded industry shares experiences and challenges
Diverse companies in the embedded industries showed up for Embedded Accelerator Day Oslo 2017. Excellent talks and valuable open space discussions gave everyone food for thought. This blogpost recaps the day.
After everyone stocked up on a healthy breakfast and, more importantly, a sufficient amount of coffee, Lars Kruse greeted us all.
A lot of cool companies are present. We span many interesting industries, including oil, gas sensor, microchips and more. The one common point: everyone is doing embedded development. Lars introduces the day and the program and gets everyone on the same page. Yes, there are many challenges in embedded development, but we can do Continuous Delivery. Many of the companies are already doing Continuous Delivery to some degree.
Lars introduced the keynote speaker: James Grenning author of Test driven development for embedded c. It was a pleasure to hear James talk. The topic was technical excellence. How do we avoid stagnating as expert beginners.
James told us about the second meeting of the founders of the Agile Manifesto. They met to celebrate the ten year anniversary of the Agile Manifesto. After all this time their most important bullet became “Demand Technical Excellence”. Good food for thought. No finger pointing!
“I’m a programmer and I write bugs”.
Even though James has a background in the embedded world, his talk was not very focused on it. Instead, it made the point that we should stop using the embedded world as an excuse for not embracing automation and Continuous Delivery.
Mike Long took the stage and showed us how we can do Continuous Delivery in an embedded context, there truly no excuses left.
If there were any doubts whether any of this “Continuous Delivery” craze is achievable, Espen H. Albrektsen of GasSecure, blew them away. He told the story of how they are working with automation and how it helps them be SIL2 certified with their sensors for detecting gasses.
We saw both the product, their test rigs and targets. He posed the question “Can we have fun developing software that is SIL2 compliant?”. The answer is “Yes, Jenkins allows us to do that”.
Our lunch was delicious, though I must admit that I did not try the whale sushi. I’m not that experimental when it comes to food. Invigorated, we launched ourselves into discussion groups. Two sessions of three groups under the headings DevOps, Culture, Build, Testing, Version Control and Architecture and Design.
Lots of interesting challenges and solutions were brought forth during these discussion. To the benefit of both the established businesses and those that did not have any code at all yet.
After the open space dicussions ended, I got to give my talk, “Why should I learn Git? I’m just a software developer”. As a fitting ending to the day tying back to James’ “Demand technical excellence”, I talk about Git and why you should be great at it. We also look at some fun numbers and stats. I talk briefly about deliberate practice and point people to Git katas, some great self-contained exercises for deliberate practice of Git. It was a great crowd, most were already working in Git.
We closed off with a brief retrospective leading in to beer and wine. I for one am very much looking forward to the next Embedded Day!
More about the event on www.code-conf.com
See photos of the Embedded Accelerator Day.
Had enough of sluggish polling? With instant Artifactory event triggers you can give responsiveness in Jenkins a real boost. Here’s an easy way to set it up.
A super easy configuration guide
With the arrival of microservices code is becoming disposable. Does this mean that we no longer need maintainable code? Is it the end of refactoring?
Still relevant or increasingly redundant?
In software development tight coupling is one of our biggest enemies. On the function level it makes our application hard to change and fragile. Unfortunately, tight coupling is like the entropy of software development, so we have always have to be working to reduce it.
How to safely introduce modular architecture to legacy software.
I am an Atlassian certified trainer and over the years I have been spending much time with clients and their Jiras. In this blogpost, I have collected some small tips and tricks that will make your Jira usage better.
Jira Software is a powerful tool deployed in so many organizations, yet in day to day usage people are missing out on improvements, big and small.
In this post, I’ll take a closer look at the version of Jenkins X using Tekton, to give you an idea of how the general development, build, test, deploy flow looks like with Jenkins X. How does it feel to ship your code to production using a product coming from the Jenkins community that has very little Jenkins in it?
A crash course in Jenkins X and how to test it out on a local Kubernetes cluster
In this blog I will show you how to create snapshots of Persistent volumes in Kubernetes clusters and restore them again by only talking to the api server. This can be useful for either backups or when scaling stateful applications that need “startup data”.
Sneak peak at CSI Volume snapshotting Alpha feature
When I read Fowler’s new ‘Refactoring’ book I felt sure the example from the first chapter would make a good Code Kata. However, he didn’t include the code for the test cases. I can fix that!
Writing tests for ‘Theatrical Players’
Nicole Forsgren and the Accelerate DORA team has just released the newest iteration of the State of DevOps report. The report investigates what practices make us better at delivering valuable software to our users as measured by business outcomes. Read on for our analysis of the report, and how it can be best put to use.
The latest drivers of software delivery performance
A major challenge of software development is that our work is by and large invisible. This makes our folklore essential in business matters. Some of our commonly used arguments and visualizations are digital urban legends rather than solid foundations for informed decisions. Here, we’ll go through a few examples and some measures to address our misconceptions.
How the stories we tell influence our decisions
When you embark on your cloud native journey there will be important choices to make about cloud providers, continuous deployment, environments’ setup and separation. This guide will help you make the right choices by sharing lessons learnt from running cloud native apps in production.
Kubernetes has become the de facto container orchestration platform. When we help clients of different sizes and domains start their cloud native journeys in Kubernetes, we assist them in making sound decisions and technology choices. There is no one-size-fits-all solution when it comes to choosing cloud providers, CI tools, continuous deployment pipelines etc., so it is important to make the right decisions at the start. Failing to do so can be very costly in terms of lost time and money.
How to make the right technical choices on your cloud native journey
Hear about upcoming events in Scandinavia, latest tech blogs, and training in the field of Continuous Delivery and DevOps