Jason Yee - Chaos! - Codemotion Rome 2019

•

1 like•318 views

As applications become more distributed and complex, so do our failure modes. In this presentation, I’ll share why you shouldn’t just embrace failure, but why you should induce it to intentionally cause and learn from failure. Together with the audience, I'll run a Chaos experiment to show how they can start their own Chaos engineering and make their systems more resilient.

Technology

CHAOS!
Breaking your systems to make them unbreakable

–Barack Obama
“You can’t let your failures define you.
You have to let your failures teach you.”

– Corey Bertram
“Hope is not a strategy.”

J A S O N Y E E
Te c h n i c a l E v a n g e l i s t
Tr a v e l H a c k e r
W h i s k e y H u n t e r
P o k e m o n Tr a i n e r
Tw : @ g i t b i s e c t
E m : j y e e @ d a t a d o g h q . c o m

D ATA D O G
S a a S - b a s e d o b s e r v a b i l i t y
p l a t f o r m :
• M e t r i c s
• Tr a c e s ( A P M )
• L o g s
• S y n t h e t i c s
Tw : @ d a t a d o g h q
We ’ re h i r i n g :
j o b s . d a t a d o g h q . c o m

–Netflix Technology Blog, 2011
http://bit.ly/netflix-chaos
“By running Chaos Monkey in the middle of a
business day, in a carefully monitored environment
with engineers standing by to address any problems,
we can still learn the lessons about the weaknesses
of our system, and build automatic recovery
mechanisms to deal with them.
So next time an instance fails at 3 am on a Sunday,
we won’t even notice.”

“By running Chaos Monkey in the middle of a
business day, in a carefully monitored environment
with engineers standing by to address any problems,
we can still learn the lessons about the weaknesses
of our system, and build automatic recovery
mechanisms to deal with them.
So next time an instance fails at 3 am on a Sunday,
we won’t even notice.”
–Netflix Technology Blog, 2011
http://bit.ly/netflix-chaos

90 Minutes
30 minutes planning.
50 minutes playing.

90 Minutes
30 minutes planning.
50 minutes playing.
10 minutes reporting.

The Team
1 subject matter expert
1 SRE
Sometimes, 1 junior
engineer/developer

Before
• Schedule it.
• Pick tests. Start easy.

Before
• Schedule it.
• Pick tests. Start easy.
• Write down what you expect to happen.

Before
• Schedule it.
• Pick tests. Start easy.
• Write down what you expect to happen.
• Write down your plan if things go wrong.

Before
• Schedule it.
• Pick tests. Start easy.
• Write down what you expect to happen.
• Write down your plan if things go wrong.
• Share your document!

During
• Staging -> Production (off-peak) -> Production (primetime)

During
• Staging -> Production (off-peak) -> Production (primetime)
• Announce start in group chat.

During
• Staging -> Production (off-peak) -> Production (primetime)
• Announce start in group chat.
• Maintain discussion in group chat.

During
• Staging -> Production (off-peak) -> Production (primetime)
• Announce start in group chat.
• Maintain discussion in group chat.
• Monitor for outages.

During
• Staging -> Production (off-peak) -> Production (primetime)
• Announce start in group chat.
• Maintain discussion in group chat.
• Monitor for outages.
• Run your test and take notes!

After
• Create cards/tickets to track issues that need work.

After
• Create cards/tickets to track issues that need work.
• Write a summary & key lessons.

After
• Create cards/tickets to track issues that need work.
• Write a summary & key lessons.
• Email to all of engineering.

After
• Create cards/tickets to track issues that need work.
• Write a summary & key lessons.
• Email to all of engineering.
• Celebrate!

Game Levels
0. Terminate the service. Block access to 1 dependency.

Game Levels
0. Terminate the service. Block access to 1 dependency.
1. Block access to all dependencies.

Game Levels
0. Terminate the service. Block access to 1 dependency.
1. Block access to all dependencies.
2. Terminate the host.

Game Levels
0. Terminate the service. Block access to 1 dependency.
1. Block access to all dependencies.
2. Terminate the host.
3. Degrade the environment.
Monitor & alert on Latency, Errors, Traffic, & Saturation

Additional Resources
• systemctl, kill, iptables

Additional Resources
• systemctl, kill, iptables
• Comcast - https://github.com/tylertreat/comcast

