Speaking at SQLSaturday Sacramento 2016

Speaking at SQLSaturday Sacramento 2016On July 23rd I will be speaking at SQLSaturday Sacramento 2016! This will be my first time visiting California, so I’ve planned a day of sightseeing in San Francisco before heading up to Sacramento. There’s a big chance I’ll melt in the Californian summer heat and never come back, haha! But hopefully I’ll be able to finish my sessions first :D

This will be the first time I present two sessions at one SQLSaturday. My first session is Level Up Your Biml: Best Practices and Coding Techniques. Depending on your previous experience with Biml and C#, this is an intermediate or advanced session. I’ll cover things like code management, LINQ and how to create your own C# classes and methods.

If you’re new to Biml, you can get an introduction to Biml from Bill Fellows (@billinkc) who will be presenting his
What is Biml and why are SSIS developers excited about it?
session before mine. I definitely recommend attending, Bill is a great speaker :)

My second session is Tools and Tips: From Accidental to Efficient Data Warehouse Developer. This is a fun, fast-paced session with a whole bunch of tips and tricks. I don’t really go into details on anything, but I hope that new developers can pick up a thing or two. And here’s a little secret for you: I will be giving away a free software license to one lucky attendee in this session! And maybe a book or two. And definitely some Norwegian chocolate if you want to try it.

Outside of my own sessions I really want to attend Who needs SSAS when you have SQL? and finally see Meagan Longoria (@mmarie) present live.

Hope to see you at SQLSaturday Sacramento this weekend, and please come and say hi if you see me! :)

Goodbye Comfort Zone! – Starting a New Job

Right now, as I write this, I’m between jobs. Earlier today I finished my last day as an in-house data warehouse solutions architect and business intelligence developer. Tomorrow I’m starting my new job as a technical architect in a consulting company. It’s sad to say goodbye to wonderful coworkers, but it’s also very exciting (and scary!) to start a new chapter in my life.

Continue reading →

Goodbye 2015, hello 2016!

Happy New Year 2016! :)

Happy New Year 2016

2015 was a year of highs and lows for me. I did so many things for the first time and really pushed myself out of my comfort zone. I made new friends and grew closer to old friends. At the same time I struggled more than ever with my old enemies depression, insomnia, migraine and impostor syndrome. All in all, I guess you can call it “life” :)

Continue reading →

Stop assuming wrongly and start assuming responsibility (T-SQL Tuesday #56)

T-SQL TuesdayT-SQL Tuesday #56 is hosted by Dev Nambi (@DevNambi) and the topic is assumptions: Your assignment for this month is to write about a big assumption you encounter at work, one that people are uncomfortable talking about. Every team has an elephant in the room. What happens if these big guesses aren’t true?

Stop assuming wrongly
“If you make an assumption, you suppose that something is true, sometimes wrongly.”

We’ve all assumed wrongly at some point. While it’s not always a big deal, sometimes the result can be disastrous. I’ve accidentally deleted all the weekly data in our production data warehouse because I assumed wrongly. (Thank goodness my assumption that we had working backups was correct!)

Most of the time I’m not aware that I make assumptions until something goes wrong, like when I realized I had deleted all that data. That’s when I stop and ask myself why I didn’t ask more questions, why I didn’t do more research, why I didn’t triple-check the logic?

The answer to why I assume wrongly is usually time. In the world of business intelligence there are just not enough hours in a day. When a business user asks for new data or a new report, their answer to “when do you need it?” is usually “yesterday”. We all want to deliver as much as possible in the shortest amount of time, which often leads to everyone making some kind of assumption without actually being aware of it. Business users assume IT knows all the business rules (“that’s supposed to be a negative amount”), IT assumes the business users have specified all requirements in detail (“that’s not in the requirements”), and we don’t take the time to sit down and go through it together.

Which leads me to my next point:

Start assuming responsibility
“If someone assumes responsibility, they begin to have responsibility.”

We need to take our time to collaborate, to ask those questions, to do that research and to triple-check that logic. Don’t assume that everyone else knows what you know, but share your knowledge. Don’t just assume that things work, but see how you can improve them. Work together.

I’ll start with me and make this a goal for me at work :)

Interviews as Learning Experiences (T-SQL Tuesday #54)

T-SQL TuesdayT-SQL Tuesday #54 is hosted by Boris Hristov (@BorisHristov) and is all about interviews and hiring.

I have a confession to make: Once in a while I say yes to interviews, not because I’m actually looking for new opportunities, but because they’re both fun and challenging.

For me, it’s a great way to learn and grow. I haven’t walked out of a single interview without having learned something new about myself, a technology or the industry I work in.

Going to interviews forces me out of my comfort zone and makes me feel stressed, nervous and a little scared. Sometimes I get questions that I don’t immediately know the answer to and I get flustered. Sometimes I knock over water glasses or burn my hands on hot coffee and make a complete fool of myself. But every time I go to interviews I get a little better at small talk, calming my nerves, thinking on my feet, handling unexpected situations, structuring my thoughts and formulating answers.

It’s a great opportunity to reflect upon my own situation and where I want to be in a year or two. It gives me a peek into what skills are needed and wanted right now, and if it’s a technical interview I quickly find out which skills I need to improve.

My best interview happened early in my career, it was just supposed to be a first introduction interview for a junior developer position. Halfway through the interview I mentioned that I like to challenge myself to learn from the experience, and the interviewer promptly decided to follow up on that statement: “What would you do if we gave you a challenge right now?” (I couldn’t really say no, could I?)

The challenge was to skip right into the second, technical interview without preparing. I had to look at a screen capture of a website and explain the HTML and CSS I would use to replicate it, I had to draw data models and SQL queries on a whiteboard, and I had to guess my way through some JavaScript – and it was fun. I left the interview feeling proud, not because I did well (I forgot important things and made mistakes), but because I was thrown into a new situation and handled it better than I had feared.

The opposite experience was when I was still a student and had a series of speed interviews in one day. They lasted ten minutes and you had three minutes to introduce yourself, three minutes to listen to the company introduction, and the rest of the time to ask questions. The first speed interviews went really well. I grew more confident and didn’t feel like a complete nervous wreck anymore, but as I approached the next table and saw three very serious men in suits stare at me I could feel my palms getting sweaty again. Thankfully they never noticed that, because none of them even wanted to shake my hand. They told me to sit down, grabbed their pens and stared at me in silence. I took that as my cue to introduce myself and spent the next three minutes telling them about my background and why I had applied. When my three minutes were up they looked at each other, looked at me, looked at each other and finally said: “You know that there are mostly men working in this industry, right? How are you going to handle that?”

My jaw dropped to the floor. Inexperienced and flustered, I answered as best as I could that I was used to working and studying with guys and that it had never even been an issue before. They looked at each other again, sighed, looked at me and said: “Well, we don’t have any more questions, so you can just go.” What? I looked at my watch and saw that we still had more than five minutes left, but it was so uncomfortable to sit there that it was better to leave early. So I got up, utterly embarrassed, and zigzagged my way out of the room trying to ignore the stares from everyone still in the middle of their speed interviews.

It is by far the worst “interview” I have ever been to. I felt small and ashamed, but it was also when I promised myself that I would look at each interview as a learning experience. It also made me bring my “I’ll show them!” attitude to the next interview – and that next interview got me my first job :)

Page 1 of 2 1 2