Disclaimer: I know it's really important for the industry and it's worth the time.
SQL.
Yes, weird, but I don't like interaction with DB in SQL. I'm not sure if is just how the code looks or what makes me not finally learn a good way to do things in a DB. I know the basics on how to create, select, insert, update, delete, etc. But haven't gone far than that. Even plain DB design is something I don't want to learn deeper.
I know is kind of wrong "Then how do you store stuff?" someone on the team does that for me, writing an API or with libraries.
Disclaimer: I know it's really important for the industry and it's worth the time.
SQL.
Yes, weird, but I don't like interaction with DB in SQL. I'm not sure if is just how the code looks or what makes me not finally learn a good way to do things in a DB. I know the basics on how to create, select, insert, update, delete, etc. But haven't gone far than that. Even plain DB design is something I don't want to learn deeper.
I know is kind of wrong "Then how do you store stuff?" someone on the team does that for me, writing an API or with libraries.
Interesting ...
As you friendly #sql mod I'm really interested in hearing what it was that put you off.
DB design is something I'm delving into at the moment and find it's easier if there is a project to work on, or if it involves video games :)
BI Series: Entity Relationship Diagrams explained by Sonic the Hedgehog
Helen Anderson ・ May 20 ・ 3 min read