CRUD is actually just what were called 'expert systems' in the 80s. Once you realize that, you can see that it is actually the most interesting type code.
The real problem with programmers is that they don't specialize in a specific type of application and become domain experts in it. Choose a field, such accounting, or hr, or finance, and become an expert in it throughout your career, so that you develop the most featureful CRUD application of that type in the fastest time (or base a startup around it).
Knowing java, php, sql, etc. is like an accountant claiming he just knows bookkeeping. A really valuable accountant is someone who might be a specialist in taxes for medium sized manufacturing firms in california for example.
"CRUD is actually just what were called 'expert systems' in the 80s."
No. CRUD was a programming style that arose from relational database technology. CRUD = (Create, Read, Update, Delete) corresponds to the SQL CREATE, SELECT, UPDATE, DELETE statements. CRUD was popularized by Oracle. For example, Oracle's program generators IIRC used the acronym CRUD as part of their program generator's specification.
"Expert systems" in contrast, were a specific outgrowth of AI technology in the 70's and '80's and were defined loosely as systems that mimicked human expertise.
There is no necessary conceptual overlap in the two terms.
That's a simplistic unerstanding that ignores the actual technology. Expert systems were nothing more than logic programming dressed up to seem all "ai". Prolog is backward chaining, while Clips expert system shell is forward chaining. Today they are referred to as business rules engines, which can again be forward and backward chaining.
Sql databases are also in fact logic programming, basically prolog without recursion and iteration, but instead have pl-sql and t-sql to make them turing complete. Also, with triggers they are also forward chaining too.
The main difference between crud and expert system is essentially that crud is multiuser and everchanging, and so is actually a better version of classical expert systems.
I'd disagree; the modern day equivalent to expert systems would be ersatz "Semantic Web" (the idea of intelligent Internet applications; including, but not limited to RDF/OWL/Reasoners and/or "business logic" engines such as JBoss Drools).
My comment above explains why sql is pretty much the same as logic programming and business rule engines. The semantic web is just a way of saying that everyone should be using a "universal database schema", and once you think of it in those terms is a pretty silly idea - there isn't a remote chance that will happen.
CRUD is actually just what were called 'expert systems' in the 80s. Once you realize that, you can see that it is actually the most interesting type code.
The real problem with programmers is that they don't specialize in a specific type of application and become domain experts in it. Choose a field, such accounting, or hr, or finance, and become an expert in it throughout your career, so that you develop the most featureful CRUD application of that type in the fastest time (or base a startup around it).
Knowing java, php, sql, etc. is like an accountant claiming he just knows bookkeeping. A really valuable accountant is someone who might be a specialist in taxes for medium sized manufacturing firms in california for example.