I'm excited to have another contender on multi platform apps space but in the case of Flutter for desktop I just wonder about the RAM consumption compared to Electron.
I hardly see a scenario where shoplifting is acceptable. Hell, the only possible scenario I might "tolerate" would be if it was food (As in, you are so poor you can't afford to eat).
I wouldn't mind working on that kind of software tho, specially if I am "days/weeks away from being completely broke".
If you happen to know the runway time you got before things start to fall apart economically, I don't think there's much to argue regarding code quality (and general maintenance of the platform).
In large companies, projects usually have a budget and some desired launch date. If that launch date is not met, your _worst_ case scenario is you're fired. While your best is the acceptance that It just got delayed by whatever factor affected the outcome.
With small companies, your worst case is you're fired and the company could go bankrupt (or something as bad).
Now, OP said he was at a mid-size company and I'd like to believe he could be a beacon of change as the company grows. Maybe all the other seniors were used to work in startups and just can't fathom doing development any other way.
Bottom line is, your expectations might be off depending on the scale of the company and their current objective.
* User authentication
* Users can post products to be sold
* Making orders to _other_ users
Move on to the details of those features
* User authentication
-> Social login OR email authentication
-> Usual features like reset password/forgot
-> Most other features will only be available when authenticated
I try to keep progress measured by features and use kanban boards to keep track of it. I don't go overboard with keeping everything in their lane and the checklists updated because I tend to not update things as much as I wanted to.
I am part of a startup for the first time and, coming from a project that was a bit messy on its own but had some structural integrity, I feel a bit torn apart with the current code quality.
For starters, the project _must_ be done in a completely serverless manner (AWS was the chosen provider) and _nobody_ in the team had experience making a complete product just using this kind of architecture.
Since performance is the main concern, at the beginning we did a very shallow research on our options for languages and relevant items to the lambda's performance. One of those was cold startup time, which the bundle size has influence in. This led us to split our custom dependencies as much as we could, making the development and testing more painful.
With both previous points presented, I can say our code quality is not good. As for velocity and delivering on time, we have had some issues because of planning mistakes and unforeseen inconveniences while using AWS SAM and AWS CF. Nonetheless, we're "on time".
We have identified some pains that we would like to fix post-launch but that moment seems to never going to happen. I got a feeling we won't have time to do maintenance on the product and we'll just be bombarded with either bugs or new features.
As others have said before, customers will only look at the app's functionality and UX. And in our case the application looks amazing. The backend, not so much.