Being a successful start-up requires more than the right idea and good timing; if your product includes software, then it also requires a software development strategy.
Like most other start-ups, Specshell is founded on an innovative idea: by utilizing in-situ spectroscopy, they had cracked the code to monitoring crucial stages in the process of brewing beer. Two of the largest Danish breweries alone can save over 30 million euros worth of failed beer production every year by applying the algorithms and monitoring equipment that is under way in Specshell’s labs. But, to release its vast potential, Specshell needed software to process the large volume of data that would feed the complex algorithms they had developed.
With very little knowledge about software in general and software development processes in particular, Specshell decided to employ a computer science student programmer on a part time contract.
Lars Kruse, Partner at Eficode Praqma remembers their first encounter with Specshell:
“Specshell approached us through a common friend and asked us to help formulate the job ad for a student programmer, but with our insight into the magic of software development, we feared that the work at hand was dramatically underestimated and far too complex to be coped single-handedly by a part time student programmer.”
In the end, Eficode Praqma offered to find a suitable student programmer, lay-out the software architecture, build the continuous delivery pipeline and guide the student programmer until she was capable of building up momentum and navigate the direction herself.
Christian Nybo, Specshell co-founder explains:
“Lars Kruse understood our business idea from the very beginning and gave us a very generous offer on consulting. We chose to work with Eficode Praqma because their consultants know coding processes, tools, and strategies to perfection - and just as importantly: they are excited to work with start-ups.”
Over the course of roughly three months Eficode Praqma hosted the student programmer, who had unlimited access to two designated consultants from Eficode Praqma. They helped the young programmer clarify Spechshells’s needs, shaping a suitable system architecture and a protocol for exchanging data. As a result of this process, Specshell now has a unique foundation code base that their own staff can continue to develop. But most importantly they also have a continuous delivery pipeline; complete - but inexpensive, since it’s built solely on open source technology and best practices.
Christian Nybo looks back on the process:
“Eficode Praqma helped us move from a separate algorithm to specific digital solutions that are the basis of the critical data processing stage of the product. With the viable software, Specshell has been able to demonstrate a functional system and we have now received additional funding that will allow our start-up to move from proof of concept to approaching the market.”
On the question, why Eficode Praqma finds it interesting to offer counseling and consulting services to start-ups at a price that seems ridiculously inferior to what it’s actually worth, Lars Kruse laughs and throws a quote from the DevOps bible ‘The Phoenix Project’: “All unicorns were once horses” and elaborates:
“All the successful unicorns that we praise and are impressed by today, Google, Netflix and Spotify, all took DevOps and continuous delivery very seriously right from the beginning when they were just small start-ups. We believe that implementing continuous delivery as a concept is a prerequisite for potentially becoming a unicorn. Becoming best friends with horses that later grow to become unicorns is an investment we believe in.”
What testing steps should you include in your Continuous Delivery pipeline? Don’t just string together existing manual processes - use simple, collaborative tools to design something better!
A new card game to design Continuous Delivery pipelines
Continuous Delivery and DevOps are here to stay and not because they’re being practiced by trendsetting unicorn companies. The fact is science tells us that these approaches work and this year’s conference gave us lots of examples.
Continuous Delivery and DevOps - Not Just For Unicorns
A developer that pushes their changes and goes on a celebratory walk to the water cooler is done. But, they’re not done done, their changes have yet to be thoroughly tested, added to future release notes, properly peer reviewed and more. These are pains we want to rid the software industry of, and here’s how we do it.
How we tell the Continuous Delivery story
Immutable infrastructure as code reduces inconsistency and makes deployments faster and easier. We can provision immutable infrastructure with Packer & Terraform. Let’s use them to provision Jenkins Windows build slaves.
An immutable infrastructure approach
The Continuous Delivery and DevOps Conference took place in Stockholm for the third time. It brought together scientists, thought leaders, and practitioners to share their experiences and thoughts on CoDe and DevOps.
Inspiring approaches to Continuous Delivery & DevOps
Only a year ago, I was a CoDe Academy student learning about Git, Docker and Jenkins. This year I’m teaching Docker to 24 students at CoDe Academy 2017 in Aarhus.
Falling in love with Everything as Code and Automation
Hear about upcoming events in Scandinavia, latest tech blogs, and training in the field of Continuous Delivery and DevOps