"One more thing".  We always have one more thing to do in software development -- whether our customer asks us for one more feature, or we task ourselves with going beyond the requirements, the challenge remains: how much is enough?
What is overengineering?  How do we know when our software is ready to launch?  When customers can always come back to us with more work -- one more thing -- when do we know when to stop adding more features?  How can we reduce scope creep in our projects while still overdelivering?  Does it even make sense to overdeliver?  What "one more thing"s make sense as developers, and what does overengineering even look like?

Ver todos los episodios