3 ms·
I think even with edge-cases, the question remains valid why you can't automate the common cases. I wonder how often it's actually non-standard requirements an
by xg15 9y ago
I think even with edge-cases, the question remains valid why you can't automate the common cases.
I wonder how often it's actually non-standard requirements and how often it's a mix of processes and poor communication/changing requirements.
I think in many projects, in hindsight it's perfectly obvious it is just a standard CRUD app - but it might need a few iterations to get the understanding of all stakeholders to that point...
Also, seems to me that such tools clash with the organisational process of how webapps are created today: It almost seems to be required that a web app has some kind of custom-written "business layer" in between, even if that business layer doesn't do anything than pass requests around.
- adrianratnapala 9y agoI think heavyweight frameworks often make the edge cases harder, because when you need to do something "unusual" you end up fighting the framework, and now you end up with a complex program where the framework as well as the buisness needs count as the problem domain. But you are likely onto something that some things are just standard apps even if you can't see that at the time. And my mind might not be well tuned to seeing it even in hindsight. Which makes me think that banging out simple apps fast is a very specific skill, because you need to see how to meet business needs within the slot provided to your by framework.