SQL Developers: What Do They Write? Do They Write Good SQL?? Let's Find Out! Thursday 11:50 Baltic II+III
Briefly is not my strong suit. When I was a kid I liked computers, I had a chance to start working as C++ developer during the university so I ended up working in IT, but in the high school I studied very old things like Latin and Ancient Greek... and Turbo Pascal. I left Italy almost ten years ago and in this time I really enjoyed this Schengen thing.
Currently I am a BI Architect at Zalando, in Berlin, I deal every day with data and people using them.
I'm sorry, but I never attended one before, but I'll do my best to contribute to PGconfEU2017.
My talk will be about writing good SQL code. It will not be about the SQL syntax or improving your database performances. It will be about writing code that it is easy to read, understand and maintain. Things like "do not call your variables a, b, and c".
Today we have an always increasing number of smart people writing SQL, but many of them have very little experience on working in complex organizations.
I'm thinking about the new data scientist in your team that runs that machine learning alghoritm, but when he asks you some help with his query to extract the data you need twenty minutes to read it. But there is also that senior guy who still uses the "Oracle sintax" for the joins. Please move on.
I used to get angry about these things, but then I remembered how I learned these things, someone took time to explain to me what I was doing wrong. This is my way to give back.
People who want to improve their SQL should be in the audience, but I think also the people who think they write the best possible code should attend. I hope there will be something interesting for all.
And of course the Bojack Horseman fans to cheer me up.
It is the PG conference so I expect people will be confortable with some simple snippet of SQL code. Then if you know where the title talk is coming from you probably will like it.