Yup, ugly quick-and-dirty monoliths and then fix it and make it more object-oriented incrementally. You need something barely functional for tech demos if it's external, or you need shit prototyped quick if internal. Outside of designing databases (and school bullshit) I've never used even block diagrams before starting the ghetto-code.
ghetto-code, well written, is a great basis to draw a block diagram from. In my industry, there are requirements to provide block diagrams for certain aspects of the system... some I pull out of -thin air- before starting anything, others are best generated from however the code finally took shape.
(Score: 1) by Ethanol-fueled on Saturday May 26 2018, @12:04AM (1 child)
Yup, ugly quick-and-dirty monoliths and then fix it and make it more object-oriented incrementally. You need something barely functional for tech demos if it's external, or you need shit prototyped quick if internal. Outside of designing databases (and school bullshit) I've never used even block diagrams before starting the ghetto-code.
(Score: 3, Informative) by JoeMerchant on Tuesday May 29 2018, @01:21AM
ghetto-code, well written, is a great basis to draw a block diagram from. In my industry, there are requirements to provide block diagrams for certain aspects of the system... some I pull out of -thin air- before starting anything, others are best generated from however the code finally took shape.
🌻🌻 [google.com]