The difference is this: some people use "I'm just working for the money" as an excuse for apathy and doing just enough not to be fired. It doesn't have to be that way, if you reframe your personal mission to do as well as you can at the things that are within your control you'll likely find that the quality of your work and job satisfaction goes up.
If I kept my satisfaction based on my employer's goals I'd still be making 1/10 of what I make today working on a system that is just now getting upgraded to Java 7 and would know nothing about anything else.
The simple truth is that for every greenfield project we get in life, there's probably 30 brownfield projects. A lot of big enterprise developers may never once see a greenfield project. I sure didn't when I was on a product team.
If you want new you may find agency life fun. The downside is that if you love building new and are proud to watch things evolve gracefully you'll feel frustrated that you never get time to 'finish' the code. Also it's fucking chaos 24/7. I loved it. It will destroy you if you can't manage the always under the gun feeling though.
this is one of the pieces of life advice from stoic philosphy.
(i just finished reading A Guide to the Good Life: The Ancient Art of Stoic Joy by William B. Irvine, and recommend it)
I've reached that stage at 23, after about a year into my first job. Since then, I've been working for the money.