Wow - good stuff, and keep up the good fight.<p>I don&#x27;t have that many people around me that are worth influencing directly, so here is the way that I do it :<p>1) I divide up the TODO list and customer requirements into the &#x27;Little Things&#x27; and the &#x27;Big Things&#x27;.<p>2) Customers &#x2F; Managers &#x2F; Users seem to love the &#x27;Little Things&#x27;, and feel like they are getting great value for their dollar when so many of the &#x27;Little Things&#x27; can be delivered in a relatively short time, it looks like great progress to them.<p>3) I always do the &#x27;Little Things&#x27; at the Customer&#x27;s site, in the Customer&#x27;s presence. I always do them during the day, and I get the managers involved as much as possible. Be a good corporate citizen, and get paid on time.<p>4) Doing lots of little things on an hourly rate is a good way to generate cash quickly, and get paid on time.  Its useless in the grand scheme of things in terms of software development, but it is needed to keep everyone happy and ensure that you can pay the bills on time. As you can see, this is all about cash, fast cash, and smiles and happy customers all around.  It can be borderline degrading at times, but there you go. Milestones and Invoices and Smiles, and more Smiles and Cash.<p>5) I don&#x27;t even bother trying to explain the &#x27;Big Things&#x27; to these same Customers &#x2F; Managers &#x2F; Users, because it just plain scares them. They will never believe that software can ever be that complicated or difficult. It really scares them in fact. They want their world to be manageable, understandable, easy to estimate, easy to achieve ... that want to feel like they are 100% on top of things and in control.  So I just don&#x27;t talk about the &#x27;Big Things&#x27; at all.  Peering into the void that is the Big Things is the quickest way to make a Happy Customer (who pays on time at a good rate), into a very upset individual.<p>6) Bank the money and take time off. Turn off the phone, close the email app, stock up the fridge, tell people you will be out of town for a while.  Get comfortable .... and code.  Code the big things. Do it in the comfort of your own setup, away from everyone, and take your time. No deadlines, no clocks, no timesheets .... just you, an editor, a github account, some emergent ideas that may or may not be well defined, and some code.<p>Working on the &#x27;Big Things&#x27; is simply not negotiable.<p>I never charge for doing the &#x27;Big Things&#x27;, and I never discuss this with customers, or try and use it as leverage in future billing arrangements.<p>Working on the &#x27;Big Things&#x27; is simply not negotiable.<p>Working on the &#x27;Big Things&#x27; is why I program and why I ever started to get into this in the first place. Being able to properly  immerse myself in the Big Things, on my own terms, on my own time, out of my own pocket ...  is compensation enough, and worth far more to me than any paycheck ever will be.<p>Working on the &#x27;Big Things&#x27; is simply not negotiable.<p>Having a set of &#x27;Big Things&#x27; in my toolbox then enables me to re-enter polite society for a while, in order to crank out some more &#x27;Little Things&#x27; easily and cleanly, and get the bills covered. You need happy customers for that. Happy customers with Milestones and Ticks in Boxes and Smiles and Invoices and Cash on Time.<p>But working on the &#x27;Big Things&#x27; is simply not negotiable.