> But on the other hand, when you think about it, once the main architecture is put down and the main issues are solved, most software engineering jobs are just

> But on the other hand, when you think about it, once the main architecture is put down and the main issues are solved, most software engineering jobs are just repeating the same trick over and over again, copy / paste / edit some names, done. I don't know. I think it gets less and less true as you get away from web development. The fundamentals stay the same but how they intersect with what you are doing can vary widely. If you want to, you can encounter domain knowledge intersecting with the problems you are trying to solve, different architectures for complexe systems coming with their own set of constraints, different project structures, different ways to deal with end users requirements. I think they are plenty of opportunities to do boring things and plenty to do interesting things.