Is there a moment when there is no room for error?

Question

Programming

Hello everyone
, the pros are stupid, but for me, as a novice programmer, it is interesting.
Is there a moment when a programmer has no right to make a mistake? Let's say you need to write code that will work perfectly the first time after writing.
Have you ever been in such a situation, if yes, tell us how it was

Answer 1

There is no such thing that works immediately after writing.
The program is not written the first time at all. You write a piece, run it, see if what you wrote works. You write more.
You add unit tests, you debug.
You give the finished result after testing and debugging.
And the first time - what does it mean there is no room for error? It is because of the existence of the human error factor that entire SDLC institutions have been created, including the science of testing, code review, and so on.
There is always room for error. The only question is the cost of the mistake.

Answer 2

There is no right to make a mistake when without a backup you climb into the site's production database and with the words "Yes, I just correct the line" destroy the database

Answer 3

At the interview.

Answer 4

If the workflow is correctly built, then it does not happen.
You develop in your branch in the repository, and cover with tests. And a successful commit to the production branch is possible only after the autotest stage. If the autotest fails, none of this drama does. Just edit the code and iterate. As a result, already tested code gets into the production branch.
Such a situation can only arise during an interview in order to impress interviewers ...