Moving & Starting My Own Co

Friday was my last day at my current job. I joined Pariveda Solutions 2 years 8 months ago with little programming experience. True to form and promise, I was thrown in the deep end on day two. A few months later, I felt like I was beginning to get my feet under me. A few months after that, I created a new website for a nationwide electronics retailer from top to bottom. Six months after that I was managing the deployments of 10+ applications to five different environments in Windows Azure for a major health insurance broker as well as training up some of the new guys. Nine months ago I was given my own team of five developers; we created a new website for the aforementioned insurance company that would bring in a new line of business year around in a normally seasonal industry. Three months ago I was made Tech Lead of their entire team of 14 developers to continue building out functionality across all of their sites hosted in Azure. Two weeks ago I gave my notice. Two days ago I said my goodbyes.

If you're thinking I quit because I want to slow down the pace I've been on for the past 2 years and 8 months, you'd be wrong. The reason I quit is because we're moving to Denver. It's been a long time dream of Kate and I's to live in Denver and it's finally happening. I'll be starting my own company and Pariveda has offered to be my first client.

How long will I be self-employed? How long will we live in Denver? Only God knows. For now, I'm just excited to get to see the mountains again, to go camping under stars you can point to, to start my own company and learn that process, and to keep writing code for clients.

Now that I'm officially out on my own...Need a software developer? Need a Tech Lead? Hit me up at If you're curious about the company name, here is a brief explanation: I once read a Quora post on lessons from Stanford Professor John Ousterhout. One of them was titled "A little bit of slope makes up for a lot of y-intercept" and it had a profound impact on me. If you read the first paragraph of this post, you know that my y-intercept was seriously lacking 2 years 8 months ago. Nonetheless, I've done by best to maintain as steep a slope as sustainable (note I didn't say possible...this is important). That strategy has served me well and I've seen the fruit in my own life. So, how does m not b play into this? You've probably guessed it by now, but if you haven't...the equation of a line is y=mx+b where m is the slope and b is the y-intercept. Thus, it is m, not b, that is the important part when measuring oneself. It is also important when deciding on a potential consultant. I may not know what the other guy knows today, but I aim to surpass him in the tomorrow.

So that's the latest from me. It is bitter to leave Pariveda, sweet to move to Colorado. I have nothing but the utmost respect for my colleagues; they are an immensely talented group of people doing amazing things for their clients. Pariveda gave me the opportunity of my lifetime and I hope I made the most of it. I now look forward to capitalizing on the knowledge I've gained and seeing what it can do for me along the Front Range.

portrait title

About Scott

I am a software engineer from Bozeman, MT enjoying the slightly warmer climate of Colorado. I think code can change lives. I think lives are worth changing. I write code.

You can find me on Twitter, LinkedIn, , and Github.