Code Story episode
S10 Bonus: The CI/CD Performance Shift: Accelerating Build Pipelines and Eliminating Developer Idle Time with Darko Fabijan, Co-Founder & CTO of Semaphore
Apr 10, 2025 · Season 10 · 25 min
Semaphore has gone open source!
Darko Fabijan is originally from Serbia, and splits his time between their and the US. He got is first computer in 1994, and eventually started tinkering and playing with Linus. He went to university in 2003, and then started a company with a college friend, which was a rails consultancy. Outside of tech, he is married, with 2 kids - ages 3 and 9. The older one is into athletics, and the younger one is more into art. He enjoys spending time in nature with his family, and got into trail running a few years ago - recently running a 64km trail. He enjoys business books because he likes to see how other people "did it", when it comes to their successes and failures.
In 2011, Darko was running his consulting shop with 7 or 8 people. As they were developing applications, they couldn't find anything for continuous integration where you just "signed up" and it worked. That was enough for them to get out there and build it on their own.
This is the creation story of Semaphore.
Sponsors
MailtrapSpeakeasyQA WolfSnapTradeLinks
https://semaphore.io/https://www.linkedin.com/in/darkofabijan/
Checkout our episode stacks on Stacklist! https://stacks.codestory.co/
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
More episodes
Keep listening
Topics
Explore related conversations
Startup engineering team structure that actually ships
How to structure a startup engineering team: the models that work at 5, 15 and 40 engineers, how to split teams, and the org mistakes that quietly slow delivery.
How to choose a tech stack for a startup
A decision framework for choosing a startup tech stack: what actually matters, which choices are reversible, and how to avoid the rewrite that eats your Series A.
Build vs buy: a decision framework for technical leaders
When to build software in-house and when to buy it: a build vs buy framework covering total cost of ownership, differentiation, switching costs and vendor risk.