3 ms·
It's not all one or the other, I'm more of a layer-at-a-time developer and within a layer development can be inside-out (start with an algorithm and add an inte
by zwieback 4y ago
It's not all one or the other, I'm more of a layer-at-a-time developer and within a layer development can be inside-out (start with an algorithm and add an interface) or outside-in (start with an interface and mockup, then add the internals later).
- cestith 4y agoI mostly like to choose a data structure that's handy for modeling the data I'm worried about first. Then I write code to manipulate that data, including getting it into and out of other formats if necessary. Then I worry about what the application really needs to do with it. Once everything's a presentation or transformation of the central data structures, the code becomes fairly obvious. One I have the data handling and the UI, often the UI is just another case of presenting or updating the data.