Addressing run-time problems
The mantra "if it compiles, it works" helps followers score amazingly well in time-to-market ratings for enterprise software development.
Taking Jet.com as an example of building green field e-commerce platform implementation, it has really condensed the path from zero to minimum viable product (MVP) in less than a year. Release of the platform to the production mode took place in a bit more than a year from the reception.
Does this mean following a functional-first approach is a software development silver bullet? Surely not on an absolute scale, although on a relative scale, the improvements are just great.
Why is the success not exhaustive? The thing is that the practice requires transition from gory ideas to mundane implementation issues. No matter how accurate our implementations are, there are always dark corners exist where unexpected problems may lurk.
Let me demonstrate this with a sample taken from F# enterprise development practice at Jet.com...