S4E39 Kyle Valiton | Common Pitfalls of Startups, Dealing With Stress, Setting Budgets

Being an Engineer · 13 Oct 2023 · 44m · Episode 39

What this episode covers

Kyle Valiton, founder of Build to Launch, discusses common pitfalls in startup engineering, emphasizing the need for strong cross-departmental communication and the use of tools like Slack to maintain transparency. He advises engineers to adopt an 'abundance mindset' and set realistic budgets to manage stress and avoid pigeonholing during R&D projects. Valiton also highlights the importance of storytelling in prototyping and building professional networks through closed communities like Discord and Slack to support career growth.

Other shows on the same ground, closest first.

  • Product Startup · 34m

    034: Staying Motivated & Overcoming Lack of Money, Time & Skills

    Filip Valica, founder of Mako Design + Invent, discusses overcoming the limiting beliefs of lacking money, time, and skills when launching a product startup. He shares his personal journey from a corporate engineer to founding Mako Design + Invent, emphasizing the importance of deep core motivation and using failure as data to validate ideas. Valica outlines practical strategies for managing time, such as blocking calendars and saying no, and advocates for a DIY approach using tools like Canva, Inkscape, and Jungle Scout to minimize upfront costs. He argues that perfectionism is the enemy of progress and encourages founders to start small, iterate, and surround themselves with supportive communities to avoid burnout.

  • Oxide and Friends · 1h 44m

    Engineering Culture

    Bryan Cantrill and Adam Leventhal of Oxide Computer Company discuss the nuances of establishing engineering culture, distinguishing between absolute principles and relative values. They analyze case studies from Meta, Twilio, Amazon, and Uber to illustrate how values like 'frugality' and 'urgency' can be misinterpreted or weaponized if not carefully defined. The speakers emphasize that culture must be established early through explicit hiring criteria and that changing an established culture is nearly impossible, making initial alignment critical.

  • How I Built This · 1h 03m

    Slack & Flickr: Stewart Butterfield

    Stewart Butterfield, co-founder of Slack and Flickr, recounts his journey from building the failed online game Game Never Ending to creating Flickr, which he sold to Yahoo, and then pivoting from the second failed game, Glitch, to build Slack. He details the specific challenges of raising capital for enterprise software, the difficulty of selling a communication tool that requires network effects, and the rapid scaling of Slack from an 8-person team to a massive organization. The episode also highlights the importance of organizational performance over individual genius and the role of luck in startup success.

  • How I Built This · 42m

    Live From HIBT Summit: Payal Kadakia, Tristan Walker, and Perry Chen on Innovation

    In a panel discussion from the 2021 How I Built This Virtual Summit, Guy Raz speaks with Payal Kadakia of ClassPass, Tristan Walker of Walker and Company, and Perry Chen of Kickstarter about the nature of innovation. The founders argue that innovation does not require newness but rather authenticity, soul, and solving personal frustrations, such as Walker’s experience with razor bumps or Kadakia’s difficulty finding dance classes. They discuss their early struggles, including ClassPass’s initial product failure and Kickstarter’s long development cycle, emphasizing the importance of resilience, specific metrics like ClassPass’s reservation count, and the value of continuous improvement in hardware.

  • The Pragmatic Embedded Podcast · 43m

    From Vision to Reality: Product Roadmaps in Embedded Development

    Hosts Jeff Gable and Luca Ingianni discuss the hierarchy of planning artifacts, moving from product vision to roadmaps and backlogs, emphasizing that roadmaps are alignment and discovery tools rather than static commitments. They identify common mistakes such as the 'progress by PowerPoint' trap, where teams list milestones like 'specification complete' instead of value delivery, and the danger of over-committing to dates before understanding the problem space, particularly in VC-funded startups. The conversation covers tailoring roadmaps for different audiences, the importance of prioritization, and the 'iceberg principle' of granularity, concluding with a discussion on the iron triangle of project management and why varying resources is often the least effective lever when a project is late.

The summary, chapters and topics are generated from the episode’s audio by this directory, not written by Being an Engineer. The episode itself belongs to its publisher.