In this podcast we discuss solution architecture and design tradeoffs on the platform to meet business requirements. I share how I apply my years of experience as a Software Architect to approach problem solving and we walk through some examples.
Listen to our conversation at https://technologyflows.com/2017/07/06/podcast-requirements-evaluation-solution-fit-with-doug-ayers/
Matthew shares an observation early in the conversation and it really struck a cord with me emotionally.
You seem to be the kind of person who finds a problem then writes a utility to fix it.
I’m pleased and thrilled to have that reputation! I love to learn, to teach, and to help others be successful.
All my projects are birthed out of seeing a problem statement.
More specifically, seeing a person who has asked a question on Success Community or #askforce on Twitter or at our local Admins and Developers Group and me thinking I wonder how we could solve that? And if this is a problem for you, I don’t want you to struggle so let’s work on this together.
If this is a problem for you, I don’t want you to struggle so let’s work on this together.
And if you have this problem, maybe someone else has this problem. So let’s solve it for everyone and make the solution open source.
Seeing a problem and then wanting to solve it. That really drives me. One, just to see if I can (ha!), but two just to be helpful and give back. I’m very thankful to be a part of the #Salesforce #Ohana.
Be helpful and give back.