Published Aug 3, 2021

Episode 471: Jason Meller on Choosing the Right Tech Stack for a Greenfield Project

Jason Meller dives into the intricacies of selecting the right tech stack for greenfield projects, discussing front-end vs back-end decisions, the impact of programming languages like Python, Ruby, Java, .NET, and PHP, and weighing strategic considerations for building or buying solutions for optimal project success.
Episode Highlights
Software Engineering Radio - the podcast for professional software developers logo

Popular Clips

Episode Highlights

  • Decision Factors

    emphasizes the importance of aligning tech stack choices with team productivity and empowerment. He argues that while engineers often aim for objective decisions, personal biases and familiarity with certain technologies heavily influence choices. At , they prioritize empowering powerhouse engineers by selecting technologies they are comfortable with, which enhances productivity 1. Meller also highlights the anxiety surrounding tech stack decisions, especially for small teams with limited budgets, where optimizing for self-sufficiency is crucial 2. He notes, "There's a lot of anxiety when choosing tech stacks because that's really going to determine the quality of life or the day to day for that engineer."

       

    Balancing Skills

    Balancing existing skills with the need to learn new technologies is a critical aspect of tech decision-making. and Jason discuss scenarios where founders might choose suboptimal tech stacks to leverage existing skills and quickly test ideas 3. Jason advises against learning new technologies on the fly when time is limited, suggesting that founders should focus on getting their ideas out quickly, even if it means accruing technical debt 4. He explains, "You need to be able to just get out of the mindset of every time that you need to do something, you're trying to translate your old JavaScript knowledge into what is the language equivalent of this in Swift."

       

    Build vs Buy

    The decision to build in-house or buy existing solutions is pivotal for startups. Jason suggests testing the validity of an idea with minimal software engineering to avoid unnecessary technical debt 5. He recommends leveraging managed services to fill knowledge gaps, allowing founders to focus on core business logic 6. "If you are a person, it's just you. You have your idea and you have enough software engineering knowledge. That doesn't necessarily mean you know definitively that you can build the whole thing, but you're willing to bet on yourself to actually build it out," Jason notes, highlighting the importance of strategic decision-making in early-stage projects.

Related Episodes