4 ms·
OP, I am assuming you're the author of the article. I think it could be improved by relating it to an experience when the advice given wasn't followed. At the m
by maps7 7y ago
OP, I am assuming you're the author of the article. I think it could be improved by relating it to an experience when the advice given wasn't followed. At the moment I am struggling to gain anything from it.
- wheresvic3 7y agoThis is actually very interesting! The article is mainly trying to answer the question - how do I begin with a new project? Should I make the UI first or should I make the backend first? One of my projects where this advice was not followed was one where we decided to build something without having a clear idea of how it was going to be used. In this case we decided to focus on the backend and just had a very rough UI. This project went way overbudget because by the time we managed to get it to the users and got feedback, we had to refactor the entire data model and API due to new requirements. I suppose one critical take-away from all of this is that proximity to users is a key component of a project's success :)
- maps7 7y ago> I suppose one critical take-away from all of this is that proximity to users is a key component of a project's success Thank you. That is a great take-away actually.