He worked with him closely, then stepped away and came back. Multiple times. By telling the story of this, he lets readers know that he wasn't always by his side and that he left to try other things but circled back at different junctures in his life and in Steve's.
Knowing Glenn and his successes and failures and talking with him over many a margarita at Compadres (after long bouts of writing NeXTSTEP code with him), the story brought strong memories and a very clear voice of different periods and circumstances across several years. He shows an arc of ups and downs in both careers and a lot of hard work and sweat that often didn't get notice until many years later if at all.
Rereading the story, I don't get boastful at all. I get much appreciation for being able to be on a pretty cool ride and being able to create some great products. There's also disappointment in some hard work that didn't pay off. But above all appreciation for someone who continually rolled up his sleeves to get in the ring, take chances, and build something... or in this case tell a damn good story.
"Steve would draw a quick vision on the whiteboard, we'd go work on it for a while, bring it back, find out the ways in which it sucked, and we'd iterate, again and again and again. "
Half joking aside, it would have been nice if the author would have spent more than 1/5th of the article actually talking about what he claimed he was going to give insight on. Instead the author spent most of the article tooting his own horn, which is fine, if that's what the title had indicated to expect.