<?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 u2i on Medium]]></title>
        <description><![CDATA[Stories by u2i on Medium]]></description>
        <link>https://medium.com/@u2i?source=rss-2f109c7692d4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kdrJbF1dV2zRsKXI6p5nUQ.png</url>
            <title>Stories by u2i on Medium</title>
            <link>https://medium.com/@u2i?source=rss-2f109c7692d4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 14:29:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@u2i/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[Internships — A Tale of The First Summer of Code]]></title>
            <link>https://medium.com/u2i-blogs/internships-a-tale-of-the-first-summer-of-code-3dfc7831e050?source=rss-2f109c7692d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/3dfc7831e050</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[hiring-for-startup]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[u2i]]></dc:creator>
            <pubDate>Thu, 18 May 2017 13:11:45 GMT</pubDate>
            <atom:updated>2017-05-18T13:14:11.809Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Internships — A Tale of The First Summer of Code</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QqFdNWzzu28RrqQhppKmQA.jpeg" /></figure><p>For every student there comes a time when they decide to spread their wings and venture into the professional world. For some it stems from their inner desire to become independent and to start shaping their future. Others just have to do it. Because college.</p><p>For me it might have been a mixture of the two. I’d had my share of freedom and college had been steadily becoming quite a boring experience. And it was the 6th semester which means mandatory professional practice.</p><p>I had heard tales of a magnificent land where everyone rejoiced and was showered with riches (and food). This land was called u2i. Some of my close friends retold this tale to me but they were all unable to gain entry into this magical kingdom. So, in my mind, the company had grown into a myth.</p><h3>The Entry</h3><p>Having heard such great things about the company I jumped at the opportunity when I saw the tweet announcing The Summer of Code at u2i. I sent them my CV without hesitation.<br>Soon I received a reply inviting me to fill out online coding tasks. As I set out to complete them within a given time I was apprehensive but I soon discovered that with some thought and care I was able to finish with time to spare.</p><p>After two dreadfully long weeks I finally received another message. I was invited to an interview. A couple of days later I was standing in front of a glass door with the u2i hexagon painted on it like a hypnotising spell.</p><p>I was welcomed by the sight of many people feasting together at a long table, the chatter was friendly and relaxed, and the kitchen was filled with everything your heart could desire. I was ushered into a bright room called Sherwood Forest where I awaited my interview to start.<br>The interview consisted of two parts led by different people. During the first one I discovered what the internship would look like. Afterwards we had a conversation about me and my expectations which wasn’t stressful at all. The second part tested my abilities as a future coder and consisted of a set of more technical questions preluded by an algorithmic task.</p><p>A couple of days later another email from u2i found its way to my inbox. As you can imagine it was not a rejection letter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/721/0*fWTLefw0DyQRtEZ5.jpg" /></figure><h3>Sworn in</h3><p>When the first day of the internship rolled around and I arrived for my first u2i breakfast the excitement was palpable. I didn’t really know what to expect from my time here. I was just eager to learn from more experienced people than me. I was sure it would be interesting especially since we were to build an internal project from scratch. And boy, was I right.</p><p>The three months that followed went by in the blink of an eye. One of the unexpected things about the project was actually how much fun I had doing it and how much I had grown to like all the people I worked with. Which wasn’t solely because we played a lot of table tennis together (which was a whole lot)! There were many great people involved in the internships who took time away from their regular responsibilities to teach us a thing or two.</p><p>We faced some challenges along the way and the end result was hardly flawless but we picked up useful insights and managed to deliver something that turned out to actually be useful to the people at u2i (an app that allows managing conference room bookings). One of the great things about starting a brand new project was the fact that we weren’t hindered by trying to maintain existing legacy code. We got to use all the shiny new toys (e.g. Rails 5) and build everything from the ground up. Which also resulted in making a large amount of our own mistakes. But after all those are the best learning tools.</p><p>Throwing us into a single project also meant there was no rivalry between us, instead we were “forced” to become a team and work together to solve the problems we faced (which doesn’t mean we didn’t also receive a lot of guidance from our mentors).</p><h3>Aftermath</h3><p>In retrospect the internship far surpassed my expectations. I definitely learned a lot and then learned some more: working in a real team taught me a great deal about collaboration; my personal comfort zone was challenged by pair programming where I couldn’t always get my way; my coding skills improved a whole lot (I’m pretty sure) and I boosted my knowledge of Rails and React; implementing the scrum methodology prepared me for real projects. You won’t get this much experience in your whole college career.</p><h3>Ever after</h3><p>As you may or may not have guessed I am still working at u2i along with two more of my fellow interns. What motivated my decision to become a permanent resident in u2i land? I can honestly say it wasn’t a difficult one. After meeting so many great people, solving interesting problems and, most importantly, improving myself in ways other than increasing my knowledge, I knew I just had to stay.</p><p>Author: Beata Obrok</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3dfc7831e050" width="1" height="1" alt=""><hr><p><a href="https://medium.com/u2i-blogs/internships-a-tale-of-the-first-summer-of-code-3dfc7831e050">Internships — A Tale of The First Summer of Code</a> was originally published in <a href="https://medium.com/u2i-blogs">u2i’s lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is Programming for Women?]]></title>
            <link>https://medium.com/u2i-blogs/is-programming-for-women-b84cb843dbe4?source=rss-2f109c7692d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/b84cb843dbe4</guid>
            <category><![CDATA[women-in-business]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[diversity-in-tech]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <dc:creator><![CDATA[u2i]]></dc:creator>
            <pubDate>Thu, 18 May 2017 12:59:08 GMT</pubDate>
            <atom:updated>2017-05-18T12:59:08.636Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*98WJwbrZdSfKcE78h1hB-w.jpeg" /></figure><p>This is an English version of the interview about women in tech, originally published by <a href="http://mamopracuj.pl/">Mamo Pracuj</a>*</p><p><em>People tend to love the IT industry for its openness to employees and their ideas. If we add the lack of hierarchy, flat structure and flexibility, do we really have to do anything more to convince you to work in the industry? Rita Pater, from u2i, reminds us that programming was a typically female activity in the beginning. How did we come to this point when nowadays IT is overwhelmingly dominated by men? Is #MamoPracujwIT initiative even necessary then?</em></p><p><strong>Mamo Pracuj: Rita, during our conversation at your office you mentioned that IT was once female-oriented to such an extent that it was considered a job for women. Unfortunately, while working on #MamoPracujwIT we don’t feel like we push at an open door. There are plenty of stereotypes in this field which make it not such an obvious choice for women now… Why is it?</strong></p><p>Rita Pater: I still seek the answer to this question. I think this mindset is only in our heads and the steps that Mamo Pracuj takes are a milestone in the direction of changing attitudes among women.</p><p>Back in the 50s, when very few people thought about the actual programming, the duties were as follows: men took care of building hardware whereas women were responsible for providing the algorithms enabling it to work. Writing code was considered easier. Attention to details, diligence, patience and ability to reflect logical reasoning into code — these were all female traits.</p><p>According to the <a href="http://gender.stanford.edu/news/2011/researcher-reveals-how-%E2%80%9Ccomputer-geeks%E2%80%9D-replaced-%E2%80%9Ccomputergirls%E2%80%9D">article from Stanford University</a>, once men discovered software was more complex and challenging than they initially thought, they started to switch their careers in this direction. The perception of IT changed and programming wasn’t viewed as a simple and secondary task anymore. Professional associations started to emerge. They often allowed only male members.</p><p>MP: And that’s how guys dominated the IT industry.</p><p>RP: Yep, fast-forward by a couple of decades and the industry is firmly dominated by men — especially when it comes to the prestigious role of a software developer — but we’ve been noticing a change recently. Above all, education is widely accessible. There are no restrictions or implicit barriers that would prevent women from taking jobs in new technology. Of course, some stereotypes and prejudices have developed throughout the years, but when you encounter a mature company with a healthy and human attitude that doesn’t differentiate between male and female developers, there’s no such thing as a conflict between those two groups. In this case, organisational culture plays the most relevant role. Thankfully, I am a part of a company that embraces such a culture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*9QZmNSR9XmIqEVBF.jpg" /></figure><p><strong>MP: You work for u2i, a company which has hosted our workshops on programming and testing recently. What do you do at work and how do you find the IT industry?</strong></p><p>RP: I joined u2i a year and a half ago as a PR &amp; Brand manager. Since then I’ve been taking care of planning and the realisation of image campaigns on the local market (employer branding). But I’ve never felt as if I held a strict position and dealt with the same stuff all over again. You see, according to our organisation’s policy, we can contribute to a variety of “extracurricular” projects or groups. Because of it, the employees continue to develop their skills which in turn makes them more satisfied with their jobs. Therefore, my responsibilities have changed since I got here. Currently I’m involved in business development, coordinating efforts on the internal product and marketing strategies directly impacting the company’s development.</p><p><strong>MP: PR &amp; Brand manager among a couple of dozens of software developers… hmm… It seems like it’s impossible to have no clue of what your peers do. Do you? If so, where did you acquire such knowledge?</strong></p><p>RP: I come from the branch of event management. A couple of years ago I organised Blog Experts — the second greatest conference for semi-professional bloggers back then. Given the location, I took an interest in the startup community of Kraków, thus new technologies. I’ve been following the trends and achievements of Polish and worldwide tech companies ever since, being at the same time a strategist consulting their PR efforts. Before joining u2i I had a couple of years of experience in marketing for IT companies, so I knew what to expect.</p><p>Working for a software house whose clients are tech companies seemed like a challenge I was willing to face. Of course, there were some areas I had to catch up on. Thankfully, knowledge sharing is commonplace at u2i, so my colleges supported me in these matters.</p><p><strong>MP: Why do you value working in IT ? What convinced you and still convinces new candidates to become a part of u2i?</strong></p><p>RP: What amazed me the most was highly developed organisational culture, employee care , collective responsibility for everything u2i does, and last but not least, the flat structure which facilitates communication with the team as well as the management. I can still remember one of my first days here when I barely knew anyone. Somebody in the kitchen started a conversation by asking what my plans for the job were. We chatted for several minutes and it wasn’t until a couple of days later that I found out it was the founder of u2i, Tom Clarke, visiting Poland at that time. Personally, I’ve never got the feeling of having an actual boss at u2i. What I do know though, is that the company gathers some true leaders.</p><p>As to potential candidates — this May we launched the recruitment for the summer internships for students. We were astonished by the number of people applying — 150. I think what attracts people the most is openness and again the internal organisational culture we try to highlight in different ways. We are present at conferences, we support initiatives like yours, we make our space available for workshops. Every few months we throw a “Waffle Breakfast Party” gathering people from new tech, marketing and PR. Everything we post on our social media channels builds up an image of a company operating for over a decade in Polish IT.</p><p><strong>MP: Rita, u2i is a software house where the majority of employees are developers. How many of them are women?</strong></p><p>RP: There are 9 women at u2i, most of which are experienced developers. E.g. Marysia. She used to work as a full-time developer but she made a pivot in her career and now she’s a team leader. Due to the flat structure I mentioned before, we are not constrained by job titles. Quite a few times I’ve also been sung the praises of Laura, who embarrasses her male colleges in terms of technical skills!</p><p>MP: There is also Agnieszka, who was promoted just 3 months before giving birth.</p><p>That’s right, Agnieszka’s been with us for 8 years. In February 2015 she came back after over a year of maternity leave. Her comeback wasn’t as ordinary as for the majority of women though. Only when her son became 3-months-old, she took advantage of the vacations in order to improve her competences, learn new technologies and polish the skills she’d acquired at u2i before.</p><p>I remember Agnieszka working part-time from the office for a few months after the leave in order to get her son ready for the absence of both parents by leaving him with his nanny. A few hours of working remotely along with complete absence is what got the boy used to his momma’s busyness. He spent that time with his father or the nanny. Flexible work hours allowed her and the family to adjust to the transition in the least harmful way possible. Agnieszka herself is passionate about programming. Asked if she likes her job, she responded she couldn’t imagine herself in a different profession (even though her dream job as a child would be in the armed forces).</p><p>Ever since I immersed myself in the field of new technologies, my view has changed significantly. From what I’ve noticed there is no such thing as monotony here. Getting back to my talk with Agnieszka, she also told me she took pride in doing things calling for a different approach to every task which leads to day-to-day self-improvement. It was the ultimate confirmation of our outlooks on professional progression being alike. You can face new challenges and opportunities no matter if you’re a marketer or developer. Personally, I have never been more convinced that learning programming and working with new technologies is for both men and women and there’s no such term as boredom in our vocab.</p><p><a href="http://mamopracuj.pl/czy-programowanie-jest-dla-kobiet/">An original article</a></p><p>*Mamo Pracuj is an organisation teaching, empowering and supporting women who to go back to work after maternity leave.</p><p>Translated by Mateusz Kowal</p><p>Author: <a href="http://www.twitter.com/ritapater">Rita Pater</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b84cb843dbe4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/u2i-blogs/is-programming-for-women-b84cb843dbe4">Is Programming for Women?</a> was originally published in <a href="https://medium.com/u2i-blogs">u2i’s lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Summit — over 50 thousand tech people vs Lisbon]]></title>
            <link>https://medium.com/u2i-blogs/web-summit-over-50-thousand-tech-people-vs-lisbon-4d8ab8992475?source=rss-2f109c7692d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d8ab8992475</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[websummit]]></category>
            <category><![CDATA[events]]></category>
            <category><![CDATA[lisboa]]></category>
            <dc:creator><![CDATA[u2i]]></dc:creator>
            <pubDate>Thu, 18 May 2017 12:53:56 GMT</pubDate>
            <atom:updated>2017-05-18T12:53:56.027Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Web Summit — over 50 thousand tech people vs Lisbon</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*NL6vwWlJQfJPtvea7bhhaQ.jpeg" /></figure><h4><strong>Tech Lisbon?</strong></h4><p>Web Summit is — without a doubt — the biggest tech conference in Europe.</p><p>This year’s event took place in Lisbon, Portugal. I’ve never thought of Lisbon as a tech city, but hey! Life is full of surprises!</p><p>Imagine yourself landing at the airport just a few stops away from the venue. There are signs welcoming the guests, volunteers checking you in, people smiling everywhere, striking up conversations with other attendees.</p><p>Then, the world turns bright white as your eyes try to adjust to the sunlight (because sunny autumn in your country has already turned into grey days). The city is full of tech people wearing wrist bands, enjoying the lively networking atmosphere in the Bairro Alto district or dancing by the riverbank next to the Ponte 25 de Abril which looks like the Golden Gate.</p><p>And so you walk through the narrow and steep streets of Lisbon, passing by pedestrians with a fellow conference participants. All around you people are smiling, talking business in the subway, on the bus or in restaurants. And you’re part of it all. All it takes is to reach out to the person sitting at the table next to yours, starting the conversation with simple ‘Hi’ and finishing it with an exchange of business cards, or just scanning badges to plan a business meeting or schedule a call next week.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kM3yhp93UoN7nSK4.jpg" /></figure><h4><strong>50 thousand tech people — what could possibly go wrong?</strong></h4><p>As a team, we didn’t have any specific goals for the event. We just wanted to meet interesting people and to build our network, which honestly is inevitable when you take part in a conference of such scale. Entering the venue, or even walking down the street, I felt as if I was diving in the networking sea. Everyone I talked to was interested in new tech and worked for the IT sector.</p><p>With 50 thousand people from tech staying in this historic city over a week, anything could go wrong, but as far as I’m concerned nothing major did! WiFi could use some improvement and the on-site coffee was, to be delicate, rather bad, but thankfully Facebook and their coffee machine saved the day!</p><h4><strong>Women in Tech area</strong></h4><p>As one of the women invited to the conference, I had access to the Women in Tech area, where we could share our experience with business developers, marketing strategists, software developers, entrepreneurs, etc.</p><p>I spent one whole day there and it was totally worth it. Conversations about smart city solutions with Suvi Hakamies from <a href="http://gnf.fi/en/home/">Green Net Finland</a> and with Linda Koivunen from Pre-Ohjelmistot Oy. Chatting with Filipa Larangeira from <a href="https://orangeboom.co/">Orange Boom</a>, Iwona Gruszka from <a href="http://iwonagruszka.com/#iwonagruszka">Discovering Success</a>about the power of building the community support around the IT sector and about successes and failures of startups. Together with Kai Ping Chang from <a href="http://www.techmoi.com/">Techmoi international Ltd</a>, searched to define what makes a successful business and how to support the processes to make them more effective. It was a really intense time!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0ELLOPhgR5eiBUDK.jpg" /></figure><h4><strong>Side events</strong></h4><p>Also, we couldn’t forget about many side events worth exploring over the week! I joined a local <a href="http://www.geekettes.io/">Geekettes</a> event, which took place in the amazing spaces of <a href="https://www.uniplaces.com/">Uniplaces HQ</a>. The main part of the event was a panel discussion about diversity in tech between Lu Li Founder and CEO of <a href="http://bloomingfounders.com/">Blooming Founders</a>, Filipa Larangeira — Founder and CEO of Orange Boom, Hollie Haggans from <a href="https://www.digitalocean.com/">DigitalOcean</a>, Ida Tin from <a href="https://www.helloclue.com/">Clue</a>, Ana Sofia Pinho — Geekettes Ambassador, and Leslie Miley, Director of Engineering at <a href="http://slack.com/">Slack. </a>After the event we had a chance to talk with Danny Bronstein and Danny Povolotski from <a href="http://www.caffeine.co.il/">Caffeine — Design and Development </a>about building company reputation in the local markets. It was really interesting to get to know the points of view of people from all over the world.</p><h4><strong>Talks, trends, innovations, startups?</strong></h4><p>If you come to Web Summit to get inspired, you sure will get that — not only watching talks. If you’re searching for trends, innovations, and startups, this conference is the place where you meet all the people standing behind them. And that’s the thing — when asked about what brings half of the tech world to this conference — I would definitely say ‘the atmosphere’ — conducive to networking and talking about business with the right people.</p><p>Author: <a href="http://www.twitter.com/ritapater">Rita Pater</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d8ab8992475" width="1" height="1" alt=""><hr><p><a href="https://medium.com/u2i-blogs/web-summit-over-50-thousand-tech-people-vs-lisbon-4d8ab8992475">Web Summit — over 50 thousand tech people vs Lisbon</a> was originally published in <a href="https://medium.com/u2i-blogs">u2i’s lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting up a self-learning group in your company in 14 steps]]></title>
            <link>https://medium.com/u2i-blogs/setting-up-a-self-learning-group-in-your-company-in-14-steps-b12a66336c7?source=rss-2f109c7692d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/b12a66336c7</guid>
            <category><![CDATA[golang]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[self-learning]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[u2i]]></dc:creator>
            <pubDate>Thu, 18 May 2017 12:43:42 GMT</pubDate>
            <atom:updated>2018-01-04T15:01:27.409Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DdL-dd7EXB-ZaiJYCifCsQ.jpeg" /></figure><p>So you’ve just heard about a new, cool, bleeding-edge technology. You want to learn it. After all, you know that programmers need to constantly broaden their knowledge, right? Right. You can just sit down on your own, learn it yourself and be proud of knowing it. But you think that it might be also useful to your company. Would it be worth spreading this knowledge? Maybe you’ll be able to introduce something new to your company’s tech stack? Who knows. So you decide to give it a try and create a group for learning that-new-thing. You don’t know how? Very good. Read on. <strong>Here’s a step-by-step guide how to organise a self-learning group</strong>, introduce a new technology to the company, find motivated people and help them have fun while doing it.</p><h3>A little background</h3><p>At u2i we work with a bunch of different technologies, from frontend JavaScript frameworks to serious backed cloud tools handling lots of data. But sometimes it happens that some different technology from outside the usual stack grabs our attention. We might not have a good place for it in our production stack yet, but we feel that it’s so cool that someday it might be useful to one of our clients. What do we do then? Self development time to the rescue!</p><p>Every employee at u2i may use <strong>4 hours a week of their time to do anything they like</strong>. It’s similar to famous Google’s <em>20% rule</em>. The difference is that we’ve got only 10% (but we still have it, while Google changed its mind) and that this time doesn’t necessary need to be spent on something directly beneficial to the company. We can use it for anything, like developing side projects, doing tutorials, reading technical books, writing blog posts, playing with Arduino — you name it. One general rule is that you have to do something for your own development.</p><p>Self development time fits perfectly when we want to learn something new. Especially if that something is not immediately useful for our professional work. We believe also that the best results might be achieved when working together. That’s why we started experimenting with <strong>self-learning groups</strong>. These are voluntary groups of employees who want to learn something new together using their 10% time. Here are a few things we learned about how to get things going.</p><h3>A step-by-step guide to a self-learning group</h3><p>Are you ready to start your own group? Here are the ideas!</p><h3>1. Be a leader</h3><p>One of your goals might be to create a self-organizing group. That’s fine. Noble even. U2i has a long history of different collaborative initiatives. Some of them were successful, others ended after the first meeting. We don’t have a silver bullet for success, but we know for sure that having a leader at the beginning can help a lot. Someone to establish it, set the initial pace and care about where the group goes. When your group loses momentum, the leader is the person to step in and bring the fun back. You should be that leader. Keep in mind that will require some significant effort on your part, especially at the beginning. But on the other hand it also brings a lot of satisfaction.</p><h3>2. Do the research</h3><p>You already know what technology you want to learn. Now you have to do the research. <strong>Find out general information about it, what are its features, where it aims, where it might be useful, what are the pros and, more importantly, the cons.</strong> Get some general knowledge about the market, similar tools, competitors. Think how it can be used in your company. Be ready to explain your decision. If you want people to spend some time with it, you’ll have to convince them that it wasn’t a random choice.</p><p>Don’t go too deeply into the topic. You don’t have to gain any serious proficiency in it. It’s fine to say that you haven’t written a single line of code in your technology yet. Just be aware of its features and possible downsides.</p><h3>3. Create a communication channel</h3><p>A communication channel is a good thing even if you work in a small company (like we do). At the beginning it’ll be useful as a staging point for people interested in joining you. Later on you’ll use it for organisational purposes and for posting useful stuff regarding the topic of your group. From our experience it works as a good way to facilitate a constant discussion during the time between meetings. You can use IRC, HipChat, a mailing list, a discussion board or whatever works for you. We use Slack. It works very well as a general communication platform gathering all in-house conversations. When we form a new group we just create a new Slack channel.</p><h3>4. Give a talk</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*gD2WAdZHHSjE9mtQ.jpg" /><figcaption>Me giving a talk about cool languages</figcaption></figure><p>Give a talk at your company about the technology that you chose (at u2i these kind of short presentations are called <em>techspressos</em>). <strong>Share the knowledge you gained during your research.</strong> You’ll get some immediate feedback on how people react and what they think about the technology. At the end announce the start of a self-learning group and mention the communication channel that you created earlier. Hopefully you’ll find some people ready to join you. You’re targeting those who are eager to learn something new, but maybe not motivated enough to do it by themselves. If they see that you’re going to take care of the whole process and give them an opportunity to gain some knowledge easily, they’ll automatically become more interested.</p><p>If you want to gain some inspiration on what this talk can look like you can take a look at my <a href="http://www.slideshare.net/MichaKonarski1/ruby-is-dying-what-languages-are-cool-now">slides about cool programming languages</a>. I talked about the recent, most promising, yet not very popular languages. My aim was to keep my colleagues up-to-date with the latest technologies and at the same time find people interested in learning the one I found most interesting — Golang. It worked great — a few days later the group was established and ready to take off.</p><h3>5. Create an agenda for your group</h3><p>Now that you’ve gathered your participants it’s time to create the agenda. At the very first meetings of the Golang group we didn’t have an exact plan for what to do. Nobody had written a single line in it, so we needed to start from the very basics. On the other hand we felt that sticking too long to the theoretical part would affect the group’s motivation. What worked best for us was to divide the program into two parts: <strong>the</strong> <strong>learning phase</strong> and <strong>the</strong> <strong>implementationphase</strong>.</p><p>During the <strong>learning phase</strong> you and your group will get to know the basics of the technology, familiarize yourselves with the tools and the ecosystem. One good way of going about it is to find an online tutorial or a course describing the topic and just follow it. That way you can let people learn on their own and use regular meetings only to discuss their experience and any problems they might have encountered. This part shouldn’t take too long, because people may eventually get bored with working with theoretical content only. What we find reasonable is to spend 3–5 weeks while meeting every week. That should give your participants enough time to get familiar with the topic in their own pace.</p><p>The goal of the <strong>implementation phase</strong> is to create a useful piece of software. The best way to learn is to use the knowledge in practice. Meetings during that phase will be used for designing, problem solving and coding. The length and frequency of the meetings may vary depending on the number of people, their involvement, the amount of free time they have, the specifics of the project and many other factors. Initially try not to put any time limits here. You’ll see how it goes.</p><h3>6. Gather your group for the first meeting</h3><p>Start with finding a good time in everybody’s calendar and create a recurring event. When it’s set it’s harder to skip it. Invite everybody to the first meeting. Prepare a list of recommended materials, links to documentation, cheat sheets and instructions on how to setup a development environment. Anything that can be useful to start learning as quickly as possible. Your participants will be happy to see that they can just focus on content, rather than searching through the Internet to find why some library doesn’t compile. A well prepared boilerplate can go a long way in this respect.</p><h3>7. Post interesting stuff regularly</h3><p>Look for blog posts, conference videos, GitHub repositories, Reddit news, new release announcements and any other useful content regarding your topic and post them on your communication channel. Not only will people use them to stay up to date, but also get the impression that something’s constantly going on. It’s usually very motivating when you feel somebody really cares.</p><h3>8. Go through the learning phase</h3><p>What worked best for us was to leave the meetings for <strong>exchanging thoughts and comments only</strong>. Ask people to do the tutorial (or any other content that you chose) between the sessions. This way everybody can think at their own pace and tackle problems individually.</p><p>On the meeting connect your computer to a bigger screen and use it to go through the material. <strong>Focus on things that you found particularly interesting or tricky.</strong> Make sure everybody gets general understanding of it. Encourage people to take part in the conversation. At the end tell the participants what the topic for the next meeting is. You can even ask them to do some coding as homework. Don’t be surprised if people don’t do it though. It’s normal. Make sure to politely remind them during the week about the next meeting and its topic.</p><p>Remember that the aim of this phase is<strong> not to teach people everything</strong>. It’s okay if afterwards they say that they still don’t know much about the topic. It’s only to show them the general concepts and places where they can find useful information. They’re gonna learn stuff for real during the implementation phase.</p><h3>9. Encourage people to prepare something on their own</h3><p>If you feel that your participants are eager to do something more, give them a chance. What worked best for us is the idea of <strong><em>lightning talks</em></strong>. They are very short (5mins — 10 mins) and focused on some particular small topic. Ask people to prepare and present them. The topic may be e.g.: which IDE to use, what are the most popular testing frameworks, what are the tools to build binaries or manage dependencies. Examples of cool projects done with the technology might also be interesting. Remember to keep it short and don’t be afraid to enforce this rule. It may also be a great opportunity for participants to train their public speaking skills, but still in a controlled environment.</p><h3>10. Prepare for the implementation phase</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*ZHYCtYNWZRkuV5Lg.jpg" /><figcaption>Rocket science in progress</figcaption></figure><p>This phase is where the fun begins. You’re going to implement some real stuff here. It’s very important to choose a good project. <strong>An ideal one would be both interesting for your group and useful for somebody else.</strong> Maybe there’s something that your company needs? A simple app to help with ordering food or office equipment? A scoreboard for your foosball matches or console games tournaments? A tool to provide content for your TV dashboard? A Slack bot? A browser game you can use to entertain employees or promote your company? Speaking of games, maybe a modern clone of some classic arcade title? There are many possibilities. Brainstorm it with your group. The general suggestions are that:</p><ul><li>It should be fun for everybody! Don’t let your people get stuck in some boring project, because they’ll lose the motivation.</li><li>It shouldn’t be trivial or something that has been well described in articles over the Internet (like yet another blogging platform).</li><li>It should be relatively small. You should be able to create a working solution in weeks or months.</li></ul><p>In the Golang group we initially wanted to get involved in some open source project, but eventually changed our minds. We felt that we simply don’t know enough to make a meaningful contribution. And because we decided that doing something from scratch would bring more fun, we finally created a backend for a massive multiplayer galactic browser game.</p><h3>11. Implement it</h3><p>Start the implementing phase after you finish the material in the learning phase. This time you’ll meet your group to do some coding. It may be better to plan slightly longer sessions to have enough time to actually get something done. You may stick to your previous schedule or gather your group ad hoc, depending on how flexible everybody is with their time. When it comes to what the meetings should look like we found two options useful:</p><ul><li><strong>Mob programming.</strong> One person is coding on a computer connected to a bigger screen and everyone else gives their suggestions and ideas. We weren’t convinced by this method, but it worked surprisingly well in our initial meetings. It’s the time when many people are still far from being fluent in the technology, so it’s good to do it together. Of course the number of collaborators is limited. We successfully tested it with up to 6 people, but your mileage may vary.</li><li><strong>Pair programming.</strong> This is one of the fundamental values at u2i. We do pair programming on a daily basis in our professional work. Therefore, it was quite natural for us to adopt this way of working. To make it happen, let people divide themselves into pairs and give them some tasks to do. It may not work well in the first meetings, because there is not much written yet and it might not be easy to distinguish separate units of work that can be done independently.</li></ul><h3>12. Generate some publicity in your company</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*O1-bQIox1NhIeF2D.jpg" /></figure><p>It’s good when other people in your company know that your group works on something interesting. Make sure they have a chance to notice your efforts. You may prepare some kind of <strong>visual identification for your group</strong> in a form of posters, stickers, labels or anything else. It has two advantages: you make your group more self-aware and it helps to find new people willing to join you.</p><p>Remember the massive multiplayer game I mentioned earlier? It’s called <em>Superstellar</em>. It’s placed in outer space where players fly their spaceships. To create an atmosphere, the developers received paper desk stands with NASA-like names that <strong>symbolized</strong> some imaginary departments of our “galactic company”. We also prepared a sheet of paper with our project’s logo that we put on the conference room’s door every time we gathered to do the implementation phase meeting.</p><h3>13. Your group lost motivation?</h3><p>It happens. It happened to us several times. The most important thing is that you — the leader- are still motivated. Try to prepare something on your own and present it to the group. Maybe implement some cool feature in your app? Or show them some interesting talk? It’s important to remember that it’s your responsibility to take care of your group. And the general rule is: carry on even if there’s only one person left besides you. Motivation is contagious.</p><h3>14. Finish</h3><p>It’s essential to plan with an end in mind. People work better when they have some clear aim and feel better when they succeed in completing it. After some time of development sit down and <strong>choose a set features you would like to implement</strong>. This will be your target (or to use the startup world’s terminology — your MVP). Don’t go too far with it. It’s better to plan something smaller, but more reachable. Write down a list of chosen features and put them into some project management tool, like Trello.</p><p>Once you finish your MVP share it with the rest of your company. Prepare a presentation and describe what your group has learned, show your project and ask for feedback. Announce an official <strong>end of the learning group</strong>. That doesn’t necessary mean that you should stop working on the project. Based on feedback, people’s involvement and motivation you’ll decide if you want to continue the project or not. Maybe you’ll hand your project over to somebody else and establish a new self-learning group?</p><p>Curious about <strong><em>Superstellar</em></strong>? Take a look <a href="https://medium.com/u2i-blogs/we-made-a-multiplayer-browser-game-in-go-for-fun-242a5990ce29">here</a>.</p><p>Author: <a href="https://twitter.com/mjkonarski">Michał Konarski</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b12a66336c7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/u2i-blogs/setting-up-a-self-learning-group-in-your-company-in-14-steps-b12a66336c7">Setting up a self-learning group in your company in 14 steps</a> was originally published in <a href="https://medium.com/u2i-blogs">u2i’s lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Things We Learned When Recruiting for Internships]]></title>
            <link>https://medium.com/u2i-blogs/things-we-learned-when-recruiting-for-internships-e4d6b01278f7?source=rss-2f109c7692d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4d6b01278f7</guid>
            <category><![CDATA[recruiting]]></category>
            <category><![CDATA[hiring-tips]]></category>
            <category><![CDATA[internships]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[company-culture]]></category>
            <dc:creator><![CDATA[u2i]]></dc:creator>
            <pubDate>Thu, 18 May 2017 12:35:07 GMT</pubDate>
            <atom:updated>2017-05-18T12:35:07.321Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sY2K66dpWI2cKmlu1yMgvw.jpeg" /></figure><p>In u2i we’ve been hiring students for years. The thing we absolutely value is the fresh and open-minded approach students tend to bring to the company. They usually have a different view on things that our senior staff have been doing in one particular way for years. Also, given the right environment they can grow into awesome developers with a quickness.</p><p>All that said, we’ve never really had <em>very</em> junior people joining u2i. We’ve been aiming at more experienced students that already took their first steps in other companies.<br>One day, an idea came into our heads — “What if we’re missing something?”<br>We decided to give it a try.</p><h3>The Idea Behind the Internship</h3><p>The sad truth of most of the universities is that they miss a lot when it comes to teaching software engineering. Projects focus on one particular engineering problem without considering the big picture and various challenges that show up. The classes often utilize outdated engineering practices and tools.<br>We wanted to give students a chance to work on a real product. Ideally, that would involve working with one of our regular clients, however it was impossible at the time because of our current arrangements with clients.</p><p>We set up an internal project. There are a lot of small things that we struggle with on a daily basis that can be improved with software, so we picked one of the problems and made a project out of it.</p><p>When it comes to organizational things, we decided to build a team of a few interns (4 to 6), that would work in the same way u2i’s regular employees work.<br>Besides that, we didn’t want to differ internships from regular work at u2i (that means pair programming, agile process and constant collaboration with clients).<br>We involved a few employees in the internship: a scrum master to make sure the team can do its work without obstacles, a product owner who can define the project (their client) and a few “mentors” who could help them if they have problems with technology.</p><h3>How We Interviewed Candidates</h3><p>The recruitment process for the internship was very similar to our usual recruitment. The major difference was that we didn’t expect candidates to have in-depth knowledge of any technology.</p><p>The first step was an automated coding test. We expected to get a lot of applications and we were aware that not all candidates would advance to the interview stage. We knew it’s not a perfect solution, but unfortunately it’s the only feasible one.</p><p>Most of the automated coding tests check hardcore algorithmic and speed-coding skills. We’re a software engineering company, far from doing abstract mathematical things.<br>That’s why we created a small workaround — we picked a few very easy programming tasks and set the time limit to a few hours.<br>This way our candidates didn’t have to work under a lot stress and didn’t have to hurry to solve these tasks.<br>Furthermore, it allowed us to select those who are comfortable writing code and carefully test their solutions.</p><p>After this initial stage, our 150 applicants shrank down to a pool of just over 40.</p><p>40 is still too many to interview (especially for a company of our size), so we still needed another way to narrow down the list of candidates.<br>We did it just like every HR professional would do it. We went through their resumes.</p><p>As I’ve mentioned before, we didn’t care much about prior experience.<br>Still, we highly value students that do more than just what teachers tell them to.<br>When reading resumes, we looked for cool side projects, participation in student organizations and the most basic knowledge of various programming languages, frameworks and tools. We looked for people who like playing with technology.</p><p>This left us with 24 people, which was a doable number of interviews.</p><p>There were two core competencies we wanted to check during the interview.<br>The obvious one was technical skills. We wanted to see if each candidate knew the very basics of software engineering, how they approached problems and if they felt comfortable getting their hands dirty and writing simple code in their favorite programming language. Yes, we used whiteboard for that.<br>The other thing was soft skills. No one works alone at u2i; every single developer works within a team and communicates directly with clients. It’s a part of our culture, so naturally we wanted to hire students who fit into it. Soft skills are often mistaken for being overly open and enthusiastic. The thing we really care about is being able to explain things to other people and work together on solving problems. That’s crucial for a positive and effective work atmosphere.</p><h3>A Few Mistakes We Made</h3><p>There were three important lessons we learned on our first approach to internships, mostly due to wrong assumptions we made.</p><p>Let’s start with the number of interviews. We had a pretty tight timeline, so we needed to do all of them in two weeks. We decided to optimize things a little bit and squish as many interviews into a single day as possible. It’s didn’t take long until we realized that 5 interviews in one day is a bit too much for a recruiter. Proper and in-depth interviewing can be very exhausting, and not only for candidates.</p><p>The second thing was giving feedback. If, after a regular interview we decide not to hire someone, we do our best to provide them with some feedback. We like to be clear on why we didn’t hire someone and in some cases we are able to give them advice on how to become better developers.<br>We hoped to do the same thing during the internship recruitment, but once again the number of candidates made that an impossible goal. We ended up sending general messages to most applicants, with a few exceptions if there were obvious things they could easily improve.</p><p>The last mistake was our skepticism towards 1st year students. We assumed that they would lack certain engineering knowledge usually gained in the later years of their studies. For some time we didn’t even consider inviting them for an interview, but later we decided to give them a chance. It turned out some of them have comprehensive knowledge (especially for a 1st year student). We even hired one of them.</p><h3>And a Few Things That Went Well</h3><p>On the other hand, some things went absolutely fantastic.</p><p>There’s a known bias that during interviews interviewers remember the first and the last person the most (and often make decisions in their favor). We didn’t want order to be a factor in our process, so we decided to make decisions right after each interview. This worked really well. A few days later we noticed that we don’t remember most of the interviews and if we held the evaluation off, it would’ve been impossible.</p><p>The other thing that went well was that we were able to hire people who make up a great team.<br>Our experiences with building teams is that teams that consist of very similar people are not especially effective. One of our goals was to hire people with slightly different sets of skills and personalities.<br>Before the interviews, we agreed on what kind of skills could be useful for the team to have.<br>We ended up with a great, complimentary team.<br>There’s a frontend expert, rails passionate, a guy who knows good engineering practices, all sharing knowledge. This all works well both for them (knowledge sharing) and for the project.<br>Surprisingly, we also ended up with a mix of personalities. There are interns who bring a lot of energy to the team, as well as people who calm the team down in case of crisis. It’s just brilliant.</p><p>Finally, the thing we’re really proud of is that our offer was clear to everyone.<br>We gathered a lot of feedback (also from people we rejected) and almost everyone agrees that everything they needed in order to apply or accept our offer was explained. There was no unnecessary mystery involved.</p><h3>Summary</h3><p>So far, our internship program has gone very smoothly. We learned a few important things when recruiting interns for the first time and we’ll be able to improve these things next summer.</p><p>We’ve just finished the internships, so we’ll be back with another assessment of our findings in the middle of October.</p><p>Author: <a href="http://www.twitter.com/@rafalcymerys">Rafał Cymerys</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4d6b01278f7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/u2i-blogs/things-we-learned-when-recruiting-for-internships-e4d6b01278f7">Things We Learned When Recruiting for Internships</a> was originally published in <a href="https://medium.com/u2i-blogs">u2i’s lab</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>