We lament about the recent GDPR hullabaloo, our initial reactions to the new regulations, and how we approach projects that we don't have any business handling in the first place, but still fall onto our shoulders.
We talk about Alexa development, the strong developer ecosystem Amazon is investing for it, some of the privacy problems it's facing, and a few quips about Apple, Google, Microsoft, and even Samsung.
April Wensel started a company named Compassionate Coding, which aims to "humanize the tech industry." We discuss why she started the firm and how she goes about making the tech industry a better place to work. We also learn that using the term "soft skills" is not the right way to talk about the people side of things if you want to earn buy-in towards change.
We talk about Firebase as a new backend tool for a few projects we're working on and cover many of its features, what is weird about it, and why this seems to be a product in which Google is making a big investment. Hint: It's about the Person, er, people!
In another installment related to the Chasms app, we discuss errors with the prototype, finding the right balance of customer/product fit, and the need to brainstorm without adding requirements to the ideas.
We talk about meetings, the negative vibe the tech industry has taken against them, how to best run meetings, or finding ways to communicate without wasting so much time.
Listen as Don and Randy begin a new side project together from problem/solution explanation, planning, and build approach. We aim to reduce the product scope and target a quicker launch of the prototype.
People (and ourselves) have been asking: Why are you all doing this? What is motivating you to podcast? In this episode, we discuss our motivations for podcasting, our side projects, and why we're doing multiple challenges at the same time.
Would you hire Kanye West if he was a great programmer, despite his social media presence? This week, we talk about social media quality control, public personas, and the challenge of being inclusive while trying to maintain a steady team dynamic. We also somehow bring up Pink, Tim Tebow, and James Damore into the conversation.
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.
Mark Thompson gave himself a tough 30-day deadline to build and launch the first version of his app, TotallyStrong.me. Setting a goal gave him tremendous motivation, but also served him with a strong dose of feeling failure. Find out how Mark finally followed through and shipped, despite a self-imposed timeline that both motivated and defeated.
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.
Mark Thompson discusses his learning and launching a native app using Flutter, a new cross-platform framework developed by Google.
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.
We have a guest, Megan Schemmel, discuss her new career as a developer, learning Wordpress, and taking on the new Grid functionality of CSS
Don and Randy discuss the steps we've taken to better learn JavaScript, Node.js, React, and React Native. A whole lotta videos and pain.
Randy and Don introduce our new, loose-form podcast, and talk about how it contrasts with our more formal, parent podcast, CTO Think.
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.
