I'm with you Emily. I've been in the software world for years (that does not mean i know too much or that I'm a true expert). Most of the projects I've been part of started by designing or solving the "source of data" problem, where the data will reside, and the underlying business rules. Way back when, we talked about Databases. Nowdays DDD -> Database -> Backend. By solving them we will have most of the business rules implemented. Then, we should code a front end that even could be required for different types of devices. However, in favor of what Anik wrote above, is a good idea to have a basic prototype, layout, screens, that can help the customer see what he/she is going to get as a software product (at least for the main or critical parts of it)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm with you Emily. I've been in the software world for years (that does not mean i know too much or that I'm a true expert). Most of the projects I've been part of started by designing or solving the "source of data" problem, where the data will reside, and the underlying business rules. Way back when, we talked about Databases. Nowdays DDD -> Database -> Backend. By solving them we will have most of the business rules implemented. Then, we should code a front end that even could be required for different types of devices. However, in favor of what Anik wrote above, is a good idea to have a basic prototype, layout, screens, that can help the customer see what he/she is going to get as a software product (at least for the main or critical parts of it)