For some reason I feel like there were less announcements this year about the upcoming PG Open. But now it is fast approaching: it will take place Sep 5-7, in San Francisco, at the Parc 55 Hilton hotel – same as the last year.
I will be presenting again, however I do not feel it as “again”. Some of my peers were telling me that they are so sure my talk will be accepted – they can’t even understand why I may be anxious. But for me this year was especially challenging. The workload was huge, partially objectively, partially because of the ambitious goals I’ve set for myself, and partially because of the health issues I’ve being dealing with for the past several months.
This being said, I am really happy that our talk was selected to be presented at the PG Open. And another reason to be happy – after three years gap I got back to my favorite topic of ORIM, and I am presenting together with an app developer – my coworker Alyssa Ritchie. Almost back to the old days, but better :).
And the Early Bird registration is still opened – please check out the conference web site!
The SIGMOD 2018 conference in Houston TX is approaching it’s end, and it’s the first time a had a moment to sit down and write a paragraph about it. All I can say – I am really happy to be here.
I was questioning whether my participation in the conference will be productive, when I do not have a paper to present, and also whether it is a wise idea to go away for a week when I am still a one person shop, and me being at the conference effectively means a pause in all database-related development. But now I am really glad I did.
There were a number of talks which made clear connections between theory and practice and reminded me one more time that there can be a very fast path from an idea to the production implementation, when you know what exactly you need. As they say, the theory without practice is fruitless, the practice without theory is blind. A number of talks addressed very specific problems I was trying to resolve, and all I wanted to do was just to say thank you to the people who’ve made my life easier.
Hopefully there will be more to follow, and for now I just want to thank my company, Braviant Holdings for the support of employees professional development and for understanding it’s importance.
Recently I was asked to submit my “Motivational inventory”. Among other questions there was one which made me think for a while: if I think about the best manager I ever had, what would make him(her) awesome? Here is what I’ve replied.
I was lucky to have several awesome managers, and I can’t really rank them. But there was definitely one thing in common for all of them- they were supportive.
They would trust my technical skills and would let me to do things “my way”, even when it was not “like people normally do”.
They would have patience to wait till I reach the desired results, even when I myself didn’t have patience .
They would help to resolve the conflicts between team members, and would make sure there is no bitterness left. It would often require multiple phone conversations, and sometimes felt like marriage counseling :).
They would recognize my achievements and make them visible to the upper management and clients. And they would support and motivate me at the moments when I would feel I am a looser and nothing works.
I think that being supportive is the most important role of any manager. Trust, openness, recognition of employees achievements – all of these things can be viewed like forms of support.
I like this saying, because it always reminds me about the danger of doing something “just for now”, and I often cite it to my coworkers when I argue for a better, more stable solution. However, sometimes I would revert to these kind of tactics myself, and then…
Yesterday one of our external service providers was moving our data to another server, and as a result I had to recreate the foreign servers associated with it, and cascade-recreate all the foreign tables. I’d say I am reasonably organized, all all my data definitions are stored in a github repository. So that in the event like yesterday I just need to rerun a DDL script.
Which I did. And a half an hour later I’ve started one of my daily jobs, which sometime crashes, that’s why I am always keeping a closer look on it. It crashed that time as well, but for an unexpected reason – one of the foreign tables used could not find it’s source… The name didn’t look familiar to me, and it was definitely not created in the morning. I’ve searched the github with no luck, then searched the “suspicious” directories on my computer. Finally, I’ve started the global search on my computer and iCloud. And I’ve found a missing definition! Guess, what was the name of the file it was stored in? – temp_fix. sql