<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Clio Labs on Medium]]></title>
        <description><![CDATA[Stories by Clio Labs on Medium]]></description>
        <link>https://medium.com/@cliolabs?source=rss-b9dad36f87a6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oVY3zMlSDah0HR9HA3Aolw.png</url>
            <title>Stories by Clio Labs on Medium</title>
            <link>https://medium.com/@cliolabs?source=rss-b9dad36f87a6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 09:21:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cliolabs/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A journey from electrical engineer to mother and software developer]]></title>
            <link>https://medium.com/clio-labs/a-journey-from-electrical-engineer-to-mother-and-software-developer-36361e20f632?source=rss-b9dad36f87a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/36361e20f632</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[team-clio]]></category>
            <category><![CDATA[transitions]]></category>
            <category><![CDATA[motherhood]]></category>
            <dc:creator><![CDATA[Clio Labs]]></dc:creator>
            <pubDate>Mon, 20 Jan 2020 19:03:38 GMT</pubDate>
            <atom:updated>2020-01-20T19:05:59.259Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This story was originally published on </em><a href="https://medium.com/the-chic-geek/a-journey-from-electrical-engineer-to-mother-and-software-developer-2a42ad37c2f2"><em>The Chic Geek Blog</em></a><em>.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RhquDJSAQ8238WkhqBdqVg.png" /></figure><p>With over 5 years of building a strong community for women in technology, Chic Geek is here to sit down with long-time supporter, Clio. We wanted to explore their commitment to building diverse teams and developing employees’ growth, which contributes to high performing teams and transforming the practice of law, for good.</p><p>We sat down with <a href="https://www.linkedin.com/in/somaiehbeladi/">Somayeh Beladi</a>, a Software Developer at Clio who holds a PhD in Electrical Engineering.</p><h4>CG: Can you briefly describe your background and how you got exposed to the technology space?</h4><p><strong>Somayeh</strong>: I grew up in Iran, where in high school, you need to choose a scientific focus. I enjoyed algebra and mathematics a lot and it was my strongest subject, so I decided to choose mathematics. To get into a university, I had to take a challenging test to decide what my future will be. This got me into electrical engineering, which was a very popular field.</p><p>After university, I received a scholarship from Australia to complete a PhD in Electrical Engineering. Afterwards, I became a post-doc researcher at the University of Calgary. During this time, I decided not to stay in academia and work in the industry because I was more interested in developing software solutions in industry more than writing papers and developing methods. I joined Garmin as an embedded software engineer to develop software for controlling embedded systems including hardware and mechanical parts. I mainly worked on algorithm design for Garmin fitness devices for 5 years. Afterwards, I was looking for a new challenge and I wanted to expand on my software skills as I had realized that this was my true interest, so I decided to start a career as a software developer for web applications. It was a big change and I knew I would have to work hard to gain the required knowledge and skills but I’m very happy that I made this choice and pursued what I enjoyed most.</p><blockquote><em>I believe what helped me most is the culture we have at Clio which welcomes people with different backgrounds and builds diverse teams.</em></blockquote><blockquote><em>Clio invests in people and we all help each other learn and grow in our careers. This is how we build strong and successful teams.</em></blockquote><h4>CG: So, what brought you to Clio?</h4><p><strong>Somayeh</strong>: Joining Clio was a very big change because I had no experience in web development and most of my knowledge of embedded development was not applicable. I had to start from scratch and learn about web development, new languages like HTML and CSS and databases. It was all very new to me, but the reason joined Clio was its philosophy to help me learn.</p><p>Everywhere I interviewed asked about my past experiences and my abilities, but at Clio we spoke more about my potential. I did not know Ruby, but during my interview at Clio, the lead developer said they could teach me. I have done interviews with multiple companies and usually companies are only interested in hiring experts and are not interested in investing in applicants. Clio helps us gain new and valuable skills through pair programming, which has helped me improve my problem solving skills and learn how to write high quality code. Clio is happy to invest in me, which motivates me to return the investment and demonstrate my potential.</p><p>The other thing I like about Clio is how much everyone trusts each other. <a href="https://www.tablegroup.com/books/dysfunctions"><em>The Five Dysfunctions of a Team</em></a> mentions how you should have enough trust with your team to comfortably talk about what you don’t know. I have been very open and honest about what I don’t know, and my teammates are so willing to listen and teach me.</p><h4>CG: How did your background help you as a software developer?</h4><p><strong>Somayeh</strong>: I always aim to write high quality code by being very cautious of testing my code, writing detailed test plans and thinking about edge cases. When I came to Clio, my testing skills were a valuable addition to my team.</p><p>My achievements in the past and my hard work ethic have helped me become confident that what I don’t know, I can learn. I come to work early, so that when I go home, I can focus on my family. When my kids go to sleep, I can study more and fill any gaps.</p><h4>CG: What do you enjoy most about your role as a software developer?</h4><p><strong>Somayeh</strong>: What I enjoy most is building something that other people can use. I have a lot of friends and relatives, especially women, who have wanted a divorce or custody of their kids. One of the things that makes this difficult is that a good lawyer is very expensive. Our mission at Clio is to change the practice of law, for good, which has an intentional double meaning. I’m inspired by the belief that transforming the legal industry will make law firms more efficient, driving down prices and ultimately providing access for everyone in need of legal services, including these women.</p><p>This is not a goal that we can achieve in a month or year, but we’re taking baby steps and moving toward that goal. This keeps me motivated.</p><p>The other thing I like about my job is that there’s a lot to learn. I am working with constantly changing technologies and it’s a lot of work to keep my skills up to date, but I really enjoy continuous learning. When I think about what I conquered last year, I realize I learned and accomplished a lot. The environment and people at Clio also keeps me motivated because they are so friendly and supportive.</p><h4>CG: What makes Clio different from other organizations in their approach to building diverse teams?</h4><p><strong>Somayeh</strong>: Acknowledging that there is a problem with a lack of women in tech is a big step, but actually doing something about it is more important. In the last 6 months of 2018, Clio‘s software development team moved from 13% women to 25% women. Today, our software development team is 27% women. Our Calgary office, which is almost entirely software development, is 34% women. Clio is making a big effort to build a diverse team and an inclusive culture, and I can’t say enough how much I admire that.</p><p>Every week in the software development department , we complete a survey from our vice president of engineering, which asks us happy we are with our growth, if we are learning enough, if we feel our team’s work is of high quality, and if we feel we are experiencing growth personally. Every week, I’m amazed that he cares enough to ask every individual about how we’re doing in this way.</p><p>Clio believes it is possible for an organization to be both human and high-performing. There are a lot of opportunities to learn at Clio, such as book clubs, internal mentor/mentee programs and Slack channels where you can ask your questions or for help whenever you are stuck. People are always very responsive and happy to help. We also have a full time internal performance coach.</p><p>People at Clio are friendly, and there are a lot of them ready to help and teach you, which is amazing. You never feel bad or embarrassed. Even if you ask what you think is a silly question, people will understand. Clio is willing to teach you, and they support us with education, conferences, courses and books as well.</p><h4>CG: What is it like studying and working in a field where women are the minority?</h4><p><strong>Somayeh</strong>: In university, I remember there were 100 boys and 29 girls the year I entered. I always noticed there were fewer women in this field, but I was used to it and accepted that this is the way that it is.</p><p>After joining Clio, I found it very interesting how some people in the company were taking the initiative to change this. They believe that the status quo is not good enough and they are determined to improve the gender diversity of our engineering team. Although I had previously accepted the status quo now I’m now excited to play a role in changing the industry to make it more welcoming and supportive for women and to encourage other women to pursue careers in tech.</p><blockquote><em>I make sure when I’m with them, we’re having fun.</em></blockquote><h4>CG: And what is it like working while raising a family?</h4><p><strong>Somayeh</strong>: The bottom line is, having a child and working is hard. Maternity leave makes it easier to spend a year with your baby, but when you go back to work, it’s very challenging. People don’t consider that you had a one year gap and they don’t realize you’re not the same person. You have different concerns now.</p><p>Also, it’s hard when you’re leaving the house and your kids ask you to stay at home and play with them. Sometimes this makes me wonder if going back to work was the right decision. But I believe that I am a better mom for my kids when I am happier and having a successful career is one of the essentials for me to be happy.</p><p>When I go home I make sure I’m in a good mood and present and I try to spend a lot of time with them. The trick for me is to make sure I have quality time with them. Even if I don’t spend the whole day with them, I make sure we have fun and play games together. That helps me balance work and family.</p><p>I’m currently reading <a href="https://www.insight-book.com/"><em>Insight</em> by Tasha Eurich</a>, and she says that whenever you’re having a hard time, it’s good to think of the things that are amazing in your life and your achievements. When I’m feeling down, my kids bring me joy and the confidence that I’m a good mom.</p><p>The most important thing for me are my two kids and husband, and everything is built around that core. My son Rodwin is 4 1/2 years old, and my daughter Leanna is 2. They are the joy of my life and my everything. One of the reasons I go to work is to teach my daughter to pursue her professional goals and follow her dreams. I try to make sure that I don’t speak negatively about going to work, so it doesn’t give her the impression that it is a bad experience. I want to encourage her to pursue a career as well — one which aligns with her desires and hat she enjoys doing.</p><h4>CG: What’s your advice for someone who wants to switch roles in the technology space?</h4><p><strong>Somayeh</strong>: Take advantage of your opportunities. Everyone can learn anything.</p><p>Two months ago, I registered for an online bootcamp on advanced web development and the cost was only $18. Take advantage of online courses and online resources, because they’re super accessible. You can complete them in your own time and they’re so inexpensive that you can try different fields and see what is more fun for you and what you’re enjoying most.</p><p>I spent 4 months using Udacity to get a degree in machine learning. I also have been taking different courses on Coursera or Udemy such as “<a href="https://www.udemy.com/the-advanced-web-developer-bootcamp/">The Advanced Web Developer Bootcamp</a>” and “<a href="https://www.udemy.com/course/the-complete-ruby-on-rails-developer-course/">The Complete Ruby on Rails Developer Course</a>”.</p><p>Education is evolving and you can obtain a high quality education online, so why not? Just try and see if you like it.</p><h4>CG: Can you share any final words to our community about getting into tech or being a software developer?</h4><p><strong>Somayeh</strong>: I admire people who see something and want to change it. I never considered trying to improve gender diversity in tech, and people at Clio are so driven to do that. Women usually under-evaluate our performance. We tend to think we’re not good enough or capable enough. I believe we need to pursue what we enjoy most and if tech is what we like, then we need to believe that we’re strong and capable.</p><p><a href="https://medium.com/u/2b2802d362b3?source=post_page-----2a42ad37c2f2----------------------">Clio</a> is a dedicated partner with <a href="http://thechicgeek.ca/">Chic Geek</a>. We love featuring women in tech to inspire the community. If you’re interested in what we do, check out our <a href="https://www.thechicgeek.ca/events">MeetnTech</a> events!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36361e20f632" width="1" height="1" alt=""><hr><p><a href="https://medium.com/clio-labs/a-journey-from-electrical-engineer-to-mother-and-software-developer-36361e20f632">A journey from electrical engineer to mother and software developer</a> was originally published in <a href="https://medium.com/clio-labs">Clio Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#TeamClio: Kimberly Westvelt, Development Manager]]></title>
            <link>https://medium.com/clio-labs/teamclio-kimberly-westvelt-development-manager-43294544ea71?source=rss-b9dad36f87a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/43294544ea71</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[team-clio]]></category>
            <dc:creator><![CDATA[Clio Labs]]></dc:creator>
            <pubDate>Tue, 13 Nov 2018 17:01:04 GMT</pubDate>
            <atom:updated>2018-11-16T00:32:46.268Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uBdw8P54tnmm2qr2BgPqYg.jpeg" /><figcaption>Kimberly in Clio’s Calgary office.</figcaption></figure><p><strong>Who are you?</strong></p><p>I am a development manager at Clio. I grew up in Saskatchewan and I moved to Calgary to start working as a software developer. I try to stay active and get outside (two things that help me feel grounded). Lately, you would most likely find me at a climbing gym, in a ballet class, or walking or biking along the river after work. I take the occasional trip to the mountains for an easy hike or a day snowboarding. I try to escape somewhere hot at least once a year, preferably somewhere I can scuba dive.</p><p><strong>What do you do at Clio?</strong></p><p>I help build and lead great teams. I reach out to potential candidates, tell them about my experience at Clio, and help them determine if Clio is a place they would excel and love to work. I interview candidates, determining if they have the potential to become the type of leader we look for at Clio. I create onboarding plans for new Clions so that they make connections throughout the company, understand our project and goals, and understand how our team works. I work closely with each developer on my team to understand their career goals, help them develop a plan to get there, and coach them along the way. I provide feedback to my team on what they are doing great, what they need to improve, and help them identify opportunities to stand out. I work with my fellow Product Manager and Product Designer to ensure that the team has purpose, has a plan to achieve our goals, and is executing well. I work with my dev team, writing code, doing code reviews, testing, and deploying.</p><p><strong>How long have you worked at Clio?</strong></p><p>I joined the Clio team in October 2017 as a back-end developer, and I moved into a development manager role in May 2018. After hearing so many good things about Clio from a previous co-worker and meeting a bunch of wonderful Clions, I knew it was somewhere that I could learn, have fun, and explore new career opportunities.</p><p><strong>Which office are you in?</strong></p><p>The best one! YYC. We have spectacular mountain views, and I’ve pet at least 4 different dogs in the elevator (including a fluffy puppy named Donut).</p><p><strong>What led you to become a software developer?</strong></p><p>It all began with Mr. Durham’s computer class. He taught us BASIC, and let us pick our own projects. I made a pretty awesome horoscope program that included some multi-coloured fireworks! I was pretty proud. I continued with computer science courses throughout high school and chose to follow that path after some encouragement from my teacher.</p><p><strong>What led you to become a development manager?</strong></p><p>I dabbled in some business analysis and project management alongside my development role prior to coming to Clio, and those experiences lead me to want to explore more opportunities. I made up my mind that I wanted to pursue the development manager role at Clio, I communicated that during my interview process, made it a goal on my career plan with my development manager, took the opportunity to lead a project to demonstrate my skill, and the rest is history.</p><p><strong>What does your average day look like?</strong></p><p>I live five blocks from the office, so my day starts with a walk, a stop in at my favourite cafe, taking in the beautiful mountain view from my desk, and a quick catch up with the Clions that sit close to me. I usually grab lunch from somewhere along Stephen Ave with one of my teammates, or partake in the free Friday lunch with the entire office. I love the fun, friendly atmosphere at Clio, but my work is quite serious. My team is wrapping up a payment processor migration for our North American customers. Our main focus is protecting our customers data while ensuring that Clio’s ability to collect payment is not impacted. I’ve worked with my team throughout this process to ensure that our Security team has reviewed and approved our plan, we can tell at a glance how many customers have been migrated and if we are experiencing problems processing payments, and we have the ability to fallback if problems occur. We take our responsibility to our customer and to Clio seriously, and ensure that everything we do is thought through and tested. We rely on one another to speak up, ask questions, and challenge each other.</p><p><strong>What drew you to Clio originally?</strong></p><p>A former colleague who works at Clio reached out to me at just the right moment. I was looking for an opportunity to work with a team that I could have fun with, would challenge me, and would help me grow. I wanted to be at a company that would support me in exploring a new role. I wanted to be in an environment that values transparency. Each person that I met from Clio painted a picture of a company where this and much more was possible.</p><p><strong>What do you love about your job?</strong></p><p>My favourite part of being a development manager so far are the moments when I feel like I’ve helped one of my team gain confidence in themselves. The best part of coming to work everyday is being surrounded by people that make me laugh, care deeply about solving problems, and support one another.</p><p><strong>What’s been your favourite moment at Clio?</strong></p><p>Putting forward my first recommendation to promote one of the developers on my team, sharing with her all the ways that I observed her making an impact on the organization, and getting to deliver the good news!</p><p><strong>What advice do you have for anyone interested in working at Clio?</strong></p><p>Be ready to work hard, learn, say the hard things, and have a lot of fun.</p><p><strong>What did you want to be when growing up?</strong></p><p>There wasn’t a constant, but as a kid I dreamt of being a professional ballerina, an olympic swimmer (butterfly was my best stroke), a business lady with a suit and a briefcase, and I wanted to own a house with an entire level that was a forest, so that I could befriend some bears.</p><p>I also really liked my computer. :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*borOXeW_RYMWh1Bc" /><figcaption><em>Actual excerpt from Kimberly’s journal on January 10, 1989.</em></figcaption></figure><p><strong>What’s a fun fact about yourself that no one knows?</strong></p><p>I’ve jumped off a boat in the open ocean for an impromptu swim with a huge manta ray.</p><p><em>Kimberly Westvelt is a software development manager at Clio. Her team is currently revamping Clio’s subscription system. Before Clio, she spent six years at a software consultancy, working as a developer, business analyst and project manager. Kimberly likes to be outdoors (mostly when it’s warm and sunny). She’s an advanced open water diver, has swam alongside whale sharks, dolphins, and manta rays in the open ocean, and recently encountered white tip reef sharks on a dive in Hawaii.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43294544ea71" width="1" height="1" alt=""><hr><p><a href="https://medium.com/clio-labs/teamclio-kimberly-westvelt-development-manager-43294544ea71">#TeamClio: Kimberly Westvelt, Development Manager</a> was originally published in <a href="https://medium.com/clio-labs">Clio Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Support Agent to Developer]]></title>
            <link>https://medium.com/clio-labs/from-support-agent-to-developer-4c098453e0fa?source=rss-b9dad36f87a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c098453e0fa</guid>
            <category><![CDATA[team-clio]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Clio Labs]]></dc:creator>
            <pubDate>Tue, 02 Oct 2018 23:00:45 GMT</pubDate>
            <atom:updated>2018-10-12T02:48:54.010Z</atom:updated>
            <content:encoded><![CDATA[<p>A defining aspect of Clio’s culture is the core value of Living a Learning Mindset. At Clio, Living a Learning Mindset means that we’re always open to learning and that we, as a company, aim to be deliberately developmental. In addition to the developmental investments that our Talent Acceleration team puts together, such as <a href="https://www.linkedin.com/pulse/how-clio-deliberately-investing-leadership-scale-allison-mcgerrigle/">Basecamp</a> and <a href="https://www.linkedin.com/pulse/four-ways-performance-coach-can-augment-katie-wyka/">Performance Coaching</a>, Living a Learning Mindset manifests in the form of the “Clio Climbing Wall”.</p><p>At Clio, you are taught early on that you own your career. We believe that one’s career is not limited to the traditional career ladder - each Clion has their own unique Clio Path which can involve moving up, down, left, right, or diagonal along the “Clio Climbing Wall”. There are countless of examples of Clions who have taken this to heart. For two of our software developers, this has been their journey. Starting their careers at Clio as customer support specialists, they are now integral to our engineering organization as software developers. It’s been exciting to watch them navigate the Clio Path from support to technical escalations to engineering with the support of their teams, one-on-one mentorship and a lot of personal grit and determination! These are their stories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dSQ3A4WAAbxUqgXD7LFH3g.jpeg" /><figcaption>Drew &amp; Ripley in Clio HQ in Burnaby, BC.</figcaption></figure><h3>Drew Goddyn, Junior Software Developer</h3><p><strong>When did you decide “I want to be a developer,” and then how did you make that happen?</strong></p><p>I always knew that I wanted to be a developer. When I first started in the support department, Clio was a smaller place than it is now — the support department was positioned right next to development, and my role involved working closely with individual developers to fix bugs. It was during this time that the role of a software developer was made much more clear and intriguing for me, but it still wasn’t obvious to me how one actually “becomes” a developer.</p><p>I completed a diploma in computer science over 10 years ago, but after graduating, I failed to make use of my education and ended up working in other roles. As time went on, it became less and less clear to me how I could get my foot in the door. Working closely with developers in my support role prepared me to think like they do, and when a QA (quality assurance) position opened up I immediately jumped on the opportunity to work even closer with developers.</p><p><strong>What was the most challenging part of starting to work in Clio’s established code base or working with Ruby in general?</strong></p><p>Having been 10 years since I got my diploma, taking on the QA role required me to basically teach myself software development again. The biggest challenge was trying to follow tutorials and then relate them back to how Clio works. Unfortunately, what every tutorial fails to state in the opening paragraph is that the real world is nothing like the carefully manicured apps I was building by following the guides. There’s a huge difference between building an app from scratch where you understand every intricacy and line of code to jumping into a very large codebase (that’s ever-changing) built on top of years of technology changes and code debt.</p><p>Another challenge is simply not knowing what you don’t know. I focused my early days on learning languages, frameworks and syntax, but that left me a bit clueless when topics around anti and design patterns arose. “Watch out for that N+1 query!” they would shout while I nodded with a blank face.</p><p><strong>How did or could your coworkers make the biggest impact in your onboarding experience?</strong></p><p>The single biggest thing co-workers can do for a new junior developer is to expose their own vulnerabilities, as well. I think every developer can closely relate to imposter syndrome and the daily cycles of “I got this!” and “I don’t know what the hell I’m doing.” It was comforting to have teammates who would reassure me that everybody feels the exact same way as soon as they step into an area of code they aren’t familiar with. Luckily, I was already familiar with a lot of my teammates as I’d been around for a while. I could see being in that situation where you’re also completely new to a company would make it extra challenging.</p><p><strong>What has been your experience with pairing, code reviews and documentation?</strong></p><p>Our team very much believes in pairing as a way to increase velocity and share knowledge. We’ve recently started <a href="https://softwareengineering.stackexchange.com/questions/147664/what-is-swarming">swarming</a> whenever we begin tackling large unknown problems to ensure we all understand and find the best solution possible. I think our first reaction to any kind of pairing was thinking that it would make us half as efficient as we’d basically be losing a developer in parallel. What quickly became apparent is how much faster we are when we’re working with someone else. Not only is the other person an extra mind to tap for solutions, but just the fact that someone else is there with us forces us to focus and shut out external noise, if for no other reason but to respect the other person’s time.</p><p>When it comes to code reviews, I’ve personally always found doing them in a timely manner challenging, especially when its an area of code I’m not familiar with (which is everything for a junior developer). What I found most important was using them as a learning tool rather than just something I need to get done for someone else. It’s been very valuable to ask lots of questions and engage with the developer directly to have them explain or walk me through concepts I don’t understand.</p><p><strong>Did you experience imposter syndrome when you became a junior developer?</strong></p><p>Oh god, yes, and I still do on a regular basis. Coming to terms with feeling inadequate is one of the first things you need to do as a developer. It’s so easy to feel like everyone else ‘gets it’ and you don’t, especially when you’re surrounded by so many super smart people, as I am at Clio. The way I approach being a junior developer now is simply to learn and absorb as much feedback and tips as possible while showering co-workers with questions. When it comes down to it, that feeling is really what drives you to learn more and to seek out creative solutions, and in that sense I don’t think imposter syndrome should ever really go away, we just need to learn how to harness it.</p><p><em>Drew Goddyn is a junior software developer on the Documents team at Clio, and comes to work with his 3-year-old labradoodle named Ripley. At home, he’s learning the ropes of being a new parent to a human tornado while continuing to take a deep dive into the world of Ruby.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OuROteQUyY2eU_3udXZ4mQ.jpeg" /><figcaption>James in Clio HQ in Burnaby, BC.</figcaption></figure><h3>James Goertzen, Software Developer</h3><p><strong>When did you decide “I want to be a developer,” and then how did you make that happen?</strong></p><p>I started at Clio in our Support team, and quickly moved on to our Technical Escalations team, which is sort of like a second tier of support. After a year and a half on our Technical Escalations team, I was starting to feel like I was hearing a lot about our customers’ issues and desired features but wasn’t really able to address those needs, no matter how much I sympathized with them. This, along with an insatiable desire to learn new skills, drove me towards teaching myself to code.</p><p>I had the great benefit of having a very supportive manager in Technical Escalations behind me as well as a supportive organization at Clio. I spent a few months finding my own way and getting started. Once I convinced them that I was serious about this, I was given the opportunity to be mentored by one of our Staff Software Developers.</p><p>This was probably the the most impactful period of my development as I received a lot of quick, actionable feedback that directed my efforts towards maintainable code as opposed to just working code. My mentor was also one of the few developers that was part of the hiring process at the time, so I got an inside view on the traits that they look for in a junior candidate: receptiveness to feedback, a hunger for knowledge, and high standards.</p><p><strong>What was the most challenging part of starting to work in Clio’s established code base or working with Ruby in general?</strong></p><p>Ruby on Rails is a pretty magic-heavy framework, by which I mean there is a lot of code you don’t have to write to make things work because the framework creates it for you in the background. When I was building my first app, it was incredible how easy it was to put together and get a working website running. The simple features I added basically built themselves, and it was easy to find gems (small extensions built by other developers) that covered some more complex flows like single sign-on.</p><p>Once I started working in the Clio codebase, it quickly became apparent that this magic was only marginally useful in an established site run by experienced developers. It was often the case that a bug would appear that would not seem possible, only to discover that it was Rails trying to be helpful by caching something you needed a fresh copy of, for example. This unexpected behaviour made for some painful early lessons.</p><p>A codebase spanning nearly a decade of evolving code standards and capabilities also has some pitfalls. Learning to read other people’s code well is an invaluable skill because it’s what you’ll be doing for most of your career. All those tens of thousands of lines of code can often be forgotten to focus on just a few important lines that you need to understand to solve the problem you’re working on. Once you get into the mindset of breaking things into bite-size pieces, things get much easier.</p><p><strong>How did or could your coworkers make the biggest impact in your onboarding experience?</strong></p><p>My onboarding experience was a little more drawn out than most. Having already been a part of the company meant I understood how to navigate the departments a little bit, and already knew a number of people I’d be working with. I had the pleasure of working directly with my mentor and a few of Clio’s other most senior developers. I was able to ask the wrong question, and have super smart people direct me to the right question and a thoughtful answer.</p><p>Being comfortable in the environment meant I wasn’t afraid to ask these questions, and I think that was incredibly important to my growth. Creating a safe environment will ensure newcomers don’t suffer in silence with solved problems that just aren’t communicated well.</p><p><strong>What has been your experience with pairing, code reviews and documentation?</strong></p><p>Pairing was a learning experience. It felt strange to have two people doing what seemed like the job of one. But as long as both of you have a decent grasp of what’s going on, it’s amazing how much faster you can identify issues. Even if the skill or knowledge level is uneven, you still have this great opportunity to learn from or teach your pairing partner. The simple questions that come out of trying to understand what is going on often bring up important considerations that end up positively impacting the code.</p><p>Code reviews are probably the single most important aspect of growing as a developer. Building a healthy relationship with feedback was so important in getting confident with my own code, and comfortable reviewing other’s code. When you have thoughtful reviewers intent on helping you, and therefore the team, succeed, you get a gold mine of knowledge and advice with every pull request you submit. Learning to respect your peers, but also being ready to challenge them, helps keep your pride in check so you can fully utilize the experience of your coworkers.</p><p>Documentation was really tricky, and it’s something we’re constantly trying to figure out. We have a number of tools to document issues or techniques and it can be hard to determine where to start looking for answers, or where to record something you’ve discovered. Once you figure out the patterns in documentation, answering questions for yourself by finding them and providing answers to future seekers is hugely valuable.</p><p><strong>Did you experience imposter syndrome when you became a junior developer?</strong></p><p>Absolutely, and I don’t know if it’ll ever go away. In a company that values code quality, you will constantly be surrounded by smart people and it’s up to you to find value in your contribution. I think it’s important to harness this feeling and strive to be more like the people around you that you admire. You will often also find that they are more than happy to impart their wisdom over coffee.</p><p>I found it helpful to bring this up explicitly with my manager in our one-on-ones because they’ve often got examples of how you’re contributing, as well as feedback on how you can level yourself up. As a junior developer, you do have some catching up to do, but it should feel like your manager and your colleagues are eager to get you there (if it doesn’t feel that way, Clio is hiring!).</p><p><em>James Goertzen is a Software Developer on the Payments team at Clio. Born and raised in British Columbia, he can’t wait for Clio to open an Australian office so he can bask in the sun year-round. When he isn’t working to expand his software development stack, or slowly moving the office thermostat higher, he’s probably playing video games.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c098453e0fa" width="1" height="1" alt=""><hr><p><a href="https://medium.com/clio-labs/from-support-agent-to-developer-4c098453e0fa">From Support Agent to Developer</a> was originally published in <a href="https://medium.com/clio-labs">Clio Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#TeamClio: Matt Abraham, Systems Engineer, Production]]></title>
            <link>https://medium.com/clio-labs/teamclio-matt-abraham-systems-engineer-production-ba74ff90693f?source=rss-b9dad36f87a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba74ff90693f</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[team-clio]]></category>
            <dc:creator><![CDATA[Clio Labs]]></dc:creator>
            <pubDate>Mon, 17 Sep 2018 16:46:27 GMT</pubDate>
            <atom:updated>2018-09-17T16:51:34.152Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jEx_qHiSiZszUzOHBV2w1w.png" /><figcaption>Matt Abraham in Clio’s Calgary office. Photo taken by Matt Abraham.</figcaption></figure><p><strong>Who are you?</strong></p><p>I’m Matt Abraham, a prairie-born Canadian that arrived in Calgary by way of Toronto.</p><p><strong>What do you do at Clio?</strong></p><p>I work in the Product team as a Systems Engineer for our production systems infrastructure. This includes the servers where the Clio app runs for customer use, the repository where code is kept, and various systems for managing our email, calendering, testing, and smaller applications. Our 3 mandates inform our guiding principles for the role: the first is to maintain the security, reliability, and performance of our production systems, the second is to ensure an effortless experience for Clio’s developers (remove as many pain points as possible), and the third is to achieve a similar experience for all other Clio employees.</p><p><strong>How long have you worked at Clio?</strong></p><p>It’s been just over a year and a half; everyday is a reminder of how much I have yet to learn, and I love it.</p><p><strong>Which office are you in?</strong></p><p>I work in our sparkly new downtown Calgary office! The building itself started out as “PanCanadian Plaza” in 1982 but underwent a thorough renovation and was recently re-christened as “The Edison”. Clio’s office opened in January of 2018, so prior this this, I worked from home along with all the other Calgary employees. It’s got a little basketball court on one of the upper floors and gym down on one of the lower floors, so there’s no excuse for not getting a little exercise. We started with 10 staffers, but we’ve grown to nearly double that… hopefully, we’ll triple it before the end of the year!</p><p><strong>What led you to this role?</strong></p><p>In the past, I’ve worked in support, as a systems administrator and a network admin. It’s easy to let your current and past experience act as a “filter bubble” and colour your sense of career options as well as your own capabilities. However, as I started to look for other opportunities, I noticed that many of the jobs I had come to expect to see were no longer showing up with the same frequency, i.e. the traditional systems administrator role had changed as cloud services had grown in popularity. I found I had to shift my perspective and start to consider some of these roles that I had originally dismissed and being beyond my expertise.</p><p><strong>What does your average day look like?</strong></p><p>It’ll come as no surprise that my day starts with coffee. Then, our group handles incoming requests from developers, so if I’m the “Air Traffic Controller” on duty that week, I’ll start with checking to see if any new requests have been received. If I’m not the Air Traffic Controller that week, I’ll work on a variety of different projects each with its own dependencies and deadline, so it’s a matter of prioritizing those and working on the ones that require the most immediate attention. The variety is fantastic: one assignment has me spinning up Docker containers on my local machine and writing Ansible playbooks while another has me going through Buildkite pipelines and WPEngine configuration. et another project has me working with a colleague to figure out how a Heroku dyno can post graphs generated in real-time to a Slack channel using data from another service. Am I involved with Deployment pipelines? Cloud services? Configuration management? Monitoring? Containers? Ruby? Ansible? Yes!</p><p><strong>What drew you to Clio originally?</strong></p><p>I had been working at a software company that was following a much more traditional approach to software development and delivery, and I was looking for a change. I came across a job posting online for this position, and the description really intrigued me. After having a meeting with Remi, the Director of Systems Engineering, Production, I was even more interested. Over a lunch, Remi described some of the problems they were working on, and I found my thoughts alternating between, “I think I could fix that,” and “I don’t recognize most of the words in that last sentence.” Plus, he paid for lunch!</p><p><strong>What do you love about your job?</strong></p><p>I love that I had a hard time answering the “average day” question earlier! Technology is always changing, and the role captures that. I’ve always been drawn to jobs that weren’t limited to a small series of repetitive tasks, and this job is about as far from that as you can get!</p><p><strong>What’s been your favourite moment at Clio?</strong></p><p>The previous tenant in our HQ offices was a large technology company, and when we moved in, there was quite a bit of legacy infrastructure left behind. Early on, there just wasn’t time to deal with it, so the company worked around it. Finally, though, things came to a head, and OIT (Office IT) was swamped with assisting the rapidly growing company, so we decided to team up to tackle the task of reorganizing the server room, rewiring the switches, cleaning up the A/V infrastructure, etc. Clio flew all the remote team members down to HQ, and we joined up with the local team members (both our team and OIT) to re-rack equipment, test cables, climb up on ladders and poke through the ceiling tiles, and simply re-do a good portion of the company’s infrastructure. For an entire weekend! I remember sitting in a restaurant with the rest of the group that Saturday evening realizing that despite how talented this group was with their regular roles, they didn’t think twice about getting completely covered in dust as they pulled ethernet cables above ceiling tiles: no egos, no complaining, just a bunch of hard work, good laughs, and great food (Clio kept us well fed!). It was a great opportunity to get to know my team better.</p><p><strong>Have you had any important mentors in your life?</strong></p><p>My parents certainly provided much of my guidance early on, but beyond that, I haven’t had specific individuals I would consider mentors. I will, however, shamelessly steal habits from others I admire, and I’ve caught myself duplicating things my co-workers have done in presentations or their computer environments, so perhaps I’ve adopted a whole team of mentors.</p><p><strong>How would you describe your career and the choices you’ve made?</strong></p><p>I think it’s a combination of safe but eclectic. In the “safe” category, I’d consider the fact that many of the IT roles I chose prior to Clio often involved technologies that I was comfortable with, e.g. Linux, simple scripting, minor automation. The “eclectic” part comes into play in the departures I’ve taken occasionally from IT: technical writer, commercial real estate agent, and makeup artist. So, yeah… I’m a little odd :)</p><p><strong>What risks have you taken in your career?</strong></p><p>Joining Clio! Prior to joining this organization, I had not worked in a “Software as a Service” business, so it was an entirely new environment. Being able to work remotely as easily as I do in the office was not something others places offered, so that was a change. Even relying on online resources for much of my daily tasks wasn’t something I had done before. I was concerned it was something that would prove too challenging. But the endless support I received from my colleagues along with the wonderful opportunities to meet other co-workers at team days and product summits have done much to resolve these concerns and let me focus on doing the best job I can.</p><p><strong>What advice do you have for prospective Clio candidates?</strong></p><p>The more effort you put into Clio, the more you’ll get out. Yes, that’s cliche, but hear me out. If you choose to just show up, carry out your assignments, and call it a day, you’ll find that Clio is a good employer. If, however, you start digging into various processes in the company and offering suggestions for their improvement, joining groups, volunteering with others for out-of-office events (hell, Clio -gives- you two and a half paid days to do just that), taking courses… you’ll find Clio is an amazing employer.</p><p><strong>How do you like to spend your free time?</strong></p><p>Corrupting my nephews and niece. Nothing brings more consternation to their parents than Uncle offering a well-timed poop joke. This fall, I’m going to introduce them to the spit-take.</p><p><strong>What did you want to be when growing up?</strong></p><p>A special effects makeup artist! Blood ’n’ guts! Monsters! Aliens! Turns out, though, “artist” just isn’t a title, you actually need artistic talent : )</p><p><strong>What’s a fun fact about yourself that no one knows?</strong></p><p>I once hit Tim Roth with my duffle bag at LAX. He took it remarkably well, and I was able to cross that item off my bucket list (I like that I’ve included “once” in that description…as if my bucket list item was “Hit Tim Roth with luggage…THREE TIMES!”)</p><p><em>Matt Abraham is a member of the Product team at Clio. The first half of his life was spent in Saskatchewan, the second half in Ontario, and he’s now working on his third half in Calgary. He’s been mistaken for a British featherweight boxer and an American soap opera actor, but he’s been correctly identified as a fantastic uncle.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba74ff90693f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/clio-labs/teamclio-matt-abraham-systems-engineer-production-ba74ff90693f">#TeamClio: Matt Abraham, Systems Engineer, Production</a> was originally published in <a href="https://medium.com/clio-labs">Clio Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#TeamClio: Shaheer Shabbir, Software Developer]]></title>
            <link>https://medium.com/clio-labs/d-teamclio-shaheer-shabbir-software-developer-be5c879a23cb?source=rss-b9dad36f87a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/be5c879a23cb</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[team-clio]]></category>
            <dc:creator><![CDATA[Clio Labs]]></dc:creator>
            <pubDate>Mon, 13 Aug 2018 16:36:02 GMT</pubDate>
            <atom:updated>2018-08-13T16:43:55.287Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DBkqC0hqi3FOEOlElSfT4w.jpeg" /></figure><p><strong>Who are you?</strong></p><p>My name’s Shaheer and I’m a software developer at Clio. While I currently live in rainy Vancouver, Canada, I was born in the ridiculously sunny state of California. Seriously, there’s an average of 284 days of sun in LA, where I was born! It seems like here in Vancouver, we have an average of 284 hours of sun but its made up for by the mountains and lack of traffic.</p><p><strong>What do you do at Clio?</strong></p><p>My role at Clio is a software engineer on the accounting and reporting team but what’s amazing is that what I can do isn’t entirely defined by my position title. While my main responsibilities are writing code, I’ve filled a bunch of other roles at the company because I found them interesting: I’ve onboarded new employees, spoken at our yearly customer conference with more than 1000 attendees, represented the company at multiple hiring events, interviewed customers, managed a small team, interviewed developer candidates, and played softball terribly.</p><p>At Clio, while we each have responsibilities tied to our roles, we also have the freedom to do what will have the most impact on the company and teammates.</p><p><strong>How long have you worked at Clio?</strong></p><p>I started working at Clio in April 2016, so it has been almost two and a half years since my first day.</p><p><strong>Which office are you in?</strong></p><p>While technically located in Burnaby, as far as anyone unfamiliar with the area is concerned, I work out of the Vancouver office.</p><p><strong>What led you to become a software developer?</strong></p><p>The turning point for me was a grade 12 IT class. Shoutout to my teacher, Marc Nordlund (Hi, Mr. Nordlund!), for turning my passion for technology into my career, as he was a huge influence on my decision to change my university program from general sciences to software development.</p><p>What really got me hooked on software development was that you can make something that millions of people can use out of nothing. Open up a text editor, Google some basic tutorials, and in no time at all, you can have a website online that you made yourself. Naturally, this lead to my desire to make things people could use, and 6 years later, here I am: building software that has a positive impact on the lives of tens of thousands of people everyday</p><p><strong>Can you describe a day in your role?</strong></p><p>I wake up early because traffic from where I live to the office is terrible if I commute to work during rush hour (but nowhere near as bad as LA). So for me, that means getting in and having a cup of coffee while I see what work was left off from the day before. Anything that needs review? Emails that need to be read? Memes that need to be made? I take it all in while I get warmed up for the day and look over my calendar and chunk my day up into different tasks I want to accomplish. I love being in the office early because when there’s no work left from the day before I have some quiet time to dive into a task or learn something new. Maybe profile some code that looked a bit fishy, read a blog post on the latest JS framework, or just take that super meaty ticket that I have no idea how to do and dive in for a bit. After a little bit the rest of the team rolls in or comes online (half my team is in Calgary) and while we get going, we catch up on each other’s personal lives. This is hugely important because it keeps us caring personally about each other, even in separate offices hundreds of kilometres apart. Also, it’s a great time for me to send off those 🔥memes I stole from the internet. Then we dive into our daily check-in meeting where we discuss what the team goal is for the day or week, depending on the project, and come up with a game plan. I think of it like a football huddle. Everyone has a part to play and strengths and weakness and also different capabilities from day to day. This is where we lay it all on the table to be the best team rather than the best individuals.</p><p>Then we get to work! We follow the plan we made earlier and sometimes that means pairing on a problem and sometimes we divide and conquer. If I’m working alone I usually stroll over to the far part of the office and work from a standing desk, because I just work better that way.</p><p>Some days also have meetings that we can’t avoid. It’s important that the team and leadership (development manager, product manager and product designer) are aligned, so when there’s a new mock-up or project, we all get involved discussing priority, scope and milestones.</p><p><strong>What drew you to Clio originally?</strong></p><p>What drew me most to Clio was the interview process. It wasn’t a series of random things you’ll never use in the real world. I wasn’t asked to reverse a string with specific time and space constraints like I was in most of my other interviews. I didn’t have to live code a random problem in a language or setting I wasn’t familiar with. I was asked questions that challenged me but I also didn’t feel like I had a gun to my head to be perfect. While technical, there was also a good mix behavioural question to really assess the how I would fit with the team. Are you someone that people want to work with? Someone that can teach or be coached? Just as important as being capable, is being a good fit for the amazing culture we have at Clio.</p><p><strong>What’s been your favourite moment at Clio?</strong></p><p>My favourite moment at Clio is a bit unfortunate but something I will never forget. This past year will hopefully be the hardest year of my life as I navigated deaths in my family, surgeries, and my house burning down, just to name a few things. There were times that I was absolutely overwhelmed and really just done with it all. I was shocked that work actually became my escape from it all. When I came to work, I was dialed into what I was working on and I got an avalanche of support from anyone I told. My manager even worked with me to take time off to recover from my surgery in an abnormal way. I realized that I’m not just a cog in a giant machine I’m a person that people cared about — not just my direct manager, but others as well. The people here are amazing and I don’t think I would have come out last year as well as I did if I was anywhere else.</p><p><strong>Have you had any important mentors in your life?</strong></p><p>I’ve had a few mentors in my life both in and out of Clio. However, my greatest mentor and role model is definitely my uncle. My uncle was one of those people that puts you at ease the second you meet him. Within minutes you would feel comfortable discussing the things that are troubling you most and he would never make you feel bad or judged. He would just listen and put himself in your shoes and talk you through figuring out what you can do next. I don’t think I’ve ever seen him judge anyone or hold a grudge.</p><p>My uncle taught me to never stop learning or pushing myself. Without him, I probably wouldn’t have had the drive to keep going in school when things got hard or to constantly push to grow in other aspects of my life. He really helped me become comfortable with discomfort and taught me to always ask questions and ask more of myself. He has a very strong belief that the only limits I had were self-imposed, and although I don’t always agree, I find myself thinking about what he would say when the path forward seems impossible.</p><p><strong>What did you want to be when growing up?</strong></p><p>Well I have stereotypical South Asian parents, so there was a big push to be a doctor. I don’t know why. I would still be in school and have 10x the debt. I thought about it, though, and was pretty close to trying to be a psychiatrist. That said, I still really love the subject and read lots of books on the subject for leisure and if I ever went back to school, I would definitely go back for psychology.</p><p><strong>What’s a fun fact about yourself?</strong></p><p>I’m a big Taylor Swift fan. Huge actually. I even added a command to our chat bot that sends a Taylor Swift gif when you type !tswift. In my opinion, the most impactful thing I’ve done as a software developer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*URvlxTmINXF681UeAZ67Rg.gif" /></figure><p><em>Shaheer Shabbir is a software developer at Clio. Shaheer was born in Los Angeles, but prefers the mountains and better traffic in Vancouver. He likes reading in his free time and still believes monsters can’t hurt you if you keep all your limbs under the covers at night.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be5c879a23cb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/clio-labs/d-teamclio-shaheer-shabbir-software-developer-be5c879a23cb">#TeamClio: Shaheer Shabbir, Software Developer</a> was originally published in <a href="https://medium.com/clio-labs">Clio Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[#TeamClio: Shaked Fromovich, Senior Software Developer]]></title>
            <link>https://medium.com/clio-labs/teamclio-shaked-fromovich-senior-software-developer-905b43a6f66b?source=rss-b9dad36f87a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/905b43a6f66b</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[team-clio]]></category>
            <dc:creator><![CDATA[Clio Labs]]></dc:creator>
            <pubDate>Mon, 30 Jul 2018 17:01:01 GMT</pubDate>
            <atom:updated>2018-08-13T16:42:56.536Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dz1vLdMPyoO_mZcAsEv8Cw.jpeg" /></figure><p><strong>Who are you?</strong></p><p>I am a Senior Developer at Clio. I moved to Vancouver and joined Clio in the summer of 2017 after spending 7 years as a software engineer in the Israeli military and in the Tel Aviv startup community. I love Vancouver, but I’m still trying to get used to the weather here. At least the mountains are full of snow in the winter, which fills my weekends with snowboarding.</p><p><strong>What do you do at Clio?</strong></p><p>Until recently, I was part of the front end infrastructure team. I’m now working with a team that is imagining the future of Clio and how we can have a larger impact on our customers’ businesses. Clio wants to help our customers become great at what they do and my team is exploring new ways we think we can do that. I still miss my old team but wanted to do more full stack stuff and that opportunity was available on the new team.</p><p><strong>Which office are you in?</strong></p><p>While technically located in Burnaby, we consider ourselves the “cool” Vancouver office.</p><p><strong>What led you to become a software developer?</strong></p><p>After failing the aircraft pilot course in the Israeli military, they offered me a consolation prize in a form of a software engineering job at the Israeli Air Forces, where I spent the first 7 years of my career. Since I always loved solving problems, it turned out to be a pretty good fit for me. Working as a software engineer is never boring, and I could not imagine myself doing anything else. Well, maybe I could be a good cook, but that story is for another time.</p><p><strong>What does a day in your role look like?</strong></p><p>My day starts with a hot cup of coffee and a review of the goals I want to accomplish that day at the office. After updating my peers at the morning stand-up meeting, I get to the good stuff. Usually during the day I participate in product meetings, design reviews and of course some ‘me time’ in the form of coding.</p><p>Sometimes I get writer’s block, which usually means it is the perfect time to catch up with some of the dogs at the office.</p><p><strong>What drew you to Clio originally?</strong></p><p>I met Clio representatives at a Tech Job Fair in Vancouver, and we clicked immediately. I applied to a couple of other companies but after interviewing with Clio, it was a no brainer. I didn’t know too much about their products, but I really liked my experience and the people I met during the hiring process. While technically challenging, my interview experience felt more like a friendly geek out on software, design and general tech. I loved it because I felt like they cared about getting to know me as a person as much as my technical skills.</p><p><strong>What do you love about your job?</strong></p><p>Clio invests a lot in their human capital, and it shows. I truly love the people I work with, and I feel very appreciated by the company. Borrowing a metaphor from the financial world, it feels like Clio is a true trickle down economy, the success is shared between each and every one of us.</p><p><strong>What’s been your favourite moment at Clio?</strong></p><p>Every few weeks, the employee experience team organizes a mixer for all employees with food and drinks. One of my favourite moments was a trivia evening of “Friends”. I was arrogantly sure there was no one who has seen “Friends” more times than I have, but I was wrong. That night I got to know another side of the people that I work with, and also got myself some new Trivia nemeses.</p><p><strong>What risks have you taken in your career?</strong></p><p>After spending 7 years as an engineer in the military, I decided to leave my comfort zone and join the private sector. I had 2 choices — joining another big corporation or go for a small start-up company in it’s very early stage. With all the risks associated with it, I chose the latter. In big companies, you have lots of opportunities to grow and learn and the job would be pretty stable. On the other hand, in a small start-up, being 1 of 4 employees, you are pretty much alone. You need to manage your own growth and your own development. Not to mention the uncertainty when every day can be your last one if the funding stops. However, I knew I wanted to try, and so I did. After more than a year at an early stage startup in Tel Aviv, I moved to Vancouver and joined Clio.</p><p><strong>What’s a fun fact about yourself that no one knows?</strong></p><p>I can’t whistle.</p><p><em>Shaked Fromovich is a senior software developer at Clio. She served in the Israeli military as a software engineer for 7 years before moving to Canada and joining Clio. She likes snowboarding and cooking in her free time and hates Adam Sandler movies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=905b43a6f66b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/clio-labs/teamclio-shaked-fromovich-senior-software-developer-905b43a6f66b">#TeamClio: Shaked Fromovich, Senior Software Developer</a> was originally published in <a href="https://medium.com/clio-labs">Clio Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Clio’s Road to Android: The Beginning]]></title>
            <link>https://medium.com/clio-labs/clios-road-to-android-the-beginning-b19d3b96de6d?source=rss-b9dad36f87a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/b19d3b96de6d</guid>
            <dc:creator><![CDATA[Clio Labs]]></dc:creator>
            <pubDate>Wed, 26 Nov 2014 22:26:45 GMT</pubDate>
            <atom:updated>2016-08-26T18:21:54.530Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Cliolab - Road to Android" src="https://cdn-images-1.medium.com/max/600/0*D3fcFBUj2C8TKNx4.png" /></figure><p>There’s a saying at Clio: “draw the fucking owl.” Last year, for me, that owl was an iOS app. This year, it was the Android app. From absolutely no Android app development experience to leading a team of six amazing product members and building a full-spec practice management app, it’s been truly an amazing journey.</p><p>On September 22nd, when I witnessed the launch of the Android app at the Clio Cloud Conference in Chicago, I was absolutely amazed at how everything came together.</p><p>The Beginning</p><p>It’s hard to believe that it was only eleven months ago that we started the project. I was definitely nervous. It wasn’t really because of the new responsibilities that came with being a team lead; it was because I had no experience with Android, yet I had to lead a team of developers and make a million decisions. I powered through a handful of Android development books and met with a few key players in Android development communities in Vancouver. I want to thank <a href="https://twitter.com/franklywatson">Jerome</a> from Amazon, <a href="https://twitter.com/Mike_Worth">Mike Worth</a>, and <a href="https://twitter.com/jstautz">Jeff Stautz</a> from HootSuite for giving me advice and tons of tips. I also went to a local mobile app development shop, SteamClock Software, and arranged a workshop; in two days, we covered topics like multi-threading, UI implementation, animations, best practices, and some major differences between iOS and Android. These were just some of the steps I took to get into the Android game.</p><p>Our team started with one product manager who oversaw both Android and iOS as well as API, one UI designer/developer, and three developers including myself. We added another developer and a new mobile QA analyst. Hiring was/still is challenging because there’s a lot of pressure to make a decision with just a few hours of interviewing, but I had to make a call. Criteria for a talented software developer remain consistent regardless of the field, but I’m definitely a lot more comfortable interviewing now with the experience and knowledge I’ve gained.</p><p>These are some of the things I look for from candidates: a deep understanding of the Activity and Fragment lifecycles, various issues with a runtime configuration change, consequences in dealing with a runtime configuration change in a variety of situations, threading, and processes, UI view elements, database knowledge, Java skills, experience with major HTTP libraries, etc. For a QA analyst, I’d like to see experience in Continuous Integration systems and configuring with mobile environment, various integration testing tools for mobile app development, and some programming experience.</p><p>It comes down to: “if you have to plan for an Android app release and need to have support for thousands of devices, multi-OS versions, and a variety of screen resolution sizes, what is your plan to meet our quality standard with these conditions and being able to confidently ship an app at a release date?” We’ve been working on that since the beginning and are still trying to get it right. If you can give me a solid answer for this question, you’re all set. Come chat with me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b19d3b96de6d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/clio-labs/clios-road-to-android-the-beginning-b19d3b96de6d">Clio’s Road to Android: The Beginning</a> was originally published in <a href="https://medium.com/clio-labs">Clio Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Clio Customer Notice: Shellshock]]></title>
            <link>https://medium.com/@cliolabs/clio-customer-notice-shellshock-a2ac013c0507?source=rss-b9dad36f87a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2ac013c0507</guid>
            <category><![CDATA[uncategorized]]></category>
            <dc:creator><![CDATA[Clio Labs]]></dc:creator>
            <pubDate>Sat, 27 Sep 2014 00:22:53 GMT</pubDate>
            <atom:updated>2016-08-26T18:21:50.364Z</atom:updated>
            <content:encoded><![CDATA[<p>On Wednesday September 24th, a major computer security flaw officially known as CVE-2014–6271 was released.</p><p>Dubbed “Shellshock,” it’s a vulnerability that allows hackers to send commands to a computer’s operating system (which is what a “shell” does). What devices are affected? Potentially, Internet-powered devices that have the problematic software package installed — these could be like Wifi routers, remote webcams, and even appliances if they are hooked up to the Internet.</p><p>As soon as the Clio team learned about the bug early Wednesday morning, we worked to patch our servers immediately, and the patches were complete within hours.</p><p>A few hours later, however, additional vulnerabilities named CVE-2014–7169 were discovered that the patch for CVE-2014–6271 didn’t fully address. Our team immediately got to work patching these as well — completed within about 24 hours.</p><p>There’s no evidence of any customer information being compromised, but we’re still monitoring the Internet and making sure your data is safe. We’re currently fully patched and secured, which means that even if hackers try to get into information that doesn’t belong to them in Clio, they won’t get anywhere. No effort is required on your part at this time to further secure your data.</p><p>Our team is on top of it, so in the meantime, stay informed and <a href="http://techcrunch.com/gallery/what-you-need-to-know-about-shellshock/">read up on the bug</a>. If you have any questions, just email us at <a href="/service/mailto:support@goclio.com">support@goclio.com</a> and we’ll be happy to address any concerns you may have.</p><p>– Graham Kennedy (Twitter: <a href="https://twitter.com/GrahamAtClio">@GrahamAtClio</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2ac013c0507" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Removing String Literals in SQL with AREL]]></title>
            <link>https://medium.com/clio-labs/removing-string-literals-in-sql-with-arel-776d01594c1c?source=rss-b9dad36f87a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/776d01594c1c</guid>
            <category><![CDATA[sql]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Clio Labs]]></dc:creator>
            <pubDate>Mon, 26 May 2014 19:54:11 GMT</pubDate>
            <atom:updated>2016-08-26T18:21:45.189Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="SQL Areal Banner Photo" src="https://cdn-images-1.medium.com/max/651/0*p27NQvBPzYXP8TTy.png" /></figure><p><em>“With great power, comes great responsibility.</em>” ~Voltaire, or Franklin D. Roosevelt, or maybe Spiderman’s uncle.</p><p>This line runs through my mind EVERY time I write raw SQL in my Rails code. ActiveRecord does some really nice stuff for us, and is really flexible, but some of us still can’t <br>get away from the SQL fragments in our queries. How many of you have done something like this?</p><pre>Post.joins(&quot;LEFT JOIN comments ON comments.post_id = post.id&quot;)</pre><p>So what’s wrong with that? First off, you have to know SQL syntax. Not everyone has a SQL background, and maybe even less want one. On top of that, the above query has no syntax checking. What if, heaven forbid, you had to change a table name? Search and Replace. Fun.</p><p>Maybe you are just doing a simple WHERE clause with a few parameters passed in — active posts published in a date range:</p><pre>Posts<br>  .where(&#39;posts.active = ? &#39;                  \<br>    &#39;AND posts.published_at &lt;= ? &#39;            \<br>    &#39;AND posts.published_at &gt;= ?&#39;, <br>    true, from_date, to_date)</pre><p>Pretty sure we have all done lots of these. So what’s wrong here? Apart from the tragic formatting — I am dealing with WordPress here. Again, we have to know SQL syntax, we get no syntax checking, and you have to match up parameters with the proper placeholders. Not usually a big deal with a couple parameters, but it only takes getting two params mixed up and you have an annoying bug to hunt down. Spot mine?</p><p>So, what’s a better approach? First, let’s avoid literal strings in our queries. They suck. Some syntax checking would be nice to have and, since we are making demands, let’s ask that all this is done in a language we already know.</p><p><strong>Arel</strong> <em>*angels singing*</em></p><pre>Post<br>  .joins(<br>    Post.arel_table.join(Comment.arel_table,Arel::OuterJoin)<br>      .on(Post.arel_table[:id].eq(Comment.arel_table[:post_id]))<br>      .join_sources)<br>  .where(<br>    Post.arel_table[:active].eq(true)<br>      .and(Post.arel_table[:published_at].lteq(to_date)<br>      .and(Post.arel_table[:published_at].gteq(from_date))))</pre><p>Now we are on to something. We no longer have to know SQL syntax, we have Ruby syntax checking and, as an added bonus, we are working with objects and can further chain our query.</p><p>Glossing over the details, Arel is the query building language, or “relational algebra”, for Ruby. This means IT DOES NOT REPLACE ActiveRecord; ActiveRecord still does all the retrieving and storing of data. Arel only constructs queries.</p><p>Let’s do a couple bonus examples for fun. Say you need to do a subquery. Say you don’t even care any more and you just wrote raw SQL.</p><pre>Post<br>  .find_by_sql(&#39;SELECT `posts`.`title` FROM `posts` &#39;   \<br>               &#39;WHERE `posts`.`title` IN (&#39;             \<br>                 &#39;SELECT title FROM `posts` &#39;           \<br>                 &#39;WHERE `posts`.`id` = 8)&#39;)</pre><p>So many places to make a mistake. Wouldn’t you be chapped if your team was already out on the patio, with some craft suds, and you had to fix your flailing SQL? I would be chapped for you.</p><pre>Post<br>  .select(Post.arel_table[:title])<br>  .where(<br>    Post.arel_table[:title].in(<br>      Post.select(:title).where(id: 5).ast))</pre><p>As a final example, we can also do a like query with Arel’s matches:</p><pre>Post.where(Post.arel_table[:title].matches(&#39;%SQL%&#39;))</pre><p>Good example code and tutorial material on Arel is a bit tough to find, so the learning curve is a bit steep. But, sometimes just messing with it is the best way to learn. Enjoy!</p><p><a href="https://github.com/rails/arel">Arel on Github</a><br><a href="http://rubydoc.info/github/rails/arel/master/Arel/Predications">Arel Predications</a><br><a href="http://railscasts.com/episodes/215-advanced-queries-in-rails-3">RailsCast #215</a></p><p>– Terry White “PANCAKES” (Twitter: <a href="https://twitter.com/PANCAKESo">@PANCAKESo</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=776d01594c1c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/clio-labs/removing-string-literals-in-sql-with-arel-776d01594c1c">Removing String Literals in SQL with AREL</a> was originally published in <a href="https://medium.com/clio-labs">Clio Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quality Control vs. Quality Assurance]]></title>
            <link>https://medium.com/clio-labs/quality-control-vs-quality-assurance-529e23ce47be?source=rss-b9dad36f87a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/529e23ce47be</guid>
            <category><![CDATA[uncategorized]]></category>
            <category><![CDATA[qa]]></category>
            <dc:creator><![CDATA[Clio Labs]]></dc:creator>
            <pubDate>Wed, 05 Mar 2014 20:43:31 GMT</pubDate>
            <atom:updated>2016-08-26T18:21:47.421Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Apples and Oranges" src="https://cdn-images-1.medium.com/max/651/0*FX4VutBbenZv9rRV.png" /></figure><p>When I joined Clio in October 2013, I was excited for a few reasons (This isn’t even counting the free flow of beer in the lounge). I knew Clio had a solid track record of delivering an awesome product with frequent updates and new features. This alone was a good sign, but getting a chance with my fellow QA team to establish a QA guild was a great opportunity to make deploys more stable, reliable, and less stressful! It’s no mystery that QA does a lot of testing, but often we’d get questions about how we do it. To help explain, I like to say QA involves both Quality Control and Quality Assurance. Often these terms are used interchangeably, but they actually mean different things.</p><p>Let’s start with taking a look at bugs. At minimum, the expectation from QA is to ensure that we help prevent deploying a critical or blocker issue while doing as much as possible to minimize other problems. In other words, we provide the business with an expectation that what is being deployed meets acceptable levels of risk and quality. It’s a fine balance though. Fact is, we cannot test/fix bugs forever or we’ll never finish or deliver anything! So what happens when we do miss a nasty bug?</p><p><strong>Here’s a very summarized view of what happens from start to finish:</strong></p><p><strong>1.</strong> Customer encounters a bug</p><p><strong>2.</strong> If the bug is bad enough it will likely prompt a call / ticket with our Support team</p><p><strong>3.</strong> The ticket is then either linked to an existing bug / feature report, or a new one is created</p><p><strong>4.</strong> Bug is fixed, code-reviewed, passed to QA for verification and sign-off, then deployed</p><p>This is actually an ideal path for a bug (aside from it escaping in the first place). It assumes the bug was straightforward to identify, reproduce, prioritize, fix, test, and deploy. Even so, we’ve already engaged numerous parties and spent hours if not days of total time to close the loop, not to mention the frustration and lost productivity for our customer. It’s obvious there is cost, pain, and frustration that we need to try and avoid as much as possible.</p><p><strong>Quality Control</strong></p><p>To achieve this, our first order of business was introducing Quality Control (error detection). We started with defining a <a href="http://en.wikipedia.org/wiki/Smoke_testing_(software)">Smoke Test</a>. Specifically, a small set of tests that covers as much common and critical functionality as possible in a limited amount of time (we chose 30 minutes). Sample tests include “Verify that a Time Entry can be created and billed.” and “Verify that reports can be generated.” etc… Simple, but crucial functionality that is verified before a deploy. Having these defined, we know that it will not prevent us from deploying bugs, far from it, but it will help us avoid deploying those bugs. Since many of these tests are simple and repeatable, they were natural candidates for automation but that’s a topic for another day.</p><p><strong>Quality Assurance</strong></p><p>Our next order of business was introducing Quality Assurance (error prevention). Just having QA on the team helps, but ultimately we require a final sign-off by QA on features and fixes. This isn’t the only sign-off, but it is always the final sign-off. So what does the QA sign-off represent? Where Quality Control is responsible for error detection, Quality Assurance is the business of complementing the team’s ability in preventing failures. Failures being: bugs, poor usability, coding error, customer confusion, or frankly anything that detracts from product quality in our customer’s eyes. Error detection is crucial, but relatively trivial. Essentially, you are just following steps to determine a pass / fail case. Taking QA to the next level is effective failure prevention. Bringing solid QA expertise truly does require a broad skill and knowledge set. It requires being meticulous, thorough, and patient while also keeping the big picture in mind. Derek Rawlings, a fellow QA gives <a href="http://labs.goclio.com/how-wearing-multiple-hats-helps-your-users/">good insight</a> into this.</p><p>At the end of the day, I can’t be successful unless I work with awesome people on an awesome team. Clio truly is a wonderful place to work and it is a very rewarding atmosphere. Fellow Product team member, Hanson Wu highlights a number reasons why Clio reflects a <a href="http://labs.goclio.com/4-steps-for-creating-a-winning-culture/">winning culture</a>.</p><p>– Jeremy Papp (Twitter: <a href="https://twitter.com/PappJeremy">@PappJeremy</a>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=529e23ce47be" width="1" height="1" alt=""><hr><p><a href="https://medium.com/clio-labs/quality-control-vs-quality-assurance-529e23ce47be">Quality Control vs. Quality Assurance</a> was originally published in <a href="https://medium.com/clio-labs">Clio Labs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>