Additional Resources
• systemctl, kill, iptables
• Comcast - https://github.com/tylertreat/comcast
• Vegeta - https://github.com/tsenart/vegeta

Additional Resources
• systemctl, kill, iptables
• Comcast - https://github.com/tylertreat/comcast
• Vegeta - https://github.com/tsenart/vegeta
• Kubernetes & Istio -
https://istio.io/docs/tasks/traffic-management/fault-injection/

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
name: wordpress-virtualservice
spec:
hosts:
- "*"
gateways:
- wordpress-gateway
http:
- route:
- destination:
host: wordpress
fault:
abort:
percentage:
value: 50.0
httpStatus: 500
delay:
percentage:
value: 50.0
fixedDelay: 30s

Additional Resources
• Gremlin - https://www.gremlin.com/
• ChaosToolkit - https://chaostoolkit.org/

Questions?
jason.yee@datadoghq.com
@gitbisect

Slides: bit.ly/cmr-chaos 
Documents: bit.ly/cmr-chaos-docs
jason.yee@datadoghq.com
@gitbisect

I hack people for money. Companies pay me to find vulnerabilities in their infrastructure. Everyone from small businesses to top corporations hire me and the company I work for to find the ways that a malicious hacker might compromise their systems and access data. The vector may be through a web site, through their externally facing networks, or even from insider threats in their network. I can also do social engineering, using your company's employees to give me the information I want. Let's talk about some of the methods that I use to compromise these targets and you can take away some areas to look at in your own business.

Red Team Diary: Meu Recon falhou e agora?

Arthur Paixão

EduSparkz Thunder Thursday Debugging Code

Satish AG

The Future of Testing Webinar

Alan Richardson

The recording in https://eviltester.com/talks has: - longer practice session recording - live recording - local recording better quality - 8 bonus recordings with an extra hour of material - will automation take over - impact of buzzwords - how to cope with trends - contextual problem solving - information about the references - exercises - behind the scenes look at how the talk was prepared and tools used - transcripts - subtitles

Failing @ Scaling: Don't Panic, and Carry a Towel - Agile2016

Em Campbell-Pretty

Presented at Agile 2016. Struggling with agile at scale? Thinking about scaling agile beyond the team? Want to learn from others mistakes? Well don’t panic, and carry a towel. After all “any man who can hitch the length and breadth of the Galaxy, rough it, slum it, struggle against terrible odds, win through and still know where his towel is , is clearly a man to be reckoned with.” There is a lot to be learnt from those who have successfully Hitchhiked their way to the galaxy of Scaled Agile, but there is also much to learn from those who have gotten a little lost upon the way. This session celebrates the scaled agile hitchhiker, the people who tried and failed, with ideas that were occasionally brilliant but often plain stupid. You will laugh, you will cry but you will also walk away will a nice long list of ideas not to try when scaling agile! Learning Outcomes: - 7 failure patterns in scaling agile - An understanding of why these patterns lead to less than optimal results - Tips on how to avoid falling into these failure patterns

Dev / non dev communication

aaronjorbin

Mobile CRO - The psychology behind selling to thumbs

Online Dialogue

Test Motherfucker...Test

Mario García

From Red Hat Agile Day Oct 20, 2015 Session 4 Advanced Track: You know “collaboration over contract negotiation’, right? However, metrics often drive a wedge between management and the team, none more so than forecasting metrics. However, when you give a probability distribution as the answer to the question, “When will we get it?” instead of a single date, an amazing transformation happens. Suddenly, the team and management start working together to manage tradeoffs and risk. You need two things to take advantage of this paradigm shift: 1) How do you start to think probabilistically?; and 2) How do you generate a probabilistic forecast or analysis? This talk provides mindset shifts necessary for #1 and lots of worked out practical examples for #2.

Five Cliches of Online Game Development

iandundore

How I failed to build a runbook automation system

TimothyBonci

Hushcon 2016 Keynote: Test for Echo

Deja vu Security

Continuous Automated Testing - Cast conference workshop august 2014

Noah Sussman

