The goal of my talk is to make you a more competitive programmer.
How the average programmer thinks? “Ok, I am the programmer, I like to program, and I will program.”
However, programming is just a small part of the software development process.
It all starts with discussing an idea, then the idea turns into a task/issue, then you dig into the details, prioritize and plan, and lastly you'll start drafting your code. When the code is written, it should be tested and reviewed. New version should be tested on Staging, and then if approved, it can go to Production. Finally, you get a feedback from your customers, and the whole cycle starts from the beginning.
I suggest adding GitLab CI to your arsenal of tools. You’ll become more valuable by being able to automate any routine task, such as running tests, generating builds, and deploying your code.
Initially, this talk should have been called “Breaking Bad with GitLab CI”, and I was going to cover non-standard ways of GitLab CI utilization. However, let’s start by Breaking Bad Habits of not automating routine tasks!
You can consider this talk a mini-workshop because it is not just a demo or introduction. After you understand the principles, you will be able to use GitLab CI with any technology stack.
The first paragraph is crucial to attract people to your talk and those first sentences don't have anything to do with your talk or what attendees will get out of it. I suggest to shorten this abstract to maybe two paragraphs indicating what the talk is about and what people will get out of it. What problems are you solving that current solutions (Jenkins, Travis, Bamboo, etc) don't have. How will they become better developers or create better apps by learning this?