cdCon 2022

Critical infrastructure products like Spinnaker form the basis of many technology strategies, increasing the velocity of innovation while reducing the risk of outages. Failure of these systems erodes trust, limiting a team’s ability to delegate responsibility. When deploys fail due to operational constraints or bugs in the platform, it becomes difficult for teams to reliably deploy, encouraging alternative solutions that detract from delivering business value. Much like software infrastructure, failure in more traditional domains is no less worrisome. For example, without trust in a system of laws, it’s difficult to facilitate basic interactions between parties. In this session, we’ll explore the relationship between critical infrastructure across domains and propose a set of strategies for building resilient CD platforms that prioritize trust over building features.

Jump into this fast-moving and practical discussion to dig into how you and your peers can use a single mainline of source code to manage continuous delivery with greater agility and higher quality.

Assembling a jigsaw puzzle is a combination of science and art. There is a method to sorting the pieces, assembling the frame, and completing sections in a logical progression. Much like staring at a pile of 500 unsorted cardboard puzzle pieces, the blank page can be overwhelming when trying to write technical documentation. Where do you start? What should you focus on? What do your readers even need to know? Documenting your work is an essential part of the development lifecycle, but if you don’t write regularly as part of your job, it can feel daunting. Luckily, there are established methodologies you can lean on whether you’re trying to make sense of your puzzle pieces or write down how your code works. This talk will explore what Ember has learned from assembling countless jigsaw puzzles over the years and how it applies to writing technical documentation.

Continuous Delivery defines activities in a workflow. Known tools like Jenkins support those workflows and make the DevOps life easier. A process engine can automate workflows too. Join me for my little experiment and find out what I learned when using a workflow engine to automate a CI/CD workflow.

Today’s software development relies more than ever on (third) dependencies. Even though solutions exist to help maintain them, yet, we see many of them being outdated. Why do so many teams struggle with that practice?

Let’s see that together.

The GraphQL Foundation's inaugural GraphQL Conf will be co-located with OpenJS World and cdCon. This collaborator summit-style event will be an opportunity for core GraphQL spec and implementation developers to meet in-person, discuss recent work, and plan for the future. All attendees of OpenJS World and cdCon are welcome.
Talks are expected to include:

• Recent activity in the GraphQL specification working group, such as Defer and Stream, Input Unions, and Client-Controlled Nullability.
• Downstream implementations of GraphQL
• Security considerations
• Common practices and lessons learned

To learn more, click here.

How to Register: Pre-registration is not required; however, if you plan to participate please add GraphQL Conf to your existing cdCon registration.