You are viewing content from a past/completed conference.
  
    
  
  
        
    
  
    
      
  
Unconference: Languages of Infra: Beyond YAML
    
  
    
      
	
	
	
	
	
		
		
	
	
		
			
				
					
					                    Abstract
					
						What is an unconference?
An unconference is a participant-driven meeting. Attendees come together, bringing their challenges and relying on the experience and know-how of their peers for solutions. A professional facilitator is also there to help keep the discussion moving forward, but where it goes is up to the participants.
It's a facilitated peer group that avoids the hierarchical aspects of a conventional conference, such as a top-down organization. Only the broad themes are predetermined. Everything else is just space for attendees to sound off ideas together, relate to shared challenges and rewards, and identify new ideas and goals. 
Our unconference sessions have been based on the Open Space Technology and Lean Coffee format since 2006.
Why are we doing unconference sessions?
We have designed QCon for senior software practitioners. That role comes with demanding challenges and complex problems. 
Connecting with your peers in a structured environment allows you to:
- Broaden your perspective with the benefit of the experience of others.
- Challenge how you've been doing things by breaking out of your bubble.
- Learn from peers who have already overcome the challenges you're facing now.
- Benchmark your solutions against other teams and organizations.
- Get real-world perspectives on challenges that might be too novel or specific to find solutions in books or presentations.
- Validate your technical roadmap with real-world research.
- Connect with others like you and build relationships that go beyond the event.
 
					
						
					
					
					
										
					
				 
				
					
					
					
						
				
			 
		 
	
			
			
				From the same track
				
					
    
        Session
        Infrastructure as Code
        What if Infrastructure as Code Never Existed?
        Monday Oct 2 / 01:35PM PDT
        
            
            We rewind the clock and ask ourselves: what if Infrastructure as Code never existed? What different solutions might we have come up with to the problems we faced? We’ll leave you full of possibilities about the future.
      
        
        	
		 
		
			Adam Jacob
			CEO @System Initiative, CTO @Chef; Systems Administrator who loves building products 
		 
	 
 
        What if Infrastructure as Code Never Existed?
     
 
    
        Session
        Cloud Engineering
        Pulumi Adventures: How Python Empowered My Infrastructure Beyond YAML
        Monday Oct 2 / 10:35AM PDT
        
            
            In recent times and as technology keeps evolving, the boundary between software engineering and DevOps continues to blur, presenting unique challenges and opportunities for software engineers.
      
        
        	
		 
		
			Adora Nwodo
			Community Engineer
		 
	 
 
        Pulumi Adventures: How Python Empowered My Infrastructure Beyond YAML
     
 
    
        Session
        CI/CD
        CI/CD Beyond YAML
        Monday Oct 2 / 03:55PM PDT
        
            
            This session explores the evolution of infrastructure strategy, focusing on the shift from traditional YAML configurations to pipelines-as-code.
      
        
        	
		 
		
			Conor Barber
			Senior Software Engineer, Infrastructure @Airbyte, Over a Decade of Experience in Data and Infrastructure Engineering, Previously @Apple
		 
	 
 
        CI/CD Beyond YAML
     
 
    
        Session
        Kubernetes
        Kubernetes without YAML
        Monday Oct 2 / 05:05PM PDT
        
            
            Kubernetes ONLY understands JSON, yet we all write a ton of YAML. This is because it's meant to be easier for us to write ... but writing our manifests in YAML can be complex, error-prone, and damn right opaque as we adopt more custom resources.
      
        
        	
		 
		
			David Flanagan
			Kubernetes Whisperer
		 
	 
 
        Kubernetes without YAML