How do you break ground and start making progress on a big coding task?
How do you take the first steps in a daunting and complicated software project?
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (7)
I typically try and break it down into smaller chunks wherever possible, first of all in a bullet list and/or diagram. Once I start to see the components involved, I then try and further break each of those down, just to the point where I know enough to start spotting obvious 'gotchas'.
I like to build little POC (proof of concept) versions for the more complex parts as well, since it can really speed things up when you come to do the 'real thing' later on. The danger is of course that the POC ends up in production 😅.
It helps when I can see some progress, so early on I try and get to a point where something works and is demonstrably part of the way there.
So basically start with some high-level part that changes, even if the inner-works still have lots of work to do. I find this better than starting with some underlying logic which doesn't feel as close to finish.
In a ideal world, I start writing ::
.... until
like this (dev.to/pengeszikra/wannabe-js-fram...)
If we talk about whole project, tackle the hardest pain point FIRST. Do NOT work on authentication, infra etc until you solve this one problem.
Start with a prototype of the Minimum Viable Product. Break it down, build it up piece by piece. Just get started :)
Avengers, Assemble!
I have a cold beer 🍻 with an LLM