3 ms·
You should not introduce complexity into software for the sake of adding complexity. That goes without saying. Most business logic problems are not inherently
by patio11 18y ago
You should not introduce complexity into software for the sake of adding complexity. That goes without saying.
Most business logic problems are not inherently complex -- the overwhelming majority of programmers in the world will spend the overwhelming majority of their time on the routine practice of their profession, not pushing its boundaries. Same with doctors or lawyers for that matter.
This categorically does not mean that the routine parts of the job suck. I write CRUD code for Japanese universities. Sample: there is a table which holds session data into it. Take the number of people who are currently logged in and record it to a file every 5 minutes. Make the file accessible by FTP for another system.
Is it going to set the world on fire? No. Is it an opportunity to practice my craft, to carefully design around the obvious issues and the not-so-obvious ones? Yes. Does it improve the lives of my customers? Yes -- that file makes a graph possible and that graph is going to get one forward thinking administrator a raise because it will demonstrate that the project he staked his organizational capital on is a success. As it should be, as the project (which is MUCH bigger than me) helps the university and its students out scads.
It doesn't have to be a multiorgasmic thrillride EVERY day of the week, you know.
- dasil003 18y agoIt'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.