That happens when you think you don’t need experienced software devs any more, because the AI can do everything now. A seasoned developer/devOp/admin would have known that the production environment needs to have different credentials from staging and these need to be protected. If that is not possible with railway then it’s simply not a good product to use and (again) a good dev/admin would have seen this in the initial evaluation phase. Not preventing AI access to the production environment from the start is the third grave mistake. However, there’s none of it in the “lessons learned” section of the article. You have learned nothing and are bound to repeat your mistakes.
That happens when you think you don’t need experienced software devs any more, because the AI can do everything now. A seasoned developer/devOp/admin would have known that the production environment needs to have different credentials from staging and these need to be protected. If that is not possible with railway then it’s simply not a good product to use and (again) a good dev/admin would have seen this in the initial evaluation phase. Not preventing AI access to the production environment from the start is the third grave mistake. However, there’s none of it in the “lessons learned” section of the article. You have learned nothing and are bound to repeat your mistakes.