Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Stress-free software releases
Search
Sponsored
·
Your Podcast. Everywhere. Effortlessly.
Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
→
Tosho Trajanov
November 10, 2019
Technology
300
0
Share
Stress-free software releases
Tosho Trajanov
November 10, 2019
More Decks by Tosho Trajanov
See All by Tosho Trajanov
The click that saves weekends
tstrv
0
43
Other Decks in Technology
See All in Technology
Cursor Subagentsはいいぞ
yug1224
2
120
Zephyr(RTOS)でARMとRISC-Vのコア間通信をしてみた
iotengineer22
0
110
AgentCoreとLINEを使った飲食店おすすめアプリを作ってみた
yakumo
2
270
Navigation APIと見るSvelteKitのWeb標準志向
yamanoku
2
130
Oracle AI Database@Azure:サービス概要のご紹介
oracle4engineer
PRO
4
1.3k
Kiro Meetup #7 Kiro アップデート (2025/12/15〜2026/3/20)
katzueno
2
270
「活動」は激変する。「ベース」は変わらない ~ 4つの軸で捉える_AI時代ソフトウェア開発マネジメント
sentokun
0
130
DMBOKを使ってレバレジーズのデータマネジメントを評価した
leveragestech
0
490
MCPで決済に楽にする
mu7889yoon
0
160
開発チームとQAエンジニアの新しい協業モデル -年末調整開発チームで実践する【QAリード施策】-
kaomi_wombat
0
280
Sansanの認証基盤を支えるアーキテクチャとその振り返り
sansantech
PRO
1
120
ハーネスエンジニアリング×AI適応開発
aictokamiya
1
900
Featured
See All Featured
Game over? The fight for quality and originality in the time of robots
wayneb77
1
150
Bioeconomy Workshop: Dr. Julius Ecuru, Opportunities for a Bioeconomy in West Africa
akademiya2063
PRO
1
79
Documentation Writing (for coders)
carmenintech
77
5.3k
Bash Introduction
62gerente
615
210k
We Are The Robots
honzajavorek
0
210
Optimising Largest Contentful Paint
csswizardry
37
3.6k
Marketing to machines
jonoalderson
1
5.1k
WENDY [Excerpt]
tessaabrams
9
37k
How GitHub (no longer) Works
holman
316
150k
Introduction to Domain-Driven Design and Collaborative software design
baasie
1
690
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
254
22k
Building a Modern Day E-commerce SEO Strategy
aleyda
45
9k
Transcript
Stress-free software releases BGPHP 2019, Sofia
@TsTrv CTO Adeva - An Exclusive Developers Network Fully-distributed network
Worked with startups and Fortune 500 companies
@TsTrv Building strong engineering processes
@TsTrv Nirvana in software engineering
@TsTrv State of the application ー Legacy, enterprise application built
in PHP ー Being developed for over 10 years ー 0% test coverage ー 10 engineers - to keep it alive
@TsTrv The problems ー Unable to ship as fast as
we needed ー Never ending bug fixing cycles ー Full-regression testing took 3-4 weeks ー Releases once monthly ー Scheduled on weekends
@TsTrv Formula for stress and burnout
@TsTrv Continuous Everything
@TsTrv
@TsTrv Objections ー Complexity ー Risk ー Control ー Habit
@TsTrv Continuous Everything
@TsTrv Continuous Everything… Nirvana
@TsTrv Continuous Everything… Nirvana
@TsTrv Continuous Everything… Nirvana
@TsTrv Continuous Everything ー If you fail, you fail small
ー If something breaks, you know to fix immediately ー Fewer bugs ー Release new features faster ー Reduce Costs
@TsTrv What could potentially go wrong?
@TsTrv What could potentially go wrong right?
@TsTrv Legacy code ー Strangler Pattern ー Branch By Abstraction
Technique
@TsTrv Strangler Pattern
@TsTrv Branch By Abstraction
@TsTrv Automated Tests
@TsTrv Automated tests ー Assume legacy works flawlessly ?! ー
Utilize new modules to Increase the code coverage
@TsTrv Pipeline
@TsTrv Deployment vs Release ー Decoupling ー Feature Toggles –
Dark Launching – Phased rollout
@TsTrv
@TsTrv Deployment Strategy ー Blue Green ー Canary deployment
@TsTrv Blue Green Deployment
@TsTrv Blue Green Deployment
@TsTrv Canary Deployment
@TsTrv Mindset ー Everyone should participate ー Not a DevOps
work only ー Continuous improvement, day by day
@TsTrv Actions ー Wrapped up the legacy code ー Faked
automated tests for the legacy ー Identified pipeline ー Decoupled releases from deployment ー Created a culture of continuous improvement
@TsTrv Wins ー Release code to production multiple times daily.
ー Production bugs lowered by 80% ー From bug report to deploy < 30 mins ー No more weekends work
@TsTrv Always strive for continuous improvement, instead of perfection.
@TsTrv Thank you