A developer shares their preferred approach to building full-stack applications, arguing against starting with the frontend. The recommended order is: design with UML diagrams first, then build the database, then the backend, and finally the frontend. Key reasons include avoiding data mocking pitfalls, having real types available for frontend work, and reducing context-switching between layers. The author acknowledges this is subjective and influenced by their background in C++, SQL, and UML.
Sort: