I think this is where a lot of varied work experience (small / large / old / new companies) is key, because it gives you perspective. You can then ask yourself, "why does this process suck so much, and why didn't it when I worked at X? In my experience, people who come from a monoculture background usually seem to not question dubious software, architecture and methodology choices that end up killing productivity and sanity.
Yeah. If you're going to use languages, methodologies, and architectures without understanding, and without evaluating them for how well they fit your situation, many things will be painful. Don't follow the fads, whether methodologies (Agile), architecture (microservices), languages, or frameworks. Use what's appropriate for what you need to do.
