It's just the author acknowledging all the code written belongs to some company or organization, and often, can't even be used as a showcase. It was work for mo

It's just the author acknowledging all the code written belongs to some company or organization, and often, can't even be used as a showcase. It was work for money, plain and simple, but may become a hard sell later. However, it's not necessarily true. Working with large codebases, working on language design questions, committees, everything grows experience that can be used later. It's just not clear now how, as requirements and work in other companies or in FOSS may be very different than that C++ development. The author mentions Go as a positive experience. If the ego could be left at the door, Go could be a good language to make a new home in. Either that or Haskell, though with much more investment in all layers. The language and tooling can have very much to say for overall development and maintenance. Also architecture and design matters, as well as changing requirements. It's all very simple or complicated, depending on unknowable X-factors that often need to be decided up-front.