Welcome to the wonderful world of system architecture! This is what it feels like to design complex sociotechnical systems. You know, how it should be done by theory and practice. You tell good people and they understand and agree. But then life happens and someone decides to prioritize their epolets and the funding source turns finicky and there you go.
But I disagree with the lack of accomplishment. Effectively, when moving up in the abstraction levels from code, reaction times get longer and risks higher. Let me tell you, the feeling when you see a team click together and finally raise to the occasion, is no less satisfying, than seeing code work. Even more so. But it takes frickin _years_ and happens much more rarely. I’m currently at a stage where a project I started on almost four years ago, is starting to deliver. And we are talking about a significant improvement on a national level. It feels good, man. It really does.
Oh, and with a manager, there’s the occasional pat on the back when goals are met on the timely basis. But nobody remembers the architect, if they have done their job properly. Thus is the nature of the beast.
But I disagree with the lack of accomplishment. Effectively, when moving up in the abstraction levels from code, reaction times get longer and risks higher. Let me tell you, the feeling when you see a team click together and finally raise to the occasion, is no less satisfying, than seeing code work. Even more so. But it takes frickin _years_ and happens much more rarely. I’m currently at a stage where a project I started on almost four years ago, is starting to deliver. And we are talking about a significant improvement on a national level. It feels good, man. It really does.
Oh, and with a manager, there’s the occasional pat on the back when goals are met on the timely basis. But nobody remembers the architect, if they have done their job properly. Thus is the nature of the beast.