CAST 2014 New York: The Art and Science of Testing The Association for Software Testing www.associationforsoftwaretesting.org COURSE DESCRIPTION Automated tools provide test professionals with the capability to make relevant observations even in the fastest-paced environments. Automated testing is also a powerful tool for improving communication between software engineers. This is important because good communication is a prerequisite for growing a great software engineering organization. This workshop will explore the continuous testing of software systems. Special focus will be given to the situation where the engineering team is deploying code to production so frequently that it is not possible to perform deep regression testing before each release. People who participate in this course will learn pragmatic automated testing strategies like: * Data analysis on the command line with find, grep and wc. * Network analysis with Chrome Inspector, Charles and netcat. * Using code churn to predict hotspots where bugs may occur. * Putting stack traces in context with automated SCM blame emails. * Using statsd to instrument a whole application. * Testing in production. * Monitoring-as-testing. Technical level: participants should have some familiarity with the command line and with editing code using a text editor or IDE. Familiarity with Git, SVN or another version control system is helpful but not required. Likewise some knowledge of Web servers is helpful but not required. It is desirable for participants to bring laptops. BIO From 2010 to 2012 Noah was a Test Architect at Etsy. He helped build Etsy's continuous integration system, and has helped countless other engineers develop successful automated testing strategies.These days Noah is an independent consultant in New York. He is passionate about helping engineers understand and use automated tools as they work to scale their applications more effectively.

Software testing (2) trainingin-mumbai

vibrantuser

Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Why is Software Testing Important to a business? Software testing is a process to determine the quality of the software developed by a developer or programmer. It is a methodological study intended to evaluate the quality-related information of the product. Understanding of the important features and advantages of software testing helps businesses in their day-to-day activities. Testing can be done in two ways, manual testing and automated testing. Manual software testing is done by human testers, who manually check the code and report bugs in it. In case of automated testing, testing is performed by a computer using software such as WinRunner, LoadRunner, etc.

Scrum Plus Extreme Programming (XP) for Hyper Productivity

Ron Quartel

Secrets and Mysteries of Automated Execution Keynote slides

Alan Richardson

Angus Fletcher - Error Handling in Concurrent Systems

Maritime DevCon

Let's Sharpen Your Agile Ax, It's Story Splitting Time

Excella

This slide deck is from the recent presentation Brian Sjoberg gave at the DC Scrum User Group on August 25, 2016. It is about User Stories and how to split them. Do you want to write great User Stories (a.k.a. small features that are part of a product) that provide the vehicle for conversation and confirmation that we build the right thing? Do you struggle with splitting stories so that they still provide business value but can be accomplished within a fraction of your iteration and be potentially shippable to production? We will do a quick refresher on User Story formatting to include Acceptance Criteria. Additionally we will learn techniques for splitting stories in this interactive workshop. Here is a link the meetup - https://www.meetup.com/DC-Scrum/events/232765657/

Sharpen your Agile Axe by Brian Sjorber

Washington DC Scrum User Group

Getting Schooled DerbyCon 3.0TonikJDK

Coaching teams in creative problem solving

Flowa Oy

Agile has helped teams to collaborate and organize work better. That’s great. Better teamwork and better understanding of the work definitely helps a team to do right things. Agile has also lead the way toward technical practices such as Continuous Integration and Delivery, Test Driven Development and SOLID-architecture principles. Great, these things definitely help the team to do things right. Then again, most of the time in software projects goes into problem solving and similar creative acts. Agile has relatively little to give on these areas. Currently, agile is not about creativity nor is it about problem solving. This coaching circle session will focus on the creative core of software development: solving creatively novel, original and broad problems more effectively all the time. I will introduce some principles and tools I’ve found useful when helping people to solve hard problems and to find creative solutions.

Software testing (2) trainingin-mumbai...

vibrantuser

Chaos Engineering Talk at DevOps Days Austin

matthewbrahms

DevOps Days Vancouver 2014 Slides

Alex Cruise

Speaker: Alex Cruise (Dir. Architecture, Metafor Software) Abstract: The rise of the DevOps movement has brought into welcome focus something that is often learned only through painful experience and expense: the success of a software product critically depends not only on its implementation, maintenance and enhancement, but also on how it’s deployed and operated. Distributed systems are hard, but you can’t escape them: you need to scale out, but wrapping proxy interfaces around remote resources so they look local is a recipe for a fragile system. Plus, as the complexity of components and services increases, local systems aren’t actually as reliable as we think! Concurrency is hard, but you can’t escape it: whether you’re using threads in a single process, or multiple processes on a single machine, you still need to synchronize state between them somehow. Fault tolerance is hard, but you can’t escape it: parts will fail, you need to cope without rebooting the whole application. Correctness is hard, but you can’t escape it: whether through laborious testing or a Sufficiently Advanced Compiler, you need to have some assurance that the software will work as intended. Let’s talk about a set of architectural patterns (and, yes, frameworks) that can really help us achieve the goals of concurrency, fault tolerance and correctness, while affording us the flexibility we need to scale our deployments when we achieve terrifying success.

