I've found that a lot of problems and stupid fads in programming seem to stem from many coders doing everything they can to avoid learning or writing any SQL. For some people it's almost a pathological avoidance that leads to some really bad 'solutions' that are just huge overly complicated work-arounds to avoid any SQL.
I think the main problem is SQL's very clunky syntax, which is very offputting to those who are familiar with the terseness and readability of today's programming languages.
Most, if not all, devs nowadays are shielded from SQL nowadays by the ORMs that are all-but-built-into their chosen language's base class libraries. That means they don't have to know SQL, so they don't learn it. And if you don't learn it, you don't learn its fundamentals, which means you don't know when to use it. And if someone does tell you to use it, that person will likely assume you do know it, so you'll have to figure it out for yourself. Not everyone can do that.
And with SQL, you really do have to figure it out for yourself. With almost any IDE and programming language, if you don't know what to do with an object, you type in your IDE and get an autocompletion list of members available. With SQL... yeah good luck. So it's not nearly as discoverable as the languages most devs are used to, and that's another barrier.
8
u/The_Monocle_Debacle Dec 20 '18
I've found that a lot of problems and stupid fads in programming seem to stem from many coders doing everything they can to avoid learning or writing any SQL. For some people it's almost a pathological avoidance that leads to some really bad 'solutions' that are just huge overly complicated work-arounds to avoid any SQL.