It's still fundamentally development for the marketing side of a business though, rather than development for the product side. I think the problem that people are struggling with is that they can't see how this information relates to them if they are software developers looking to do consulting work on software. Patrick's article really is from a marketing angle, even though there is a software development component to it.

That said, I think people are missing the key takeaway from the article. I think the most important thing in the article is right there in the heading "Clients Pay For Value, Not For Time". This is saying that you should frame your services in terms of a value proposition for the client. That is, how much money will you save them if they hire you to do X. Maybe X is "rewrite the backend to process transactions quicker" which will save them Y hours of compute time and reduce their AWS bill by Z a month.