How To Run a 5 Whys (With Humans, Not Robots)

Dan Milstein

Spaghetti gate

Jon Bachelor

You've officially leveled-up in the world of software development with Visual Studio, and you now find yourself working on projects that are infinitely larger and far more complex than anything you've worked on before. Time to beef up your debugging skills not only to debug, but sometimes just to learn the flow of a given process! Plain old break-points have always gotten you by, but now you quickly run into trickier situations that come close to making your head explode. Come and learn some new debugging tricks & tips to bring your debugging skills to new heights.

Put Some SRE in Your Shipped Software

Theo Schlossnagle

Fuzz-testing: A hacker's approach to making your code more secure | Pascal Ze...

Codemotion

Pompili - From hero to_zero: The FatalNoise neverending story

Codemotion

Similar to Jason Yee - Chaos! - Codemotion Rome 2019

The hunt of the unicorn, to capture productivity

Brainhub

Larry Maccherone: "Probabilistic Decision Making"

RedHatAgileDay

Five Cliches of Online Game Development

iandundore

How I failed to build a runbook automation system

TimothyBonci

Hushcon 2016 Keynote: Test for Echo

Deja vu Security

Continuous Automated Testing - Cast conference workshop august 2014

Noah Sussman

Software testing (2) trainingin-mumbai

vibrantuser

Scrum Plus Extreme Programming (XP) for Hyper Productivity

Ron Quartel

Secrets and Mysteries of Automated Execution Keynote slides

Alan Richardson

Angus Fletcher - Error Handling in Concurrent Systems

Maritime DevCon

Let's Sharpen Your Agile Ax, It's Story Splitting Time

Excella

Sharpen your Agile Axe by Brian Sjorber

Washington DC Scrum User Group

Getting Schooled DerbyCon 3.0TonikJDK

Coaching teams in creative problem solving

Flowa Oy

Software testing (2) trainingin-mumbai...

vibrantuser

Chaos Engineering Talk at DevOps Days Austin

matthewbrahms

DevOps Days Vancouver 2014 Slides

Alex Cruise

How To Run a 5 Whys (With Humans, Not Robots)

Dan Milstein

Spaghetti gate

Jon Bachelor

Put Some SRE in Your Shipped Software

Theo Schlossnagle

Similar to Jason Yee - Chaos! - Codemotion Rome 2019 (20)

The hunt of the unicorn, to capture productivity

Larry Maccherone: "Probabilistic Decision Making"

Five Cliches of Online Game Development

How I failed to build a runbook automation system

Hushcon 2016 Keynote: Test for Echo

Continuous Automated Testing - Cast conference workshop august 2014

Software testing (2) trainingin-mumbai

Scrum Plus Extreme Programming (XP) for Hyper Productivity

Secrets and Mysteries of Automated Execution Keynote slides

Angus Fletcher - Error Handling in Concurrent Systems

Let's Sharpen Your Agile Ax, It's Story Splitting Time

Sharpen your Agile Axe by Brian Sjorber

Getting Schooled DerbyCon 3.0

Coaching teams in creative problem solving

Software testing (2) trainingin-mumbai...

Chaos Engineering Talk at DevOps Days Austin

DevOps Days Vancouver 2014 Slides

How To Run a 5 Whys (With Humans, Not Robots)

Spaghetti gate

Put Some SRE in Your Shipped Software

More from Codemotion

Fuzz-testing: A hacker's approach to making your code more secure | Pascal Ze...

Codemotion

Pompili - From hero to_zero: The FatalNoise neverending story

Codemotion

Pastore - Commodore 65 - La storia

Codemotion

Pennisi - Essere Richard Altwasser

Codemotion

