I even remember the "Learn Oracle at the Sea" advertisement.
But that's the state of affairs and I try to avoid them as much as I can. Amazon seems to think similar [0].
His answers were sometimes prime examples of what is today known as seriously unwelcoming. But I remember I un-learned the "best practices" meme reading one of his answers. In fact it was just one sentence, some concise version of "if the 'best' setting existed, nobody would bother to make it a configurable option". But it clicked.
Burleson's more advanced answers were of limited usefulness, because they have never mentioned the exact oracle version. They often have been only valid for antiques like Oracle 7.
The infamous MSSQL "string or binary data will be truncated" error (fixed a while ago[0]), or the way either deals with unqualified access to columns which leads to surprises (e.g. in MSSQL subqueries or in Postgres's SECURITY DEFINER procedures).
[0] https://docs.microsoft.com/en-us/sql/t-sql/database-console-...
Oracle seems to have more than most, IMO.
I have a journeyman data engineering level experience with each. Rare combo I guess, Data Scientist focus.
Also, I had to switch to DBeaver since Oracle SQL Developer made things worse with random crashes and freezes. Back when I used it, an easy way to freeze the editor was connecting to a DB via VPN and then suddenly disconnect. The connection gets stuck, parts of the UI get frozen and after a while the whole thing freezes.
MySQL/MariaDB and Postgres are better.