Is the "most experienced programmer" also the hardest working hero in the group?
Is the "most experienced programmer" working at a sustainable pace for your company, including themselves and others (including Rob)?
Have you truly identified 1) is Rob really pushing buggy or sloppy code, and 2) is his intention really so someone else can "clean it up"? Perhaps Rob is spitballing and trying stuff and trying to contribute to the greater collective of the "correct" code. Does your process support this kind of exploration?
Has Rob worked with any other team members? Do they have the same feeling?
Could it be that your "most experienced programmer" is also an *hole control freak, and you are seeing the "most experienced programmer" with rose tinted glasses? What happens to the team if you remove the "most experienced programmer", do the rest of the team thrive or at least sustain?