Hey devs,
🚀 If you are trying to Build Innovative and Technically Challenging Solutions Fast, Spikes can be a very effective approach!
While Building Fusion, we embraced the strategy of Spikes to address complex UX and technical challenges efficiently. By focusing on specific problems, testing potential solutions rigorously, and ensuring top-notch UX standards, we were able to integrate solutions seamlessly into our product.
Although this approach led to occasional regressions in existing functionalities, it significantly enhanced productivity and efficiency. For instance, the implementation of "Linked Blocks" within Fusion enabled us to compose API blocks, reducing redundancy in test definitions and cases - but when we initially conceptualised this idea we were not sure how to estimate the work needed for this feature as we had way too many unknowns. We adopted Spikes for this particular challenge and very quickly we were able to identify the work required to build this as a proper feature in Fusion.
While many teams may naturally use this method, explicitly identifying and allocating time for such Spikes, especially in innovative projects, can be highly beneficial.
What are your experiences with using Spikes in your projects? Share examples, along with the upsides and drawbacks you've observed in the comments.
P.S Have you tried fusion yet? If not please do and let me know what you think - we are really going after something completely new in the API tooling/Client space so we are really looking for opinions :)
https://apyhub.com/product/fusion
thanks!
Top comments (0)