Wikimedia Release Engineering Team: Difference between revisions
Content deleted Content added
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
}}</onlyinclude> |
}}</onlyinclude> |
||
<table style="background: #f8f9fa;"> |
<table style="background: #f8f9fa; border: 1px solid #eaecf0; color: #222;"> |
||
<tr> |
<tr> |
||
<td style="vertical-align: top; padding: 0 |
<td style="vertical-align: top; padding: 0 0 0 1em; font-size: 1.3em;"> |
||
🚀 |
🚀 |
||
</td> |
</td> |
||
<td style="padding: 0 1.8em;"> |
|||
<td> |
|||
The most important problem that we face as software professionals is this: If somebody thinks of a good idea, how do we deliver it to users as quickly as possible? |
The most important problem that we face as software professionals is this: '''If somebody thinks of a good idea, how do we deliver it to users as quickly as possible?''' |
||
– Jez Humble and David Farley, [https://martinfowler.com/books/continuousDelivery.html Continuous Delivery] |
– Jez Humble and David Farley, [https://martinfowler.com/books/continuousDelivery.html Continuous Delivery] |
||
Revision as of 19:06, 21 September 2022
|
Release Engineering
Enable confident code deployment with feedback loops to inform optimal delivery to production.
|
|
🚀 |
The most important problem that we face as software professionals is this: If somebody thinks of a good idea, how do we deliver it to users as quickly as possible? – Jez Humble and David Farley, Continuous Delivery |