My server's first baby steps.
So, whose tactical message server has been coded in three weeks and is now successfully accepting, constructing, translating, passing, receiving, redistributing, parsing, and returning messages through an embedded system, all while the creator has had near zero prior experience with windows networking, C++ bit manipulation, embedded systems, or the military standard used for the message definitions? That would be my server, thank you very much.
After some 60 hours of unpaid overtime and headaches like I haven't had in years, my pride and joy bounced its first TacMessages between two handheld devices tonight. This pretty much signals the end of the crunch for me. There is some cleanup to do, and a lot of room for improvement, but it does what it needs to do by the time it needed to do it. I made it across the finish line and the baton has been passed to the next runners.
I also want to note that I sent out a celebratory email to my team notifying them of the server status. I had the chance to snatch more glory for my accomplishment by copying my manager's bosses, who have a vested interest in this project, but I chose not to go over his head. He hasn't done anything in particular to alleviate my irritation at him, but I've had some time to cool my nerves and we should have a chance to discuss this before I start the political games. I sent him a separate email telling him I thought his bosses would be interested in our progress, and that he could demo it to them if he felt it was significant enough to show. He has a chance to look good to his bosses by breaking the news, we both have a chance to look good to his bosses by demonstrating the capability (I wrote it and I doubt he can demonstrate and explain it without me), and I show him that I'm paying special attention to his interests and it would be best if he gave me the leeway I want to do my work.
I was once told that a person's success is often more about how good they make their boss look than how well they did their job. I went that extra length for my last manager so that he could shine in the eyes of his peers and superiors, and in return he looked out for my career. I have yet to conclude whether my current manager can understand the give and receive nature of his position.
Sleepy time,
LateNightCoder
After some 60 hours of unpaid overtime and headaches like I haven't had in years, my pride and joy bounced its first TacMessages between two handheld devices tonight. This pretty much signals the end of the crunch for me. There is some cleanup to do, and a lot of room for improvement, but it does what it needs to do by the time it needed to do it. I made it across the finish line and the baton has been passed to the next runners.
I also want to note that I sent out a celebratory email to my team notifying them of the server status. I had the chance to snatch more glory for my accomplishment by copying my manager's bosses, who have a vested interest in this project, but I chose not to go over his head. He hasn't done anything in particular to alleviate my irritation at him, but I've had some time to cool my nerves and we should have a chance to discuss this before I start the political games. I sent him a separate email telling him I thought his bosses would be interested in our progress, and that he could demo it to them if he felt it was significant enough to show. He has a chance to look good to his bosses by breaking the news, we both have a chance to look good to his bosses by demonstrating the capability (I wrote it and I doubt he can demonstrate and explain it without me), and I show him that I'm paying special attention to his interests and it would be best if he gave me the leeway I want to do my work.
I was once told that a person's success is often more about how good they make their boss look than how well they did their job. I went that extra length for my last manager so that he could shine in the eyes of his peers and superiors, and in return he looked out for my career. I have yet to conclude whether my current manager can understand the give and receive nature of his position.
Sleepy time,
LateNightCoder