|
|
|
|
|
|
by unfocused828
3730 days ago
|
|
|
> break the task down into smaller and smaller bits One problem here is that if I don't really know everything the task entails, then I end up asking myself "am I going to really need to do this?" and can't think of a way to answer that question without writing code. Maybe the right approach here is to accept this and to write a few automated tests for external APIs. Another is that I just need to be disciplined enough to do this consistently. |
|
|
Surely you can do a first level breakdown of what needs to happen.
"First I receive data, then I process the data, then I send the data over there.
Ok, to receive the data, I'll be getting an HTTPS post, so I'll need to have an endpoint set up.
I don't know how endpoints are set up here, I'll need to ask, but I do know that it will be a POST, and the data will need to look like this...
After I get the data, I'll need to process it. It starts out looking like this, and I want it to end up looking like that. I do know that I will need to save the data in the database. I don't know what libraries/ORMs, whatever, I'll need to ask."
and so on.
I think you're still thinking from the bottom up - what are the all the details, from the beginning. But, think from the top down, making the task into smaller and smaller bits until you have reached an understanding of each bit.