Thoughtful Software Podcast

Thoughtful Software Podcast

By Fahad Shoukat and Andrew WolfeNewsTechnologyTech News
Download on the App Store

Thoughtful Software Podcast episodes

  • Untangling Project Complexity

    Despite the availability of many project management tools, there is still a 70% failure rate within the software industry. Join us as Andrew and Fahad discuss the issues that stem from using project management tools, whether they are genuinely effective, and how to use these tools without undermining the ability to innovate and succeed.

    Show Notes:

    • Why is there so much failure in software? There are more than fifty different project management tools on the market such as Asana, Monday, Atlassian, and Service Now. If the failure rate continues to climb do these tools really work? 
    • While data is readily available, the actual complexity of a project is not necessarily represented in the data. Modern technology has become very intricate, but the intricacy isn't being tracked anywhere. 
    • The best-performing organizations have built great habits and their habits are driven by their culture. The culture is driven by good ideas and usually good leaders within the organization.
    • Set the culture, what do you want to become? What is your goal? What is the outcome you want while you're measuring to get there? And then what system is going to help you achieve those metrics? 
    • What is the cost of failure rate and why is it acceptable in this industry?  The returns are so high that when a company does succeed the failures almost become a rounding error.  This won't last forever, especially as better alternatives arrive. 
    • Thoughtful Software does not mean move fast and break things, but move thoughtfully and break the status quo.

    At Skiplist we want to do something to curve the 70% failure rate. Want to see how we’re doing it? Click here

    Interested in this topic and want to hear more? We have even more resources available on our Insights page

    Drop us a comment and let us know how we're doing. We read and respond to every comment and email.

    37 min
  • Building Teams for Success

    In this episode of the Thoughtful Software Podcast, Andrew and Fahad discuss team building in software, hiring methods for creating the best team possible, ways to screen for the best cross-functional candidates, and proven methods for instilling quality leadership to help train and mentor junior developers to be the next wave of industry leaders.

    Show Notes

    • How to build teams for application and development. How should development teams be built from a non-technical founder or executive standpoint?
    • Start by looking at the size and maturity of the organization. Is there a technical founder? What is the maturity of that technical founder? 
    • Small organizations and startups should begin with Dynamic Programming languages such as Python or JavaScript. While these languages enable speed they do not often work at scale (number of coders working). Hiring top talent without paying them what Google or Netflix can offer requires new and exciting programming languages like Rust where people can come and learn.
    • Once hiring is figured out then the question becomes "How fast do we want to move?" Senior developers are going to move more slowly than junior developers because they often make better decisions and take their time because they have suffered through bad decisions before. Larger companies can afford to move slower whereas startups may not.
    • The last thing in hiring that must be considered is leadership. First are People Leaders - Managers, Directors, VP's. Second, are Tech Leaders - Engineers, Architects. Most startups need one technical leader.
    • The people being hired in a startup must have a growth mindset or it will crush your team.
    • Hiring at the enterprise level is designed to throw bodies at a problem, they are building to hedge against risk and return money to their shareholders. 
    • How can you screen for good candidates? Asking the right questions at the start: "Tell me why you picked this one technology and give me your reasons for doing so?"  Asking someone to defend their choices is the best to understand why people make choices.
    • How important is it now for developers to be cross-functional and understand the context of their code, not just the latest and greatest languages? Understanding the business you are in is important. As a leader, you have to understand where the company is going and where the market might force you to go. Any single agenda can't supersede that of the business. 
    • What Does a Good Technical Mentorship Look Like? Pairing on programming is very helpful and explaining and working through errors together with junior engineers rather than leaving a note is a great learning experience. Enabling engineers to confidently sell their ideas and training them to execute. Let people make the mistakes and then help them learn from those mistakes is the constructive loop needed. Great leaders are always training their replacements.
    • Hiring Remote will help optimizing business. 


    Thanks for listening! What did you think about this episode? Drop us a comment and let us know how we're doing. We take the time to read and respond to every comment and email.

    Visit our Insights page to hear some previous episodes of our podcast and our Articles written by The Skiplist Team.

    We’d love to know what you took away from our conversation. Follow us at @fahsho12 and @andrewwwolfe and share your insights and questions with the #thoughtful software.

    43 min
  • Turning Your Ideas Into Reality

    This is episode is about designing software that enables your vision as an organization to become reality. Although this topic may seem simple, it is a common problem that trips up many projects. Join Andrew and Fahad as they discuss how technology leaders should capture and communicate ideas, approach innovation, and bridge the communication gap that so often exists between engineers and executives. 

    Show Notes

    • How do we turn our ideas into something tangible, into reality into a valuable asset? We know that 68% 0f all software projects fail, and 70% of executives believe their initiatives are doomed from the start.
    • How Should Technology Leaders Capture Their Ideas? Know the problem first. Explore the problem space completely and understand why it's a problem, and then what opportunities are there to solve that problem.  
    • Knowing the problem first opens multiple avenues and affords opportunities to create a less expensive solution that solves a larger problem.
    • Only move into the solution space once the problem is understood.  Starting in the solution space is easy to do, but doing so may mean that you miss solving for parts of your problem that that was not properly understood at the start.
    • Product vs Project Mindset. A good product life cycle is constantly moving between problem space and solution space. Don't index on things, don't make assumptions, solve for what you know are the issues, and then go back and try to discover the other issues as well. 
    • Should Innovation be Incorporated into the Problem Solving Process? No. When you're in the problem space, you should not be thinking about innovation. Innovation is a byproduct of solving a problem.
    • Wayne Gretzky used to say, "skate to where the puck is going to be" and most organizations are not doing that because they are trying to copy what other organizations are doing. Do you try and become SoFi or do you look at where SoFi is going and become that instead?
    • Don't copy innovation, decide if you want to be there, or if they're missing the mark, skate to where you think they should be going, you'll be innovative and market-defining.
    • Understand context. What market are you in? Are you in a leadership position trying to hold on to users or do you understand the problem and are getting out in front of it?
    •  What is the best way for technology leaders and executives to communicate ideas? Design and prototypes are powerful because they are quick ways of showing somebody, this is what I interpreted. Now a conversation can take place about what was truly meant. 

    Resources Mentioned

    • SoFi
    • Wayne Gretzky 
    • Apple
    • Tesla
    • Ford
    • Facebook
    • Twitter
    • myspace
    • Uber 

    Thanks for listening! What did you think about this episode? Drop us a comment and let us know how we're doing.

    Check out the Insights page to hear some previous episodes of our podcast and our  Thoughtful Articles written by The Skiplist Team.

    We’d love to know what you took away from our conversation. Follow us at @fahsho12 and @andrewwwolfe and share your insights and questions with the #thoughtful software.

    36 min
  • Quantum Computing: Closer Than You Might Think

    In this episode, Andrew and Fahad discuss quantum computers, what they are, how they are different, why they will be game-changing for software, and how technology leaders can begin developing strategies now for quantum computing.

    Show Notes

    • Background: Classic computers have bits that are defined by either a zero or a one (binary), however, there are limitations to this as our computing needs become more complex and require more processing power while using less energy.
    • Quantum computing technology is not designed to replace classic computers, but are tools for solving more complex computing problems.
    • What Are They? Quantum computers are more complex than standard binary because they may process any number of quantum bits (Qubits), storing an enormous amount of information while using less energy.
    • It is theorized that RSA, which is a common algorithm for encryption, can be solved in milliseconds, instead of what right now would take hundreds of years.
    • Quantum Supremacy is a task that a quantum computer can do better than a traditional computer which can greatly impact areas like machine learning, life sciences, biology, chemistry, medicine.
    • Should Technology Leaders Already Be Thinking About Quantum Computers? Yes. There may not be a Moore's Law for QC yet, but the technology is constantly evolving so there will be.
    • If there is an innovation explosion in this field, it changes everything, and if you aren't one of the first people there when it happens you're going to lose.
    • Known Issues With Quantum Computing: Quantum mechanics generate a lot of heat and have to be at zero degrees Kelvin (-459 F) in order to be accurate.
    • These computers will not easily transition onto work or home desks since keeping QCs at zero degrees Kelvin is expensive.
    • No real significant case studies exist yet, still too early. Quantum computing is in its own punch-card stage.
    • Current systems such as Bitcoin are not secure enough to handle quantum changes and could create a Quantum Philosopher's Stone.
    • How Will Quantum Change Software Development? Two possible ways: 1) It will change everything and we will have to re-learn everything. 2)We will be building for and using a library of quantum abstracts.
    • It is best to create a road map with this in mind and assess as to whether your goal is to pilot this new technology, roll it out, or simply observe it (which is where QC currently is for most industries).
    • Quantum Computing may even change the landscape of video games and VR gaming.

    Resources Mentioned:

    • Moore's Law
    • IBM Quantum Computing
    • Amazon Braket
    • Microsoft Azure
    • TensorFlow

    Thanks for listening! What did you think about this episode? Drop us a comment and let us know how we're doing.

    Visit our Insights page to hear some previous episodes of our podcast and our Thoughtful Articles written by The Skiplist Team.

    We’d love to know what you took away from our conversation. Follow us at @fahsho12 and @andrewwwolfe and share your insights and questions with the #thoughtful software.

    30 min
  • How to Make Digital Transformation People-Focused

    In this episode, Andrew and Fahad examine digital transformation with a focus on people and strong leadership, how digital transformation should be established at the executive level, ways to keep up with competitors, and how an organization can begin transforming in a way that is healthy for the business and employees.


    Show Notes

    • Over the next several years 6 trillion dollars will be spent on digital transformation and yet 70% of these initiatives will fail, those that succeed will only see 15 to 25% improvement. 
    • Start by transforming the part of the business that needs the most transformation. 
    • How is it possible to prevent the digital transformation from being spread out across a business but keep it contained? Parallelism - that which is computationally true tend to also be organizationally true. 
    • The more sharing between processes the less likely they are to be parallel. 
    • To prevent split-brain and stop parallelization, creating company-wide ownership is extremely effective because moving together makes a company tend to further. 
    • How to catch up with competitors? Worry about achieving outcomes as a company, and differentiate from the competition with digital strategies. Do not try to end up like competitors because they will beat you with experience, and they know how to be themselves better than you do. 
    • Understand what you want to be and the outcomes that will get you there. 
    • How strong does leadership have to guide a company through digital transformation? Strong leaders understand that culture is the only differentiator companies have, and the future is in that strong leadership where people trust that leaders will do right by them. Building a culture of mutual trust takes time and empathy. When customers and employees feel like they matter they will stay with your brand.
    • Where to start /What Strategies to use?  Think like a startup, don't try to be everything to everyone. Instead, be the best in a particular area for a certain type of product and then expand. Decide where the one place is that will have the largest impact on the business. Pull the data together and start there. 
    • Answer the important questions, get the data you need, and do it over time and you'll find that you'll fail a lot less often. 


    Resources Mentioned:

    • Apple
    • Google
    • Microsoft
    • Procter and Gamble
    • Salesforce
    • Ford
    • General Electric
    • Activision-Blizzard 
    • Amazon
    • Walmart
    • Uber 
    • Lyft
    • Chewy 

    Thanks for listening! What did you think about this episode? Drop us a comment and let us know how we're doing.

    Check out the Insights page to hear some previous episodes of our podcast and our  Thoughtful Articles written by The Skiplist Team.

    We’d love to know what you took away from our conversation. Follow us at @fahsho12 and @andrewwwolfe and share your insights and questions with the #thoughtful software.

    34 min
  • Demystifying Software Architecture

    In this episode, Andrew and Fahad demystify software architecture, discussing what defines architecture, how to make it less complicated, what the real goals of architecture should be, why patterns and technical debt are important, and how company execs can use this knowledge to empower their business.

    Show Notes

    • Software systems are becoming increasingly sophisticated and complex and business expectations are driving that complexity. 
    • Go back to first principles
      • Earn Your Complexity 
      • Abstract for that which changes. You can know what changes if you study and understand your industry.
      • Think of the problem before the solution and patterns will naturally be revealed.
    • Architecture is business enablement which helps you to understand your product, its implementation, and its real world consequences. 
    • Technical debt is a vehicle for growth and not having it means that you are stagnant and not investing in anything toward the future. Leverage your technical debt by looking forward and understanding your product roadmap. 
    • Software is constantly evolving and you should be constantly leveraging technical debt to enable the business in the future.
    • There are no "best patterns' to use as you accumulate and use technical debt. Patterns are tools and as a hammer has a specific job, so does a pattern.
    • The goal is to refactor and pattern toward the simplest possible system. 
    • You can often abstract away compliance. Architects have to know about the product as well as how to be legal and compliant.
    • Can CFOs, CTOs, and CEOs identify things that can help them with this or should they simply just truth the technical people? The best architects are going to help executives understand the decisions being made and why they are making them. 
    • Ownership requires a lack of ignorance in the entire process. It is all about connecting with people and trying to help people.

    People and Resources Mentioned

    • Slack
    • Martin Fowler
    • Django
    • JavaScript
    • AWS 

    Thanks for listening! What did you think about this episode? Drop us a comment and let us know how we're doing.

    Check out the Insights page for a library full of Thoughtful Articles.

    We’d love to know what you took away from our conversation. Follow us at @fahsho12 and @andrewwwolfe and share your insights and questions with the #thoughtful software.


    31 min
  • Data Mesh: A Deeper Dive

    In this episode, Andrew and Fahad take a deeper dive into Data Mesh Architecture, discussing why it's important as well as examining the value of centralized vs decentralized structures. They also discuss data mesh nodes, examine some common issues a business might face with data mesh, and explore ways an enterprise can transition from a centralized structure to a data mesh.

    SHOW NOTES:

    What is data mesh and why is it important?

    • As opposed to a data lake, which is the attempt to centralize into one system many different pools of data, a data mesh decentralizes the data but centralizes its governance. 
    • It is important because it helps data-driven organizations function in a way that is sustainable.
    • Four issues at work that are slowing businesses down:
      1. Decentralized ownership of systems within a centralized structure
      2. Business is moving faster than ever and centralized structures can't keep up.
      3. Data lakes have become data oceans, impossible to index and understand. 
      4. Some data is in silos and not accessible to other departments

    Centralized vs Decentralized

    • There is no bad architecture - centralized, decentralized, monolith, distributed, monolith microservice etc.  The only right architecture is one that gets the job done. 
    • Data lake docks are a piece of business logic that prevents the system from changing. Pulling away from the doc and allowing the business logic to where it was is created then will allow the business to move much faster.
    • Data mesh allows a specific department to own itself without the entanglement of depending on other departments for their data.
    • Smaller organizations may be better off starting with a data lake, but build your mesh as you grow and become more complex. 

    Data Mesh Nodes

    • Bigger companies that are acquiring smaller companies can incorporate their data with a mesh node. 
    • You can still have data pipelines that merge multiple mesh nodes that create specialized data ponds which have only the info they need to do their job and help their department. 
    • Data mesh nodes enable you to think about the data to how to compose that data to solve a problem.

    Issues Concerning Data Mesh

    • Overdeployment, not every company is big enough.
    • Lack of overall governance can cause data mesh nodes to become swampy
    • Companies are going to make nodes too big. 
    • It is 1/4 of the size of the data lake market but will likely surpass the data lake market in the next five years as data mesh picks up the failures of data lakes. 

    How Does an Enterprise Roll Out Data Mesh? 

    • Start at your biggest pain point and work out from there, pulling the data apart piece by piece until eventually, you are decentralized. 


    RESOURCES MENTIONED:

    Kubernetes
    Tableau
    Salesforce
    NetSuite
    Snowflake

    PREVIOUS EPISODES MENTIONED:

    Episode 45 - The Evolution  of Data Architecture: Moving to a Data Mesh

    Episode 51 - Microservices: Trading Code Complexity With Organizational Complexity

    Follow us @fahsho12 and @andrewwwolfe and share your insights and questions with #thoughtfulsoftware. 

    31 min
  • Let Your Vision be the Guide, Not a Contract

    This episode is a discussion about the vision being your guide to navigate your digital initiatives. Don’t let yourself be tied to a contract. Be adaptable and flexible. There is no playbook but you can take steps to deliver thoughtful software. At the end of the day, it's all about value and delivering a product that your customers not only love but are served through.

    Show Notes

    Fixed Scope

    • In 2020, two-trillion dollars was lost on harmful software.
    • Fixed scope does not allow for dynamic software. Great for building bridges, not software.
    • Software often never goes according to plan, and customers want a specific fixed scope of results.
    • Fixed scope changes the buying process with which people have become accustomed. It feels risky.
    • Changing your thinking and planning appropriately can mitigate risks and improve relationships.

    Approaching Technology Thoughtfully

    • Many companies will take a large sum of money upfront and fail to deliver any software.
    • The organizational structure must change from a top-down structure to a bottom-up structure.
    • Being a manager is no longer a boss privilege, but servant leadership. 
    • The currency of power is no longer power, it's love. How do we build what someone loves? Your company doesn't have to be the most powerful, as long as people love you they will follow you.
    • Being Successful starts with a mission and putting people first.

    Software is a Journey

    • Thoughtful software is a journey because it puts the needs and problems of people first.
    • The best technology doesn't even seem like it's there, it just fades seamlessly into the background.
    • You have to think ahead and plan, but you also need the flexibility to change and adjust when needed.

    References
    Apple
    Nike
    GameStop
    Mike Tyson
    Mahesh Patel

    Previous Episode Mentioned

    • Episode 47: CFO's, CF-NO's, and Innovation with Mahesh Patel, CFO of Druva


    Thanks for listening! What did you think about this episode? Drop us a comment and let us know how we're doing.

    Check out our Insights page for a library full of thoughtful articles.

    We’d love to know what you took away from our conversation. Follow us at @fahsho12 and @andrewwwolfe and share your insights and questions with the #thoughtful software. If you’d like to be considered as a guest or have someone you’d like to hear from (Tech Leader), drop us a direct message on Twitter or Linked.

    33 min
  • Bring Data to Life with Storytelling, Featuring Katie Taylor, CEO of Untold Content

    This episode is all about storytelling and data. By itself, data is just numbers. However, if presented as a story the impact is far-reaching on how it shapes the content we consume. To become a visionary Technology leader, storytelling is key to bring clarity in a noisy world.

    Show Notes: 

    • Humans are wired for story
    • Data + story equals a more compelling narrative which could lead to more adoption
      • The right data in the right graph can be transformative
    • The key to effective data visualization is sharing impact stories
    • The tools you use to create the visuals depend on the audience
    • How CIOs and CTOs can reduce data silos to better effectively tell stories
      • It's all about alignment within the organization
    • How to help your team adopt a storytelling approach 
    • Spinning a story is never effective in the long run. 
      • Take the disaster of Theranos for example. The stories we tell must always be true. 
    • One of the critical challenges of our time is how we handle disinformation, misinformation, and alternative facts accepted as truth
      • We can't shy away from sharing truth assuming the average person wouldn't understand. 
    • Advice for businesses to incorporate storytelling: 
      • Think of your client first
      • Empower your team with stories
      • Pour time into professional development for you and your team


    References: 

    • Color Genomics
    • Untold Content Data Storytelling Training
    • Tableau 
    • Theranos
    • Katie's Podcast - the Untold Stories of Innovation Podcast


    Thanks for listening! What did you think about this episode? Drop us a comment and let us know how we're doing.

    Check out the Insights page for a library full of thoughtful articles.

    About our Guest:
    Kathryn (Katie) Trauth Taylor, Ph.D., is the founder and CEO of Untold Content. Upon receiving her Ph.D. in Rhetoric & Writing from Purdue University with an emphasis in Professional and Technical Writing, Dr. Taylor founded Untold as a writing consultancy devoted to empowering thought-leading organizations in communications and storytelling. Dr. Taylor and our team at Untold Content have crafted content strategies for several national initiatives, including the VA National Homeless Programs Office, VA Women’s Health Program Office, the Medication Reconciliation initiative, and the Millennium Challenge Corporation's global evaluation brief effort. Dr. Taylor serves and trains clients across sectors to accelerate their thought leadership and create research-backed, impactful content. Her own writing has appeared in several news outlets, trade publications, and peer-reviewed journals in business, medicine, science, communications, and rhetoric.

    41 min
  • Thoughtful Software in 2020 and Looking Ahead

    In this episode, Andrew and Fahad reflect on the state of software and technology in 2020. They discuss what advancements were made that enabled various platforms to become more thoughtful, as well as what companies can improve upon in the coming year. From the medical industry to privacy and data, join Andrew and Fahad as they bring us insight on how software across several spectrums can become more Thoughtful.

    Show Notes:

    Advancements for Software in 2020 to be more Thoughtful
    Data

    • Pharmaceutical - Testing, simulation, and machine learning. Instead of five to six years for a vaccine, we got it down to nine months because of technology and data. 
    • As a population, Covid has presented an opportunity for people to begin the journey towards more thoughtful software as we realize its impact on our lives. Services like Instacart became a pivotal part of people's lives.
    • Pfizer is a powerful example of what it means to use the right data, build the right architecture. It cannot be understated that they may not be as innovative as a 30 person team, but they get there by partnering with them. 

    Privacy

    • Apple made major changes to its ad platforms in addition to the way ads are served to individuals.
    • We have to start seriously asking the question: who gets to work on these projects, what are the qualifications required to do it, should people be allowed to do it if they are not aware of privacy being a concern?
    • 2020 has revealed that there is a ton of bad software out there, not because it is badly written, but because it does bad things to people like collecting data it should not have and monitoring individuals in ways it should not be doing.

    Remote Work

    • Working from home was once considered a fad but has now become an accepted practice. 
    • Google and Netflix have stated that they will not become fully remote. However, many of their talented employees may leave to work for fully remote companies such as Skiplist. 
    • Remote work helps employees be efficient from home without sacrificing productivity, in person office work cannot always say the same.

    Data Swamps to Data Lakes 

    • The Broken Window Problem states that one broken window in a building leads to many broken windows and degradation over time. Because data lakes are monoliths software falls victim to this, but great teams can stop this from happening.
    • Social media outlets are selling clicks because they need to make money, however, principles from microservices may help turn data swamps into data lakes. 
    • As we leave 2020 we have an opportunity to move forward and be innovative rather than simply go back to normal.

    Resources:
    Thoughtful Software Podcast: Episode 50
    mRNA
    Pfizer
    Amazon Fresh
    Safeway

    Thanks for listening! What did you think about this episode? Drop us a comment and let us know how we're doing.

    Check out the Insights page for a library full of thoughtful articles. 

    We’d love to know what you took away from our conversation. Follow us at @fahsho12 and @andrewwwolfe and share your insights and questions with the #thoughtful software.

    49 min

About Thoughtful Software Podcast

From the publisher's feed

Software is eating the world. Software is also eating our wallets. Billions of dollars a year are lost on unusable software projects. The world wants Thoughtful Software. We discuss how thoughtful…