73 lines
3.4 KiB
YAML
73 lines
3.4 KiB
YAML
uuid:
|
|
- value: c765b1bf-87ee-4324-843a-8ca578ef2f69
|
|
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:28+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: |
|
|
Work in small batches
|
|
created:
|
|
- value: '2023-11-11T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:28+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2023/11/11/work-in-small-batches
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>Software should be designed, written, and deployed in small batches.</p>
|
|
|
|
<p>This is the first line from a blog post by Eric Ries and is something that gets discussed with a guest in an upcoming episode of the Beyond Blocks podcast.</p>
|
|
|
|
<p>In the post, Eric continues by saying, "Of all of the insights I've contributed to the companies I've worked at over the years, the one I am most proud of is the importance of working in small batches".</p>
|
|
|
|
<p>Small batches mean faster feedback, more localised problems as there are fewer changes, and reduced risk and overhead.</p>
|
|
|
|
<p>If you work in small batches and make smaller changes, merge them regularly into the mainline branch (ideally, at least once a day), and often deploy changes to production, the releases will be quicker and less stressful, and clients and customers will be happy as their changes will be available sooner.</p>
|
|
|
|
<p>I've worked this way, and with long-lived feature branches and large, infrequent deployments, I prefer to work in small batches and deploy often.</p>
|
|
|
|
<p>The full blog post is found at <a href="http://www.startuplessonslearned.com/2009/02/work-in-small-batches.html">http://www.startuplessonslearned.com/2009/02/work-in-small-batches.html</a>.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>Software should be designed, written, and deployed in small batches.</p>
|
|
|
|
<p>This is the first line from a blog post by Eric Ries and is something that gets discussed with a guest in an upcoming episode of the Beyond Blocks podcast.</p>
|
|
|
|
<p>In the post, Eric continues by saying, "Of all of the insights I've contributed to the companies I've worked at over the years, the one I am most proud of is the importance of working in small batches".</p>
|
|
|
|
<p>Small batches mean faster feedback, more localised problems as there are fewer changes, and reduced risk and overhead.</p>
|
|
|
|
<p>If you work in small batches and make smaller changes, merge them regularly into the mainline branch (ideally, at least once a day), and often deploy changes to production, the releases will be quicker and less stressful, and clients and customers will be happy as their changes will be available sooner.</p>
|
|
|
|
<p>I've worked this way, and with long-lived feature branches and large, infrequent deployments, I prefer to work in small batches and deploy often.</p>
|
|
|
|
<p>The full blog post is found at <a href="http://www.startuplessonslearned.com/2009/02/work-in-small-batches.html">http://www.startuplessonslearned.com/2009/02/work-in-small-batches.html</a>.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|