73 lines
		
	
	
	
		
			2.6 KiB
		
	
	
	
		
			YAML
		
	
	
	
	
	
		
		
			
		
	
	
			73 lines
		
	
	
	
		
			2.6 KiB
		
	
	
	
		
			YAML
		
	
	
	
	
	
|  | uuid:
 | ||
|  |   - value: 19376fcb-fc7a-4b4a-9fea-6865e423519e
 | ||
|  | langcode:
 | ||
|  |   - value: en
 | ||
|  | type:
 | ||
|  |   - target_id: daily_email
 | ||
|  |     target_type: node_type
 | ||
|  |     target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
 | ||
|  | revision_timestamp:
 | ||
|  |   - value: '2025-05-11T09:00:24+00:00'
 | ||
|  | revision_uid:
 | ||
|  |   - target_type: user
 | ||
|  |     target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
 | ||
|  | revision_log: {  }
 | ||
|  | status:
 | ||
|  |   - value: true
 | ||
|  | uid:
 | ||
|  |   - target_type: user
 | ||
|  |     target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
 | ||
|  | title:
 | ||
|  |   - value: 'Flexible Mob and Pair Programming'
 | ||
|  | created:
 | ||
|  |   - value: '2024-01-02T00:00:00+00:00'
 | ||
|  | changed:
 | ||
|  |   - value: '2025-05-11T09:00:24+00:00'
 | ||
|  | promote:
 | ||
|  |   - value: false
 | ||
|  | sticky:
 | ||
|  |   - value: false
 | ||
|  | default_langcode:
 | ||
|  |   - value: true
 | ||
|  | revision_translation_affected:
 | ||
|  |   - value: true
 | ||
|  | path:
 | ||
|  |   - alias: /daily/2024/01/02/flexible-pair-programming
 | ||
|  |     langcode: en
 | ||
|  | body:
 | ||
|  |   - value: |
 | ||
|  |       <p>Doing pair or programming doesn't mean you need to be working in groups continuously.</p>
 | ||
|  | 
 | ||
|  |       <p>If you've asked a colleague to review the code you're writing or help you fix a bug, that's pair programming.</p>
 | ||
|  | 
 | ||
|  |       <p>You don't always need a driver and navigator, a set rotation time or dedicated allocated daily pair programming time.</p>
 | ||
|  | 
 | ||
|  |       <p>While that works for some teams, and on some occasions, you can do what's needed or feels right at the time to complete the task at hand.</p>
 | ||
|  | 
 | ||
|  |       <p>If you need a short pair programming session to fix a bug or finish a feature, to review some code before you merge it or submit it for code review, or want to pair ad-hoc or for one afternoon a week, that works, too.</p>
 | ||
|  | 
 | ||
|  |       <p>There isn't one way to do pair or mob programming.</p>
 | ||
|  | 
 | ||
|  |       <p>Do what works for you.</p>
 | ||
|  | 
 | ||
|  |               
 | ||
|  |     format: full_html
 | ||
|  |     processed: |
 | ||
|  |       <p>Doing pair or programming doesn't mean you need to be working in groups continuously.</p>
 | ||
|  | 
 | ||
|  |       <p>If you've asked a colleague to review the code you're writing or help you fix a bug, that's pair programming.</p>
 | ||
|  | 
 | ||
|  |       <p>You don't always need a driver and navigator, a set rotation time or dedicated allocated daily pair programming time.</p>
 | ||
|  | 
 | ||
|  |       <p>While that works for some teams, and on some occasions, you can do what's needed or feels right at the time to complete the task at hand.</p>
 | ||
|  | 
 | ||
|  |       <p>If you need a short pair programming session to fix a bug or finish a feature, to review some code before you merge it or submit it for code review, or want to pair ad-hoc or for one afternoon a week, that works, too.</p>
 | ||
|  | 
 | ||
|  |       <p>There isn't one way to do pair or mob programming.</p>
 | ||
|  | 
 | ||
|  |       <p>Do what works for you.</p>
 | ||
|  | 
 | ||
|  |               
 | ||
|  |     summary: null
 | ||
|  | field_daily_email_cta: {  }
 |