Well, yes, we are overcomplicating it. Except on the parts we are undercomplicating... And I still couldn't find anybody that can reliably tell those apart, but the first set is indeed much larger.
1 - Do not pick a new language for an urgent project. Do look at them when you have some leeway.
2 - Yep.
3 - There's something wrong with your ops. That happens often, and it is a bug, fix it.
4 - If CI is making your ops more complex, ditch it. If less complex, keep it. In doubt, choose the safest possible way to try the other approach, and look at the results.
5 - Do not listen to consulting experts, only to technical experts. The agile manifesto is a nice reading, read it, think about it, try to follow, but don't try too hard. Ignore any of the more detailed methodologies.
1 - Do not pick a new language for an urgent project. Do look at them when you have some leeway.
2 - Yep.
3 - There's something wrong with your ops. That happens often, and it is a bug, fix it.
4 - If CI is making your ops more complex, ditch it. If less complex, keep it. In doubt, choose the safest possible way to try the other approach, and look at the results.
5 - Do not listen to consulting experts, only to technical experts. The agile manifesto is a nice reading, read it, think about it, try to follow, but don't try too hard. Ignore any of the more detailed methodologies.