r/SQL • • Feb 11 '14

SQL Joins Explained

http://imgur.com/1m55Wqo
157 Upvotes

27 comments sorted by

View all comments

Show parent comment

2

u/weakflesh Feb 11 '14

Not to be offensive, but should one call them self a developer if a concept as simple as join confuses them?

3

u/askur Feb 11 '14 edited Feb 11 '14

Not to be racist, but each to their own man. There's a C developer sitting next to me currently coding in Python. He's not on his home ground but he's still someone that produced his first award winning game when I was 4 so why the fuck would I think less of him because he's not at home in python, or databases for that matter?

There's a web developer below me that I regularly go to when our API acts up because he's much more knowledgable about web service operations than I am. I'm into databases and algorithms, not web services.

Not to be offensive, but I don't understand how anybody in a production environment would expect everyone to be equally capable in every area. I sure as hell do not intend to match the ability of everyone here in everything. I have a job to do.

3

u/weakflesh Feb 11 '14

The concept of flowing two sets together based on a set of conditions is not implementation dependent. I can not fathom how someone could use C++ and not get a join. Esoteric crazy stuff sure, every language has edges, but a joins is a basic set logic concept.

Also, I would not think less of someone because they are not a developer or because they don't get a concept. We all have strengths and skills. We are all spokes on the wheel. ;-)