How I went from $100-an-hour programming to $X0,000-a-week consulting

There seem to be a lot of comments centered on “wow, this sounds great – I wish I could charge more” or “how do I find these high paying contracts”? Here’s one way. It may seem obvious to many, but I think it bears stating. If you are looking for consulting contracts that pay really well, focus on providing a service that helps companies make money rather than save money. In other words, help grow revenues rather than reduce expenses…

Perhaps other people here shared the same assumption that I did - that this essay was about moving from tech development as a contractor/employee to tech (development) consulting. It's not. It's about moving from developing to marketing. There's nothing wrong with that, but it was a let-down to me to discover that the path to riches meant mingling with the group of people I tend to like the least in a company. Also, I think it's fair to say that…

Interesting yarn. I'm probably missing the point of the style, as it certainly doesn't seem to have damaged the author's success, but it's kind of unusual to see such verbosity.

I found this valuable—especially the part about shifting to weekly billing. That one change helped me rethink how to scope projects as valuable milestones, set expectations, and build trust faster with clients. I also appreciated what he said didn’t work: long, detailed proposals and “homework” for prospective clients. I used to default to that too—until I learned a model at Stanford that emphasized one-page scopes focused on outcomes, not tasks. Since then, I’ve seen much better traction. His point about…