3 ms·
Where do you start your new projects on front-end or back-end?
When you start a project do you start on the front end or back-end first? I have always started on the back-end which seems to drive management nuts because they can't "see" any progress. Do you have better results with starting with something front end and making it work or does that lead to management/client thinking things are more done then they actually are?
- facorreia 11y agoI recommend starting with one of the major use cases, implementing its UI and some of its back-end, even if you have to mock some of its functionality or simplify it a bit (e.g. only implementing the "happy path"). This has many benefits, not only because "management can see" the progress, but also because it's not uncommon that when we actually visualize how it will look like, our understanding of how to address the use case improves. So this reduces the requirements risk of the project, and could save you having to change or throw away back-end code at the beginning of the project. It also gives you a vertical slice on the system, so you'll have an idea of what the architecture looks like in practice (e.g. if it's too complex), which reduces technical risk.
- hamhamed 11y agoYou don't start a project for the sake of starting a project. The idea should be visualized in your head, along with some back end algorithms to solve it. That said, I usually start sketching it in a paper, then move to skeleton UI, making sure all my HTML is up, maybe use something like bootstrap to make it feel more appealing, then quickly code a lot of backend code (non-optimized) until it's functional..then jump back to UI, so i can visualize the ending project and then fixing remaining bugs/features/performance in backend then finishing touches in frontend. TL;DR: A bit of Front, a lot of backend, then some front again, a bit more backend, then finishing it up with the front
- PythonDeveloper 11y agoif your goal is to demo to raise money, the front end. Nobody spending cash wants to see how you've implemented cache or integrated twitters api. If your goal is to have a minimum viable product (mvp), you want to identify the least amount of work to do both front and back end to where they will function (or fake) the functionality needed to demo or open to alpha. facorreia is right, though, without a functional use case, you're wasting your time.