>When I worked at AWS, it used to take us months to change the position of a button in the UI. Things that our competitors did in hours and days, we did in months and years.
From what I understand, the culture in a large company varies from team to team. Was it your experience that all the teams were that slow?
Are you claiming the whole of AWS is that way or that since your team was that way we should disregard any advice about AWS?
If I invert all the advice from the post, would that be better as a development practice?
A large monolith, backed by an off the shelf database where there is a central security team looking after every line of code?
It's a company-wide issue, and it can be observed from the outside too. Existing products improve at a rate that is significantly slower than competitors (with a few exceptions). And I'm not referring to feature creep, but fixing obvious gaps and issues that the company would have been aware of for years (or more than a decade in some cases).
From what I understand, the culture in a large company varies from team to team. Was it your experience that all the teams were that slow?
Are you claiming the whole of AWS is that way or that since your team was that way we should disregard any advice about AWS?
If I invert all the advice from the post, would that be better as a development practice? A large monolith, backed by an off the shelf database where there is a central security team looking after every line of code?