Code Story episode
S6 Bonus: The Fractional CTO Fallacy: Move Beyond Fragmented Freelance Code and Build a Dedicated, Entrepreneurial Product Engine with Patrick Bryant, Co-Founder & CEO of CODE+TRUST
May 18, 2022 · Season 6 · 36 min
An entrepreneurial approach to software
Patrick Bryant lives in Charleston, South Carolina, and splits time in Washington, DC. He loves entrepreneurship, and believes it is the number one change agent in the world. He is involved in multiple communities around the topic - Startup Grind, EO, and he founded the Harbor Entrepreneur Center. Scuba diving is the thing that takes his mind off all things though, given you are 100 feet under the water, and have to focus. He is excited to go dive with the sharks soon, and he also enjoys the beaches and being in the sunshine.
Prior to his current ventures formation, Patrick and the other three partners had two software products and other companies they were building. Between them all, there were two dev teams... and in the interest of making a bigger impact in their space, they decided to join forces, and form one team.
This is the creation story of Code & Trust.
Sponsors
ImmediateOrbitPostmarkStytchVerb DataWebapp.ioLinks
Website: https://codeandtrust.com/LinkedIn: https://www.linkedin.com/in/patrickbryant/
Checkout our episode stacks on Stacklist! https://stacks.codestory.co/
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
More episodes
Keep listening
Topics
Explore related conversations
Technical due diligence checklist for startups
A technical due diligence checklist for founders and investors: what reviewers examine across architecture, security, team and process, and how to prepare before a raise.
Fractional CTO vs full-time CTO: which does your startup need?
A practical comparison of a fractional CTO and a full-time CTO: cost, scope, when each makes sense, and the questions to ask before you hire either one.
CTO vs VP of Engineering: how the two roles actually differ
CTO vs VP of Engineering explained: who owns architecture, who owns delivery, when to split the roles, and how to avoid the overlap that breaks engineering teams.