A practitioner's job is solving the customer's problem, not pushing a particular tool. Pick the right technology for what they need, then find efficiencies once you know it well. The goal is serving the customer best, not being loyal to a platform.
Chapters
Focus on the job, not the tool. I often talk to people who get very excited about their advocacy for their tool or the stack that they use. People who are very, I'm very pro WWX, or I'm very pro using Buildship, or I'm very pro using people who get excited about Draftcode or Noodle or Toggle or whatever. And I tend to think that's misplaced. What you want to focus on is how to do the job for the customer, for your clients, really well. And that means picking the tools that are going to be right for that given context. Now, some of that is going to be learning how to use the tool well, but a lot of it is understanding what the job is for the customer, what their needs are. Point our attention, focus on what the job is, select a good tool for that job. When you're using that same tool over and over, ask how you can get some increasing returns on that. But the North Star should be the customer. The North Star should be demand. How it is we're going to create the greatest service and the greatest value for others.