The best advice I’ve gotten (and applied) for solving large/complex development tasks is to research and map out a solution BEFORE you start coding. 🗺⠀
⠀
— Do the research, explore, and weigh all the potential options. ⠀
— Does this task/project lend itself to some system design pattern? Explore that.⠀
— Don’t forget to explore existing tools and services/APIs. Don’t reinvent the wheel.⠀
— Write/type them in some organized form (document, diagram, etc.)⠀
— Determine the logic flow and data flow; how does data move through your solution?⠀
— Define and diagram the different components needed and how the will work together⠀
— Also get feedback from another dev(s) if possible. ⠀
⠀
⠀
This doesn’t have to take a long time or be a lot of writing, but even doing a little of this upfront can save a lot of time and produce better software.⠀
⠀
👉🏾 Curious; what is your advice for tackling large development projects/tasks?
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (6)
Thank you!! These are gems!
Documentation is key. I've worked on a fairly huge project that was initially estimated with 9 months for the MVP, unfortunately, it dragged on for 2 years; TWO YEARS! The major cause of the delays were features and additional functionalities that were "sneaked in", you may call them scope creep. We have documentation for the functional specs but they are everywhere, we have a version in cloud, on the contract, and somewhere else's computer but they all don't tell the same thing. If there was one thing I learned through it, have the everything documented in one place, and DATE them. Document every decision on the project you've talked about with the client/project manager be it in a formal meeting or a coffee machine encounter.
Also I love that picture 😂
😂😂😂 Thanks lol! Supposed to be me working on my laptop but it got cut off
Plan for security and failure