5 ms·
I'd say the opposite because of responsibility. A bug in the BE can cost a lot of money and time to your business, not so much (usually) in the FE.
by htatche 5y ago
I'd say the opposite because of responsibility. A bug in the BE can cost a lot of money and time to your business, not so much (usually) in the FE.
- woutr_be 5y agoWouldn't that mean that both have the exact same responsibility? A bug in the FE, would essentially render the BE unusable, and therefore would cost a lot of money and time as well. For example; if Amazon's checkout button somehow broke, and prevent users from checking out, it would also cost a lot of money. EDIT: to give a more visual example, if Amazon changed their checkout button to a different color and style. It could potentially cost them millions, because it might not entice users to click it.
- nnoitra 5y agoMuch easier to fix a button then dive deep into why your algorithms which should work, don't work.
- deleted 5y ago[deleted]
- woutr_be 5y agoHow so? If that button is part of a complex frontend, with multiple stylings who might inherit from each other, it could be quite a task to fix it correctly. It's not as simple as just looking into your developer tools, and adding some CSS to it.