Why cutting cost is expensive ( from Medium)
https://medium.com/javascript-scene/why-cutting-costs-is-expensive-how-9-hour-software-engineers-cost-boeing-billions-b76dbe571957
Disclaimer: I'm not author of the post.
My take: as indie developer we often underestimate how much effort later will require to fix things, without a proper process. I understand that lack of process is a plus on start, but for me it's only on prototype phase.
What do you think about this?
In software, slow is fast.
This sentence impressed me a lot.
I think that attitude is important in all project phases.
It is always important to tradeoff between ship fast and ship something at least maintainable.
Because if your prototype works and users arrive with the conseguent issues you should be able to fix issue fast and have the time to increase product features.
Yes I agree. At every new project, fresh start new idea, I'm more and more convinced that have solid evidences on what must be done and a clear planning phase are crucial
I don't think the article has much relevance to indie developers.
Yes, you are in the prototype phase and should not be encumbered by thinking too much about future efforts and process.
As you start to see some momentum with users/customers... then you start to think further out with process and change management and all. (good problems to have)
Optimize for the task at hand.
I understand your point but also find lack of "planning" and "process" a limitation. Without some planning and process (even minimal, not too much heavy!) your prototypes are only "create ideas fast as possible" and wait until one works.
I can see a lot of wasted potential here, one for all: start from scrath every time