Hacker News new | ask | show | jobs
by ahstilde 1256 days ago
Taylor, I really enjoyed this post, and I shared it with my engineering team and also group chats.

At Wyndly, we're a software-enabled allergy immunotherapy practice (https://www.wyndly.com/pages/immunotherapy). I have a background in software engineering, and I had to learn that code wasn't always the solution. Better code doesn't mean better business outcomes for us! Sometimes I say "Every line of code is a liability!", because it's now something a small team has to support forever.

Your three bullets on how to build are something I agree with so much! Arguably, this is something everyone outside of an at-scale product should build while finding product-market fit and growth channels:

- Focus on building simple solutions that solve real, urgent user problems, in well-worn ways.

- Use battle-tested software and platforms that are stable and don’t change too much over time.

- Only integrate with third parties when it’s absolutely necessary for solving those real, urgent problems.

Thank you for sharing!

1 comments

Thank you! Glad you enjoyed it!