<?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 Kaspar So on Medium]]></title>
        <description><![CDATA[Stories by Kaspar So on Medium]]></description>
        <link>https://medium.com/@KasparSo?source=rss-29045248ce5b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*QYobQReS6AKXk41_e4Gwsw.jpeg</url>
            <title>Stories by Kaspar So on Medium</title>
            <link>https://medium.com/@KasparSo?source=rss-29045248ce5b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:50:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@KasparSo/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[Deciding to Go Back to School Over Work]]></title>
            <link>https://medium.com/@KasparSo/deciding-to-go-back-to-school-over-work-2ea4059c6fe6?source=rss-29045248ce5b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ea4059c6fe6</guid>
            <category><![CDATA[life]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Kaspar So]]></dc:creator>
            <pubDate>Fri, 08 Sep 2017 13:01:01 GMT</pubDate>
            <atom:updated>2017-09-08T15:25:19.457Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vveb4QyndHi1PW3u22jcNQ.jpeg" /><figcaption>Photo courtesy of Matt Popovich (Unsplash)</figcaption></figure><p>Towards the end of my second year at school I was presented with an opportunity to take on a full time position at a highly recognized newspaper company in my city. It fulfilled so many things that I wanted; data visualization, interaction design, UX, front-end development, narrative, working with professionals outside of design and tech, and the pay didn’t hurt. Coming off of a rougher school year, I was ready to be off school for a while. The question was whether I was ready to be done with school completely or would September roll around and I’d be recharged and ready to go.</p><p>At the time, I told my employer that I couldn’t confidently say that I would not go back to school, but regardless he offered me the position. He did ask that I approach it with the mentality that I won’t go back to school, but if I chose to, he would understand. That was a vote of confidence that I deeply appreciate. It showed that I was valued for what I could provide and not just simply for filling out the position. With that, I took the position, ready to drop out of school.</p><p>During my time there I learnt so much. From working with reporters on quick turnaround projects to being a part of conversations and meetings for investigative stories months from release, I had an opportunity to experience a breath of projects. Something about knowing the news before it was published was really unique. I would walk to and from work with a sense of knowing a secret ready to break, as if I could tell the future. And not only knowing the news, I was actively contributing to help people better understand it. By working on the digital side of the newspaper, I wrote production level code and was given fairly free reign in terms of the way I wanted to visualize supporting data. In all fairness, there are some best practices combined with time constraints and unfamiliarity with the library that we were using (<a href="https://d3js.org/">d3.js</a>) which led to less exploration being pushed out.</p><p>However, the summer had pockets of downtime. The people that I worked with actively encouraged me to explore, to find some aspect within the broad job description that I could really specialize in. I jumped around in terms of my focus, sampling from things I knew and things that were completely new. My previous experience with <a href="https://p5js.org/">p5.js</a> and <a href="https://threejs.org/">three.js</a> was not wasted when I went in those directions. As an aside, a particularly “fun project” that I worked on was mapping flight paths onto a globe via three.js but doing so via longitude and latitude conversion to 3d space while calculating the aggregate distance travelled. I also learnt d3.js, which seems like the industry standard for web data visualization, while leading the charge in committing to SCSS and BEM, which was something the team had been meaning to do for a while, all in the name of writing more collaborative code.</p><p>I can’t speak more fondly of the team that I worked with. The people at this company are bright, hard working, but ultimately they were honest. They knew where their strengths laid but were also transparent when they didn’t know something. This was incredibly refreshing as it built a strong sense of trust between each of us. It also built respect as we knew who we should default to as the expert on the team. For instance, one of my teammates was particularly interested in illustrating and building out maps, so whenever a project came around focusing on maps, we would look to him for leadership.</p><p>For all the good this company had to offer, there were a few things that I was discontent about. I wish that we sat closer to our designers, and worked more collaboratively. The producer that I worked most closely with left right around the time a lot of our designers were let go, which is just a real hit to morale. Having a large portion of the team you worked with day in and day out with leave just sucks, especially after establishing those trusting relationships.</p><p>Ultimately, I decided to leave, namely after a trip out to the bay area and seeing how large tech companies operate. I’ve always wanted to work in tech, but was weary that I may have, for a lack of a better term, drank the kool-aid. But dang, when I went out there, it confirmed what I thought; talented people working collaboratively, focusing on the user, and tackling complex problems. Best of all, it confirmed that positions existed for people like me, those who have a love for UX design and development. It also confirmed that I would most likely need my design degree to work in that space. After months of debate and a mixed response from those who I talked to in Toronto, California gave me a clear answer: go back to school.</p><p>Thank you to everyone that made my summer what it was. I want to especially thank a few people from the company, regardless if they’ve found this article or not. To my boss that took a chance on a kid that liked to data, design, and code. To the brilliant reporters, editors, designers, and producers I had to honour of working with. And especially to my immediate team, the guys that I sat with everyday. You guys got me through the rough patches and put up with my trailing thoughts, inability to link a quiz to an iframe, and naivety in terms of not knowing where to summer. Oh, and definitely thanks to the local sushi spot that would house us on the occasional Fridays.</p><p><em>Thanks for reading. I think my next couple of posts will dive deeper into building out some UI elements for the web and talking about the design decisions I made along the way.</em></p><p>Also, the startup that I’m working for right now, <a href="http://www.thejukeboxapp.com/">Jukebox</a>, is in the final rounds of voting for a Timmy Award. It’d be great if you could hit that thumbs up!</p><p><a href="https://app.reviewr.com/s1/pitch?evtid=2654296&amp;subid=2812081">https://app.reviewr.com/s1/pitch?evtid=2654296&amp;subid=2812081</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ea4059c6fe6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designer as Developer]]></title>
            <link>https://medium.com/@KasparSo/designer-as-developer-caec49f5c4eb?source=rss-29045248ce5b------2</link>
            <guid isPermaLink="false">https://medium.com/p/caec49f5c4eb</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Kaspar So]]></dc:creator>
            <pubDate>Fri, 23 Jun 2017 13:31:00 GMT</pubDate>
            <atom:updated>2017-06-23T15:31:08.633Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pUFV_X49ikg555J8N1dd1w.png" /><figcaption>Something like that</figcaption></figure><p><em>Hey, I’m Kaspar So. I’m a design student currently working as a developer.</em></p><p>For the past month and a half I’ve been working (gone undercover) as a developer for a larger newspaper company. I started this job coming off my second year of a four year <a href="https://academics.sheridancollege.ca/programs/bachelor-of-interaction-design">Interaction Design program</a>. My goal for the summer was to work closer with developers as the relationship between designer and developers has been, and still is, a growing interest of mine. When being offered a developer position (official title being Digital Products Developer), I realized that it was a great opportunity to gain perspective from a developer’s point of view. Taking on the role, my experience in web development was limited, but I was confident in my ability to learn on the job as I often found myself coding my prototypes rather than building examples in a motion graphics tool, like After Effects. This article is a brief reflection on a few things I have learned so far.</p><p>I feel like starting a new job is like figuring out where you fit within the current production cycle/process. Being a newspaper company, there were established ways of how things were done, with people that have been working here for 20+ years. My goal was to understand the current process and see where I can insert myself. When I explain the process here to some of my friends, they find it odd that it’s so different from what we had learned. Coming from design school, I’ve heard of my fair share of normative workflows.</p><blockquote>“We’re designers, we’re supposed to disrupt the process!”</blockquote><p>While I don’t oppose the processes we’ve learned, I understand that designers can be overly ambitious at times. The reality is that this company might have adopted a unique process due to their established past. I have to understand it before even trying to change anything.</p><h4>Get Close</h4><p>It’s hard to work with designers and developers if they’re spaced out. The layout of my work has designers sitting across the newsroom to where my team sits, which results in either us going to them or them coming to us for any type of review. This sucks when it comes to UX/UI refinement as each tweak is a suicide sprint.</p><p>Distance aside, our designers work overtime as they design for more than just our team. This doesn’t serve well to developing functionalities first, UI second, as designers coming in closer to the end of the production process often results in rebuilding some components, simply because they weren’t continuously a part of the development. By having them closer, a more constant dialogue can be had.</p><p><em>*This could just be an issue of not enough designers. A temporary solution would be to give the developers more creative control, as a couple of us come from design backgrounds. It’s temporary and not necessarily scaleable, but it could be useful to push us through the heavy project seasons.</em></p><h4>Don’t “Just build both and we’ll see”</h4><p>This is conditional, as changing a single button from a circle to a square isn’t hard, but building two finished versions with different UX/UI is just unnecessary, especially for our team size and workload. I much prefer the methodology of building out a MVP, or Minimum Viable Product, and iterating. This keeps forks in the road smaller, and less of a surprise. Furthermore, building multiple versions that are not iterations of one or another sets a bad precedent for the way your time should be spent, as there are always more projects to work on.</p><h4>Instances are Nice, but &lt;strike&gt;Diamonds&lt;/strike&gt; Tools are Forever</h4><p>Working at a company that is constantly pushing out content (in the form of articles), building for reusability is key. While it is nice to build a super customized end product, I’ve learned that thinking about your projects as reusable components, rather than one-offs, will yield more value long term. Allowing writers to have access to tools means you build more autonomy in their daily workflow, rather than them coming to you every time they need to visualize something. As such, from a designer perspective, it would be a nice challenge to think about designing for tools and being able to adapt them to multiple contexts.</p><p>Ultimately, this list serves as a reminder to future Kaspar, the designer. Things to remember when communicating with devs, and understanding their perspective when the topic of iterations, special features, and multiple builds come to mind.</p><p><em>Thanks for reading. My goal is to use Medium to write about my experiences and share what I learn as I journey through my design career. I may not always be right, so let me know what you think. Feel free to </em><a href="https://twitter.com/KasparIsSo"><em>get in touch</em></a><em> and expect another article soon.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=caec49f5c4eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>