For example there exist "applications"/"demos" that exist "to show the customer what could be possible if they hire 'us'". These demos just have to survive a, say, intense two-hour marketing pitch and some inconvenient questions/tests that someone in the audience might come up with during these two hours.
In other words: applications for "pitching possibilities" to a potential customer, where everything is allowed to be smoke and mirrors if necessary (once the customer has been convinced with all tricks to hire the respective company for the project, the requirements will completely change anyway ...).
> That does not mean you are correct. This mindset is useful only in serious reusable libraries and open source tools. Most enterprise code involves lots of exploring and fast iteration. Code quality doesn’t matter that much. No one else is going to see it.
Here? Most of those that I’ve listed IS boring enterprise code. Unless we’re taking medical/military grade.
but most people aren't writing code in those places. its usually CRUD, advertisement, startups, ecommerce.
also there are two things going on here:
- quality of code
- correctness of code
in serious reusable libraries and opensource tools, quality of code matters. the interfaces, redundancy etc.
but that's not exactly equal to correctness. one can prioritise correctness without dogmatism in craft like clean code etc.
in most of these commercial contexts like ecommerce, ads - you don't need the dogmatism that the craft camp brings. that's the category error.
Even in web software, you can write good code without compromising in delivery speed. That just requires you to be good at what you’re doing. But the web is more forgiving of mistakes and a lot of frameworks have no taste at all.
