The article in its current format is almost unreadable.
The art of conversation is unknown to many. I attempt to explain to others that conversation is a volley - not a match. Serve up softballs, allow others to answer questions, and then return the favor by asking a question.
Conversations with the iPad generation are almost worthless. Conversations with strangers are often fruitless. I am silent for the most part because people cannot speak in a manner that would suggest they have any interest outside of their own pleasures.
Code grows, decisions get made, and practices are adopted.
I am working on my fourth iteration of what turns out to be my largest undertaking.
Step
1. Idea
2. Hack something
3. Commit, comment.
4. Hit a wall
5. Rewrite, commit, repeat.
6. Grow until new problems are discovered
7. Modules, tests, etc to avoid future problems.
8. New problems caused by complexity.
9. Go to 5.
My recent example - I thought I could get away with 3 VMs to run my SaaS. Yes, I could, although my storage capacity guesses were 100x less than required.
I am a unicorn of sorts because I could do all that and yet I would not want to because I am going to guess that the minimum amount of hours required to meet the previous person's output I would have to work ~65 hours a week.
I personally see a minimum of three jobs, done well, at 30 hours a week.
Your counter 2x which may be due to my system - felt a little odd.
So let's say you get your 20% - and then zero savings - do they remain a client?