"If you want to delight your client, forge a relationship with them where you can actively help solve their problems. Even though your title might be some variation of “Software Developer” or “Software Engineer,” in truth it should be “Problem Solver.”"By The Pragmatic Programmer: your journey to mastery, 20th Anniversary Edition, 2nd Edition
"If you’re adding custom load balancing, extra caching, or automatic region failover, explain why it’s worth the extra time and effort. “We might need it later” is not a good enough justification."—The Staff Engineer's Path
"If you’re introducing a culture change, be patient. It takes a lot of time and dedicated effort to make everyone behave in a different way, but it’s the only way you’ll ever be able to stop pushing the process along manually."—The Staff Engineer's Path
"If you’re setting off to do something and you don’t know why, chances are you’ll do the wrong thing. You might complete the work without solving the real problem you were intended to solve"—The Staff Engineer's Path
"If you’re stuck articulating the problem, show what you have to five people and ask them what's missing: fresh eyes always see the truth."Staff Engineer: Leadership beyond the management track