Podcast log - May 2021

TOP Full Stack Radio: Ep. 101: Ben Orenstein - How to Build an App in a Week

In this episode, Adam talks to Ben Orenstein about the common mistakes people make when working on a new project that prevent them from getting it to the finish line.

• Why deadlines are critical
• Using manual processes to avoid building features entirely
• How launching a stripped-down version of your idea can help you build the right thing
• Recognizing when you don't need to solve a problem yet
• Why you shouldn't design your entire UI upfront
• How evolutionary design applies to both code and interface design
• Why you should always finish a feature before starting the next one
• Applying this approach to Ben's current project Tuple

Full Stack Radio: Ep. 106: Sam Selikoff - Single Page Application Architecture

In this episode, Adam talks to Sam Selikoff about single page application architecture, and why you should think of client-side applications like desktop applications.

• Why you should think of SPAs as desktop apps instead of web apps
• Strategies for pushing complexity out of your backend and onto the client
• Building optimistic UIs
• Best practices for storing and retrieving data
• Why you should design your SPAs with an "offline-first" mindset

TOP The SaaS Podcast: Ep. 285: Paperform: How a Developer Bootstrapped a SaaS to $1.5M+ ARR – with Dean McPherson

Dean McPherson, co-founder of Paperform, discusses bootstrapping his SaaS product to over $1.5 million in annual recurring revenue, emphasizing the journey from a lifestyle business to a growing company.

• Identifying a market gap and developing the initial product
• Early promotional efforts and the impact of an AppSumo launch
• Transitioning from one-time payments to recurring revenue
• Scaling the business through team expansion and marketing efforts

TOP Full Stack Radio: Ep. 102: Paul Jarvis - Staying Small

In this episode, Adam talks to Paul Jarvis about defining your own version of success and why you might not need to build a big business to achieve it.

• Why "success" shouldn't mean the same thing to everyone
• How to stay small without doing all the work you don't want to do yourself
• Why it's important to define what "enough" is for your business instead of always feeling the need to do better than you did last year
• Questions to ask yourself to figure out what "success" would be for you
• How knowing your "enough" can help you build better products for the people you want to serve
• Why you should ignore the people who don't like what you're doing and double down on the people who love it