Trajectory After Liftoff

LaunchDarkly
By Kim Harrison   •   April 10, 2019
LaunchDarkly

This week we hosted our first conference, Trajectory. Many thanks to everyone who helped make it an amazing day! We are so grateful to our speakers and sponsors for bringing amazing conversations to Oakland. We spent the day sharing, discussing, and learning how different teams test in production, utilize progressive delivery methods, gain observability, experiment, continuously deliver, and incorporate chaos engineering into their dev cycles, among other things.

The two-day event kicked off with a half-day technical training session that focused on LaunchDarkly. Our intent for Trajectory wasn't to focus specifically on feature flagging, or even our own platform. Trajectory isn't a user conference. Our vision for Trajectory is to be a space for conversation around better development and release practices. Inspired by Gremlin's ChaosConf and Honeycomb's o11ycon, we wanted to bring together some of the leading teams currently using modern development practices and give them a platform to share learnings and strategies. That said, we know LaunchDarkly users are always happy for best practices so we also offered a focused training session before the main full day event.

If you were able to join us, we want to thank you for making the day so amazing! Being our first year, it took a lot to build the Trajectory brand, and we're so grateful to everyone for your support. If you missed it, don't worry, we recorded the talks! Check back in a few weeks for those videos. In the meantime, here are some of the highlights.

Keynotes and Breakfast Burritos

As promised we started the main, full-day conference with breakfast burritos (chorizo, vegetarian, or vegan—this is Oakland after-all!) Our keynote speakers, Adrian Cockcroft, VP of Cloud Architecture Strategy at AWS, and Cindy Alvarez, Principal PM Manager at Microsoft, started the day with talks on how to effect change within organizations. Adrian focused on the metrics of innovation, or how to measure the effectiveness of your efforts. And Cindy discussed how to create a healthy culture of curiosity that supports innovative intent.

Someone at #TrajectoryConf just asked @adrianco about small, continuous delivery for critical systems like Boeing (alluding to 737max). He didn't mention it, but the biggest blocker in "critical systems" isn't resistance to fast iteration, it's to transparency.— Jason Yee (@gitbisect) April 9, 2019
@cindyalvarez mentioned at #TrajectoryConf that her teams send "two things you're still worried about" emails each Friday. What a great way to encourage happy teams that address small (or big!) hangups quickly and democratically so they can focus on progress.— Cameron Savage (@CameronSavage) April 9, 2019

Next we saw Sr Dev Manager at IBM, Michael McKay, share 'Learning to Do Deployments At Scale in 6 Easy Steps.' He showed us how the IBM Kubernetes Service builds and deploys micro-services to Kubernetes clusters around the world.

. @McKayMckaymic talking IBM Kunernetes scale w 100,000 deployments #trajectoryconf pic.twitter.com/oH8T6dMMuu— Edith Harbaugh (@edith_h) April 9, 2019

Breakout Talks: Gotta Catch 'Em All

Talks were divided into two main tracks–future vision and best practices. In the best practices track Josh Willis (Slack), Arjan Franzen (Maxeda DIY), Emily Voigtlander (Seesaw), and Vijay Ramesh (Demandbase) shared how they use feature flags within their architecture, became data-driven, enable teams across their organizations to use feature flags, and feature flag machine learning architectures.

Interesting uses for flags by legal and sales presented by @evoigtlander at seesaw. #TrajectoryConf— David Lawrence Evans (@owlmonkey) April 9, 2019

"...and how do I feature flag changing the feature flag engine?" - @josh_willstype questions at #TrajectoryConf— Cameron Savage (@CameronSavage) April 9, 2019

Vijay Ramesh: Analyze feature importance by adding and removing features #trajectoryconf pic.twitter.com/QbliiGiAe4— Cindy (@_cindyylinn_) April 9, 2019

#TrajectoryCon @ArjanFranzen: Culture change: Be oriented to the company and the team. Embrace feature management, continuous delivery, experimentation, and require that all features prove their effective and useful.— Heidi at #DevOneLinz (@wiredferret) April 9, 2019

And in the future vision track Emma Humphries (Mozilla), Ramin Keene (Fuzzbox), Jason Yee (DataDog), and Ellie Day (Atlassian) talked about the culture of experimentation, techniques that support effective experimentation, the value in running chaos experiments, and thinking about ways to reduce friction when adding/maintaining/analyzing flags in a codebase.

“Do you involve and empower your designers with feature flag access and experiments?”, asks @heyellieday #TrajectoryConf— David Lawrence Evans (@owlmonkey) April 9, 2019

@triagegirl “voting is a rotten way to prioritize features” #TrajectoryConf @LaunchDarkly @thenewstack pic.twitter.com/x47FRtLgQT— TC Currie (@TCCurrie) April 9, 2019

Experiments aren't isolated, they are part of a program.Thinking about how requests move through your systems as a way to organize and orchestrate experiments. @rmn #trajectoryconf— Emma (@triagegirl) April 9, 2019

The advantage of cloud is being able to easily spin up new instances. But it is NOT a guarantee against failure. @gitbisect #TrajectoryConf— Dawn Parzych (@dparzych) April 9, 2019

Panel Discussion

The day wrapped up with a panel discussion that focused on the new tools and trends in application and service delivery. The panel included Preeti Somal VP of Engineering at HashiCorp, Kolton Andrus, CEO & Co-Founder of Gremlin, and Rachel Stephens, Analyst at RedMonk.

A3: @rstephensme Locus of control of " I can build really cool stuff"iot can have a large outcome in terms of cultural buy-in, teams enthusiasm to pursue a project, and what you ultimately end up building. #TrajectoryConf— Dawn Parzych (@dparzych) April 9, 2019

A2: @psomal Ecosystem looks at security and consistent workflow. Building the ecosystem and partnerships to reduce strain on customers figuring out what solutions work together. #TrajectoryConf— Dawn Parzych (@dparzych) April 9, 2019

"Engineers want to do the right thing, but you have to make it easy to do the right thing" - @KoltonAndrus at #TrajectoryConf— Cameron Savage (@CameronSavage) April 9, 2019

What Comes Next?

It's official, Trajectory is here to stay. We even have our first fan art:

Hosting our first conference is a huge milestone! We believe when teams aren't inhibited by the fear of breaking things, they can collaborate more effectively, get feedback sooner, validate their ideas and have control over the software they're putting into the world. And the fact that a strong lineup of prominent personalities in the software development space were willing to come and talk about how they do that within their teams, really reinforces that.

As mentioned above, we recorded these talks and hope to have them on the LaunchDarkly in a couple weeks. You can sign up here to be notified when the talks are ready, or if you want to be the first to hear when we've announced the date for Trajectory 2020.

You May Like
BEST PRACTICESWhat Is Continuous Testing? A Straightforward Introduction
BEST PRACTICESTesting in Production to Stay Safe and Sensible
AUGUST 3, 2021   •   Team & NewsCatch the New Wave
JULY 29, 2021   •   POPULARMy Experience as a Career Switcher in Tech
JULY 27, 2021   •   INDUSTRY INSIGHTSNot an Engineer? Find Out Where You Belong
JULY 22, 2021   •   INDUSTRY INSIGHTSA Day in the Life of a Technical Writer