Monthly Archives: September 2018

New database position (s) at Braviant Holdings

A number of people have asked me, when we will be hiring again. My answer is that as a company, we are hiring all the time. And right now there are several opened positions, including several IT position. But now there is also one more database position opened, so if you missed it last time – here is your chance:).

The job posting is here, and a position description is the same as six months ago. And I am still looking for the same set of skills, and whatever was mentioned in this blog post is still applicable.

I can’t stress more – please read a job description carefully, when I say I need some skill, I really mean it!

To answer other questions I’ve got recently: yes, there will be more database positions next year, but I am not sure when and what positions specifically. And no, I can’t take interns right now, because neither me, nor my team has resources to train people who do not have relevant experience and will be likely gone in a couple of months.

My last hiring period was very long and stressful, but at the end we were able to hire great people, so my outlook as of now is pretty optimistic.

Leave a comment

Filed under Companies

Our presentation on PG Open 2018

It went really well, and what was especially important for me – many people commented on how it exhibited the team work. Not only our work itself, but also how our marketing department helped us to make our presentation really cool and shiny, and everything 🙂

Here is a recording of the actual presentation:

The Q&A – we had lots of question!

connecting galaxies-2


Filed under events, talks

What’s happening at PG Open 2018

Lot’s of interesting talks! The fact that this year I am not alone at the conference, that I have a team – helps a lot! We coordinate between the three of us, which talks we want to attend. Otherwise I don’t know how I would manage! Yes, you can read about the new features of Postgres 11 online, but it is way more interesting to listen to the people who made it happen. Also, I am always looking for people who are solving similar problems as we do, like dealing with incorporating time into data, improving the speed of the data load, and finding efficient ways to connect to external systems.

I was able to catch up with many people whom I knew from the previous conferences, and met lots of new interesting people. And there is still a whole day of the conference ahead, I will try again to listen to as many of the presentations as I can.

Tha opening of the conference

Leave a comment

Filed under events, talks

How to deal with “First you write, then you optimize”

Recently I’ve made yet another attempt to optimize several quite inefficient report, which had been out there for so long, that nobody remembers, who have written them, and who have speced them out. I did not finish this task, even with the help of my team we just didn’t have enough time to spare on improving something, which “works”. And when I was thinking about it over the weekend, I thought that different people may have different definition of “works”, when it comes to SQL writing.

I always say – it’s easier to write the code correctly on the first place, that to optimize reports which are written inefficiently, but way too often I am getting a response from the stakeholders – we need it now, you can optimize it later. And then later never comes.

This is so obvious, that I would not spend time writing about this yet another 101th time. However this time my thoughts have taken a different path. I thought about why I was unable to finish this optimization, why I didn’t have enough time. The reason was, that something else which I was writing have taken way more time than I originally planned. And the reason why it took so long is that I find myself unable to write, even as a first draft, the code which I know for sure is suboptimal. No matter how many people will tell me that “it does not have to be perfect”. And then – yes, it takes longer.

Now I think that when I teach an optimization class, and when I am showing to my audience some cool technique, my thought process is that everybody should realize how much better this technique is, and than use “that and only that” approach, because how-else-this-is-so-obviously-better. And as for my audience, people think – ok. It’s cool. Good to know. And do not change there code -writing habits…

Once again, I might have been just ignorant, and may be everybody knew it all along, but it was a revelation for me: if I want to teach people good coding habits, if I really want to avoid this situation “first write, then optimize”, not only that I need to show people how to write a coode code. And not only I need to show how not to write. But I also need to teach zero-tolerance to the bad coding. So that people’s minds won’t even wander in this direction:). If it is not written the right way, it is not done.

I am pretty sure nobody would like this idea, but can I at least have a dream :)?


Filed under SQL