When solving a problem for the first time, start specific instead of generic. Focus on the narrow 10-20% of the domain that actually delivers value. You'll reduce effort, time, and cost while delivering faster.
Focus on the specific rather than the general. What I find is that often people are tackling a problem for the first time, they look at the problem in its most general form because they read documentation on like, hey, this whole area. And of course, people are tackling it from the general case, trying to create a broadly applicable piece or what have you. But the better way to do it is to look at it in specific form, which is what is the job to be done? What is the problem that you are trying to solve? Which allows you to identify the 10-20% of the problem, of the domain, of technology, of the shape, what you need, that you actually is going to, you know, create value in your situation. So ask yourself, what is the job to be done? How can you answer that, the question of how we're going to apply technology most specifically? And that will significantly shrink the amount of effort and time and cost that go into that build. When you do those things, you'll be able to accomplish a lot, a lot more quickly. And there's always time for you to step back and learn something new.
