Having a strong network makes for a huge advantage for career opportunities and learning how to lead. We discuss how to push past shyness and introverted tendencies to grow your own network of relationships.
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.
With hacking, data security, and privacy as huge issues in the press, we discuss how we approach identity management on both products and across our teams.
Where do you draw the line on ethics? How do you take a stand when you want to keep your job? This week, we discuss ethical behavior and the responsibility people have regarding it.
Should you sign non-compete or non-disclosure agreements? Are these kinds of contracts binding? Are they even useful for your business? We discuss everything from saying "heck, no," to turning the ask into an initial business agreement test.
We discuss our history with in-office and remote work, why junior devs might reconsider working outside the office, and how requiring folks to work in your proximity is a trait of managerial vanity.
We speak with our first guest, Mark Thompson of Trilogy Education, about his approach to creating a productive learning environment both on the job and in a classroom setting. Mark is also working on a side project named Totally Strong, which is pushing his own limits about learning to code while building an MVP (and raising a newborn!).
Randy and Don found themselves stranded, mid-ride on the Expedition Everest roller coaster at Disney World's Animal Kingdom. Following their rescue, and during an in-person recording from Orlando, they talk about how a tech manager should handle technical downtime, service interruptions, and critical alerts for users, executives, and investors that depend on services.
Are code challenges or quizzes a legitimate practice for hiring developers? We debate whether the method of filtering candidates via whiteboarding or code games is plain lazy or a necessary part of the recruiting process for engineers.
If a junior developer is looking at the fork in a technology career path of software engineering or management, what kinds of skills do they need for the leadership side?
Is the call for "developer focus" a selfish complaint from precious snowflake employees? What right do developers have to ruin the design trend of great-looking open offices where collaboration magically happens? This week, we discuss how we feel about the need for managers to talk to employees at all times vs the need for folks to get work done without interruption.
How do you choose the best hosting options for your product or firm? This week, we discuss the thinking in a choice between self-hosting, managed hosting, cloud options, and the new buzz word: "serverless".
We discuss the importance of a work-life or non-tech balance for someone building a career in technology. Do folks need to set aside a specific amount of time, or any at all, not working on things related to their job?
Randy is a CTO that codes almost daily. Don has found it difficult to string together multiple days where he's able to code for his current roles. Today, we tackle the topic of whether a CTO or technical manager needs to be able to code to be effective at their job.
Don brings up the subject of chaos, based on a book he's been reading, Antifragile, by Nassim Nicholas Taleb. We discuss the merits of test driven development, unpredictability, and how technical managers can work towards a more resilient product in the face of inevitable failures.
Randy and Don discuss an item ripped from the headlines: What should a technical manager do about the recent Meltdown and Spectre exploits? They move into the CTO modes of research, understanding, translation, preparation, upgrading, monitoring, and, most of all, not freaking out. Randy requests a bobblehead or plush toy of the Spectre logo.
Don faced an issue at his education tech firm: When should you slow down forward progress on new features in order to spend time on festering technical issues?
Randy was posed a question by a potential client: "I want to build an app. Who should I hire?" and he asks the same question to Don.
Welcome to CTO Think, a podcast about how technology leaders think about business, tech, and people problems. Don VanDemark and Randy Burgess, two current and former Chief Technology Officers will discuss the various challenges managers face in a product development environment. We'll cover topics such as team-building, product management, scaling, and software engineering decisions.