You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
1""a while" (weeks?)" I updated the questionSergey Zolotarev– Sergey Zolotarev2025-12-01 04:33:52 +00:00Commented 6 hours ago
-
3"without error-prone steps" - does this answer come from the perspective of a developer at all? or is this mainly from the perspective of a non techie / business managementreign– reign2025-12-01 07:38:09 +00:00Commented 3 hours ago
-
1I think devs struggling with demands of people that do not do the actual work (but have stakes in it) could benefit from answers that do not come from the "but i am paying you" mindset, instead a "these are your options" one. it isn't necessarily that answers on this topic should only stem from actual "code monkeys" that share the burden of having to keep a business running through hard work.however, it's more likely that devs will give useful instead of accusatory answers. an example of a useful answer is the one from Stevereign– reign2025-12-01 07:51:08 +00:00Commented 2 hours ago
-
An hour ago is a pretty different situation, thanks for updating @SergeyZolotarevAdam Burke– Adam Burke2025-12-01 08:29:17 +00:00Commented 2 hours ago
-
Infrequent releases with long QA cycles often go together with error-prone deployments with manual steps, where support teams and management demand on-call support. This is what I was gesturing towards @reign. Have been on both sides of that situation.Adam Burke– Adam Burke2025-12-01 08:31:41 +00:00Commented 2 hours ago
|
Show 2 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. software-industry), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you