This can be incredibly frustrating for developers. In my own experience, the person in the worst position is the developer brought in to clean up another developer’s mess. It’s now your responsibility not only to convince management that they need to slow down to give you time to fix things (which will stall sales), but also to architect everything, orchestrate the rollout, and coordinate with sales goals and marketing. Oh, and let’s not forget actually producing the code to resolve the underlying issues. It can, at times, be an insurmountable problem. A developer in that situation has to wear a lot of hats. They need to be:● An advocate to management and by extension the C-suite.● A project manager.● A marketer to understand the features and desired functionality both now and down the road, to make selling the product more simple with defined pipelines and marketable features.● A decision maker, willing to make tough calls with regards to future compatibility of the services, how they interact, and what third-party tools they might need to integrate with to ensure the rectified code will be usable for the foreseeable future.Last but not least, they need to be a good developer to fix the mess. If you employ a developer who can manage all those responsibilities as well as their day job, I guarantee you aren’t paying them enough, or they’re already looking somewhere else.

If you want to implement a form with a superb User Experience, you have to take care of many variables:

it also allows for more divergence in how people write there code and where they put their logic, making different svelte codebases potentially even more different due to fewer constraints. This last point is actually something I really value, I read a lot of Svelte code by a lot of different people and broadly speaking things look the same and are in the same places.

there’s 3 steps to building software: Make it work Make it right Make it fast