Today’s Top Tech Skills
In the recent two or so years I was surprised to see how many people don&#x27;t _really_ know about SQL. Sure they can write a simple insert and update query and maybe a join, assuming they can just ignore that there actually are different types of joins. But if you ask them about other _still fundamental_ knowledge like a _rough_ idea about what the different transaction isolation level are&#x2F;mean&#x2F;imply for you, they fail hard.<p>Realizing this allowed me to understand why:<p>1. There is so many used ORM(ish) libraries which make it in practice harder to access the database for anything but trivial queries.<p>2. NoSqlish databases seem to have became so successful even in application where non of there &quot;benefits&quot; (wrt. scalability and similar) matter and you would normally prefer to avoid some of there drawbacks (e.g. eventual consistency, no &quot;system wide-ish&quot; transaction, enforcement of correct schemata and some parts of data consistency). (Sure there are other reasons for there success, too. Like being fancy, modern or no clear requirements analysis and therefore no idea about scaleability requirements ...).<p>I mean if SQL and relational databases are for you just structs with a bit more basic types then JSON but which in turn are flat requiring annoying foreign key references and a bunch of ceremony around this with very little added benefits then yes it makes so much more sense to just use a nosql database and be done with.<p>(PS: Yes I&#x27;m aware that for certain use-cases the resulting databases can be very complex and hard to use, what I mean is that it&#x27;s a skill you have to learn to use efficiently and a scarily large amount of people a came in contact with in the recent years not only don&#x27;t have that skill but are not aware that, if they don&#x27;t want to mess up larger databases they work on, they will have to learn that skill.)