CTO Think

{{ show.title }}Trailer Bonus Episode {{ selectedEpisode.number }}
{{ selectedEpisode.title }}
{{ displaySpeed }}x
{{ selectedEpisode.title }}
By {{ selectedEpisode.author }}
Broadcast by


There are a lot of factors tech managers need to consider when inheriting or choosing a technology stack. We talk about how we chose specific stacks in the past (or didn't) and why we're using a brand new one for a side project.

Show Notes

  • We've started a new podcast! Check out This Old App and subscribe!
  • We chose the Node, Express, Firebase stack for a new project we're working on
  • The first question most CTOs ask is "What pieces of a stack do we have already?"
  • The old phrase "Nobody gets fired for IBM" later became "Nobody gets fired for choosing Microsoft"
  • Open source stacks come with some risk.
  • The people maintaining libraries in an open source stack can just quit, and you can't do anything about it.
  • A big part of choosing a stack is the development community that comes along with it.
  • Regional development and proximity of developers for a stack can be a factor for what people choose.
  • Your personal laptop is part of the stack. You need to be able to use the stack of choice from anywhere.
  • Where you can source developers or the best hires available can drive a big part of the tech stack decision.
  • A tech leader should make a tech stack choice based on what the team members know, not what they personally know.
  • It's a bit selfish to force a company to switch tech stacks simply because a new CTO knows a different stack.
  • Python has really taken off because the data analysis piece is such a strong part of the stack
  • The lack of stability of stack development can be an issue, such as the issues with Python 2/3 or Node.js/io.js.
  • A big part of your choice is whether the companies maintaining the stack have a financial incentive to do so.

Thanks for listening to the CTO Think Podcast.

Shownotes and previous episodes can be found on our website at www.ctothink.com

Reviews on Apple iTunes are always appreciated and help promote the show.

Patreon contributions help us to produce transcripts, which allow people that are deaf or hard-of-hearing to access the show.

For questions, comments, or things you'd like to hear on future shows, please email us at hello@ctothink.com

Show music is Dumpster Dive by Marc Walloch, licensed by PremiumBeat.com

Voiceover work by MeganVoices.com

You'll hear from us next week!

What is CTO Think?

A pragmatic podcast about leadership, product dev, and tech decisions between two recovering Chief Technology Officers.