Re:How to Decide What to Build
by shubhamjain on Friday April 13, 2018 @01:35AM
(#16827346)
I would suggest trying to think about what task your team has to do often that is better done by a software--a minor but recurring annoyance. Like, in my case,
- Backend and Frontend development are never in sync, so we have to resort to mocking the API by using dummy code. There are API mocking services, but I would prefer something that mocks locally. Charles Proxy is great for this but it can be limiting and isn't very intuitive.
- Every time our customers face an obscure issue with the product, there's plenty of to and fro to understand the root cause of the issue. If there was a product that could tell us the trail of actions that the customers followed, it'll make debugging vastly easier.
Of course, there's a world of difference in recognizing the problem and creating a sustainable product. But, every organization is inefficient in some sort of way. It's just a matter of observing carefully.
- Backend and Frontend development are never in sync, so we have to resort to mocking the API by using dummy code. There are API mocking services, but I would prefer something that mocks locally. Charles Proxy is great for this but it can be limiting and isn't very intuitive.
- Every time our customers face an obscure issue with the product, there's plenty of to and fro to understand the root cause of the issue. If there was a product that could tell us the trail of actions that the customers followed, it'll make debugging vastly easier.
Of course, there's a world of difference in recognizing the problem and creating a sustainable product. But, every organization is inefficient in some sort of way. It's just a matter of observing carefully.