You memorize, regurgitate and participate in the agile masquerade. Creativity is shunned. Tried architectures/patterns are what is expected. I feel like there

You memorize, regurgitate and participate in the agile masquerade. Creativity is shunned. Tried architectures/patterns are what is expected. I feel like there is plenty of room for creativity in the high level solution and working with the customer/user. But it makes sense that when you get down to the nitty gritty, established patterns should be used. Without a doubt other engineers will come after you to work on the code, and the last thing they want to see is a super creative implementation that only you understand. You might see a similar thing in architecture. A bridge architect might draw up a beautiful, flowing bridge...but at the end of the day the engineers will use the same techniques to make it structurally sound. So...maybe you might like software architecture more?