Rivivere l'ebbrezza di progettare un vecchio computer o una consolle da bar è oggi possibile sfruttando le FPGA, ovvero logiche programmabili che consentono a chiunque di progettare il proprio hardware o di ricrearne uno del passato. In questa sessione si racconta come dal reverse engineering dell'hardware di vecchie glorie come il Commodore 64 e lo ZX Spectrum sia stato possibile farle rivivere attraverso tecnologie oggi alla portata di tutti.

Michel Schudel - Let's build a blockchain... in 40 minutes! - Codemotion Amst...

Codemotion

There's a lot of talk about blockchain, but how does the technology behind it actually work? For developers, getting some hands-on experience is the fastest way to get familiair with new technologies. So let's build a blockchain, then! In this session, we're going to build one in plain old Java, and have it working in 40 minutes. We'll cover key concepts of a blockchain: transactions, blocks, mining, proof-of-work, and reaching consensus in the blockchain network. After this session, you'll have a better understanding of core aspects of blockchain technology.

Richard Süselbeck - Building your own ride share app - Codemotion Amsterdam 2019

Codemotion

When was the last time you were truly lost? Thanks to the maps and location technology in our phones, a whole generation has now grown up in a world where getting lost is truly a thing of the past. Location technology goes far beyond maps in the palm of our hand, however. In this talk, we will explore how a ridesharing app works. How do we discover our destination?How do we find the closest driver? How do we display this information on a map? How do we find the best route?To answer these questions,we will be learning about a variety of location APIs, including Maps, Positioning, Geocoding etc.

Eward Driehuis - What we learned from 20.000 attacks - Codemotion Amsterdam 2019

Codemotion

Eward Driehuis, SecureLink's research chief, will guide you through the bumpy ride we call the cyber threat landscape. As the industry has over a decade of experience of dealing with increasingly sophisticated attacks, you might be surprised to hear more attacks slip through the cracks than ever. From analyzing 20.000 of them in 2018, backed by a quarter of a million security events and over ten trillion data points, Eward will outline why this happens, how attacks are changing, and why it doesn't matter how neatly or securely you code.

Francesco Baldassarri - Deliver Data at Scale - Codemotion Amsterdam 2019 -

Codemotion

IoT revolution is ended. Thanks to hardware improvement, building an intelligent ecosystem is easier than never before for both startups and large-scale enterprises. The real challenge is now to connect, process, store and analyze data: in the cloud, but also, at the edge. We’ll give a quick look on frameworks that aggregate dispersed devices data into a single global optimized system allowing to improve operational efficiency, to predict maintenance, to track asset in real-time, to secure cloud-connected devices and much more.

Martin Förtsch, Thomas Endres - Stereoscopic Style Transfer AI - Codemotion A...

Codemotion

What if Virtual Reality glasses could transform your environment into a three-dimensional work of art in realtime in the style of a painting from Van Gogh? One of the many interesting developments in the field of Deep Learning is the so called "Style Transfer". It describes a possibility to create a patchwork (or pastiche) from two images. While one of these images defines the the artistic style of the result picture, the other one is used for extracting the image content. A team from TNG Technology Consulting managed to build an AI showcase using OpenCV and Tensorflow to realize such goggles.

Melanie Rieback, Klaus Kursawe - Blockchain Security: Melting the "Silver Bul...

Codemotion

Blockchain (and Cryptocurrency) is an evolution of 20-year old research from scientists like Chaum, Lamport, and Castro & Liskov. Due to the current hype, it's hard to distinguish beneficial aspects of the technology from a desire for a "silver bullet" for device security, verifiable logistics, or "saving democracy". The problem: blockchain introduces new security challenges - and blind adoption without understanding reduces overall security. In this talk, Melanie Rieback and Klaus Kursawe explain the pitfalls and limits of blockchain, so you can avoid making your applications LESS secure.

Angelo van der Sijpt - How well do you know your network stack? - Codemotion ...

Codemotion

Networking is a core part of computing in the digital world we inhabit. But, how well do you know how it works? Do you understand all the moving parts of the OSI stack inside your computer, and how the network is actually put together? How can this ever work? This guided safari of layers, standards, protocols, and happenstance will bring us close to the copper wire, and up through the layers of CDMA/CD, ARP, routing and HTTP. We will make a few excursions through patchworks that still work forty years later, and cleverly designed mechanisms that show that simplicity is the only way to last.

