Back in July of 2014, a recruiter messaged me on LinkedIn and asked if I would be interested in interviewing for a position working with Atlassian software. I normally rejected such messages, but I decided to accept the call.
It took 20 minutes for her to mention that the company recruiting me was Adaptavist. I was absolutely floored. I had been working with Atlassian software for 7 years at that point, and Adaptavist was a big deal in the space. I had been looking at some of their plugins for a while and I admired them as a company, so I was shocked that they wanted to recruit me.
2 months and 6 interviews later, they offered me a job and I joined in October 2014. I actually started working with my first consultancy client in September, covertly taking calls from my office at the university because that client was so desperate to get me in. For the first time in a long time, I was doing interesting and challenging work that I enjoyed and that was valued by my customers and colleagues. And I was doing it within the boundaries of 40 hours a week and didn’t have to work nights or weekends.
When I attended my first Atlassian Summit in 2015, Adaptavist was asked to stand up during the partner day keynote, and we were recognized while everyone applauded. I felt like a friggin’ rock star. I had arrived, and I hoped never to leave.
I have a project at work I have been dreading. Our current wiki is running on Ubuntu JeOS and PostgreSQL, and we are moving to Microsoft Windows Server 2008 and Microsoft SQL Server. The move to Windows was frustrating, but pretty easy–to be perfectly honest, getting it to all work on Linux was a lot more difficult, but that was partially because I had no friggin’ idea what I was doing 2.5 or so years ago when I started working with Confluence. But I could handle that OK. Moving to MSSQL is a bit terrifying though. I’ve been avoiding it for a week.
Confluence was built to work with Postgre, and it works very well. There’s no configuration, no real tricks to it. You just drop the driver in the right folder, click the install button, and go. For MSSQL, though, there are a lot of hoops to jump through, both in regards to software configuration and the database setup. What’s more, the DB is running on Enterprise System‘s SQL Server, which is kind of a Big Deal. This isn’t me just playing around with a local toy anymore, so if I screw something up, it’s going to be a little more noticeable.
This afternoon when I began working on it, though, I had already spent about 4 hours researching the topic. I had read all the comments on different wiki pages and I had all my notes. I followed the directions Very Carefully.
And it worked.
I was pretty nervous when it took over two minutes to connect to the DB and get set up, which it did silently so I had no idea if it was about to stab me or not. But in the end, it did connect, and now I’m getting ready to push a ton of data to it.
That’s my next big hurdle: will the data pulled from PGSQL push into MSSQL without a hitch? According to what I read, it should as long as the DB username is the same, but I’m still nervous. Regardless, I want to offer public thanks for all those early adopters who blaze the trails I hesitantly step down.