This page and its subpages are public.
The goal of an iteration is to get feedback from the end-user.
In this chapter we are going to discuss why iterations are so important and how we work with iterations.
Most importantly we will discuss what doesn't count as an iteration.
We do the smallest thing possible and get it out as quickly as possible.
That’s how we’ve built Moralis from the start.
We got the idea and within 1 month we already had a working beta.
Small quick iterations are the key to success as they allow us to show customers what we are doing and collect feedback quickly and potentially adjust our course.
If you make suggestions that can be excluded from the first iteration, turn them into a separate issue that you link.
Don't write a large plan; only write the first step.
Trust that you'll know better how to proceed after something is released.
You're doing it right if you're slightly embarrassed by the minimal feature set shipped in the first iteration.
This value is the one people most underestimated when they join Moralis.
The impact both on your work process and on how much you achieve is greater than anticipated.
In the beginning, it hurts to make decisions fast and to see that things are changed with less consultation.