The article raises some interesting issues. I've solo written my fair share of prototype or rush-to-market code that tens of millions of dollars of revenue became dependent upon and then had to deal with criticism over how I wrote it years later from guys who really wouldn't have gotten hired if I hadn't hacked the hell out of things in the first place to close the deal and get the money flowing.

That said, when I look across the spectrum of developer types from those who feel too much ownership of their code vs. those who take no ownership of their code -- I find the latter to be more common.

These days, when I'm advising junior developers on how to make their mark while getting better at their craft; I lean more toward stressing their need to take ownership of the code they write and the projects they work on.

I'd agree more with another poster in this thread, agentultra, who stressed learning to accept criticism -- rather than this article's seeming recommendation of avoiding association with your own work.