Lars Wolff - Performance Testing for DevOps in the Cloud - Codemotion Amsterd...

Codemotion

Performance tests are not only an important instrument for understanding a system and its runtime environment. It is also essential in order to check stability and scalability – non-functional requirements that might be decisive for success. But won't my cloud hosting service scale for me as long as I can afford it? Yes, but… It only operates and scales resources. It won't automatically make your system fast, stable and scalable. This talk shows how such and comparable questions can be clarified with performance tests and how DevOps teams benefit from regular test practise.

Sascha Wolter - Conversational AI Demystified - Codemotion Amsterdam 2019

Codemotion

Sascha will demonstrate the opportunities and challenges of Conversational AI learned from the practice. Both Technology and User Experience will be covered introducing a process finding micro-moments, writing happy paths, gathering intents, designing the conversational flow, and finally publishing on almost all channels including Voice Services and Chatbots. Valuable for enterprises, developers, and designers. All live on stage in just minutes and with almost no code.

Michele Tonutti - Scaling is caring - Codemotion Amsterdam 2019

Codemotion

A key challenge we face at Pacmed is quickly calibrating and deploying our tools for clinical decision support in different hospitals, where data formats may vary greatly. Using Intensive Care Units as a case study, I’ll delve into our scalable Python pipeline, which leverages Pandas’ split-apply-combine approach to perform complex feature engineering and automatic quality checks on large time-varying data, e.g. vital signs. I’ll show how we use the resulting flexible and interpretable dataframes to quickly (re)train our models to predict mortality, discharge, and medical complications.

Pat Hermens - From 100 to 1,000+ deployments a day - Codemotion Amsterdam 2019

Codemotion

Coolblue is a proud Dutch company, with a large internal development department; one that truly takes CI/CD to heart. Empowerment through automation is at the heart of these development teams, and with more than 1000 deployments a day, we think it's working out quite well. In this session, Pat Hermens (a Development Managers) will step you through what enables us to move so quickly, which tools we use, and most importantly, the mindset that is required to enable development teams to deliver at such a rapid pace.

James Birnie - Using Many Worlds of Compute Power with Quantum - Codemotion A...

Codemotion

Quantum computers can use all of the possible pathways generated by quantum decisions to solve problems that will forever remain intractable to classical compute power. As the mega players vie for quantum supremacy and Rigetti announces its $1M "quantum advantage" prize, we live in exciting times. IBM-Q and Microsoft Q# are two ways you can learn to program quantum computers so that you're ready when the quantum revolution comes. I'll demonstrate some quantum solutions to problems that will forever be out of reach of classical, including organic chemistry and large number factorisation.

Don Goodman-Wilson - Chinese food, motor scooters, and open source developmen...

Codemotion

Chinese food exploded across America in the early 20th century, rapidly adapting to local tastes while also spreading like wildfire. How was it able to spread so fast? The GY6 is a family of scooter engines that has achieved near total ubiquity in Europe. It is reliable and cheap to manufacture, and it's made in factories across China. How are these factories able to remain afloat? Chinese-American food and the GY6 are both riveting studies in product-market fit, and both are the product of a distributed open source-like development model. What lessons can we learn for open source software?

Pieter Omvlee - The story behind Sketch - Codemotion Amsterdam 2019

Codemotion

Dave Farley - Taking Back “Software Engineering” - Codemotion Amsterdam 2019

Codemotion

Would you fly in a plane designed by a craftsman or would you prefer your aircraft to be designed by engineers? We are learning that science and empiricism works in software development, maybe now is the time to redefine what “Software Engineering” really means. Software isn't bridge-building, it is not car or aircraft development either, but then neither is Chemical Engineering. Engineering is different in different disciplines. Maybe it is time for us to begin thinking about retrieving the term "Software Engineering" maybe it is time to define what our "Engineering" discipline should be.

Joshua Hoffman - Should the CTO be Coding? - Codemotion Amsterdam 2019

Codemotion

What is the job of a CTO and how does it change as a startup grows in size and scale? As a CTO, where should you spend your focus? As an engineer aspiring to be a CTO, what skills should you pursue? In this inspiring and personal talk, I describe my journey from early Red Hat engineer to CTO at Bloomon. I will share my view on what it means to be a CTO, and ultimately answer the question: Should the CTO be coding?

More from Codemotion (20)