5 ms·
(author). I agree with your sentiment , and try to make this point in the article. This is why I suggest using out of the box admin frameworks and other ways t
by gnutrino 4y ago
(author). I agree with your sentiment , and try to make this point in the article. This is why I suggest using out of the box admin frameworks and other ways to provide quick admin features. Only spend time adding custom functionality once a need arises. With this approach you already have the frameworks setup, tested, and you have been writing your code with support in mind.
- jakelazaroff 4y agoThanks for writing the article! It definitely helped me crystallize some of my thoughts around this. I think the point at which we differ is that I actually prefer the "Oh #&@$ Solution". Part of it is to avoid building tools that I never end up using. But even if I do use a tool a lot, I would still rather slow development later rather than sooner. For example, I'm the only engineer, building an admin tool means product development stops, whereas if I wait until we've hired another engineer it means it only slows down by 50%. Or, if we only have a few months of runway, it's much more valuable for me to work on things that increase revenue or decrease costs in terms of actual dollars than things that make the company more efficient. Obviously these are contrived examples, but the general theme here is that time now is more valuable than time later. So the further into the future something is expected to pay off, the more suspicious of it you should be.