4 ms·
It's actually pretty insulting that the author assumes most developers are just looking to add needless complexity. The OA is just a multi-page rant against th
by dasil003 18y ago
It's actually pretty insulting that the author assumes most developers are just looking to add needless complexity. The OA is just a multi-page rant against this blatantly braindead straw man.
The truth of good software development practices is that there are no absolutes. We work in an abstract world, where the architectures we build are limitless and the requirements are rarely complete.
For instance, the author seems to be preaching hard-code business logic rather than dynamic data-driven logic. Well you can't really make that decision in a vacuum. It depends on how often you expect those conditions to change, whether you need to use them in another context, if they are dynamic who will be responsible for editing them, what is the cost of editing them incorrectly, how does the additional dynamic logic dilute the clarity of the program, etc.
In my experience, writing the CRUD code is not tedious. Once I decide what needs to be written I type it out in a couple of minutes (your framework has facilities for this, your IDE has autocomplete, right?). However even the most trivial app is full of critical decisions based on the reality of the business requirements. Every decision is interrelated and has many potential outcomes that are difficult to quantify. What I find fascinating is trying to provide the best solution to a business problem. There's no busywork about it.
- nazgulnarsil 18y agoBut it isn't always adding complexity for the sake of complexity. sometimes it is efficiency in a scenario where making the code 10% more efficient isn't really worth it because it makes the code harder to maintain.