<?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 Marta Gajowczyk on Medium]]></title>
        <description><![CDATA[Stories by Marta Gajowczyk on Medium]]></description>
        <link>https://medium.com/@gajowczyk.marta?source=rss-589fc41d0bf1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*4pl1trRnzxSrcN5VZDbVQw.jpeg</url>
            <title>Stories by Marta Gajowczyk on Medium</title>
            <link>https://medium.com/@gajowczyk.marta?source=rss-589fc41d0bf1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:57:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gajowczyk.marta/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[How to be new at LaterPay]]></title>
            <link>https://medium.com/supertab-behind-the-scenes/how-to-be-new-at-laterpay-7b05389d57a5?source=rss-589fc41d0bf1------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b05389d57a5</guid>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Marta Gajowczyk]]></dc:creator>
            <pubDate>Tue, 19 May 2020 06:47:25 GMT</pubDate>
            <atom:updated>2020-05-19T06:47:25.448Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>My name is Marta and I joined LaterPay’s remote team as a Frontend Software Engineer around one month ago. You know how it is; starting a new gig is stressful in itself and that’s why onboarding is so important. I had a great onboarding and I decided to share my experience. This post was written originally for the internal folks that are starting at LaterPay but hopefully you can benefit too from learning more about what it’s like to join LaterPay.</blockquote><p>Hey there! You must be new. And you’re probably wondering how you can make the best impression on your first day. Just like I did, you’re probably thinking that you should already be up to speed with a running repository, reviewing pull requests and shipping a new task tomorrow at the latest.</p><p><em>Relax.</em></p><p>We’re not expecting you to know it all right away. Take your time! You first need to swim through the pile of emails that are ready waiting for you in your inbox. All the accesses that you’re going to need the next following days and weeks. And if you find yourself not having access to, let’s say, BrowserStack, just fire away a question at a relevant channel (don’t worry, they’re categorized) and someone will be right there to help you. Slack is our virtual office so make <em>sure</em> to browse through the social channels to start creating your network. For example, the first channel I joined was #social-pets. Don’t judge me, I’m always eager to meet other people’s pets.</p><p>The first days you might perceive to be a bit slow. Focus on navigating the channels, have virtual cappuccinos with people to get to know them and take notes. I took <em>a lot of</em> notes in my first weeks. I may never go back to them again but it’s a great way to retain information and you’ll get into the habit of writing things down. Documentation is key at LaterPay.</p><p>As part of my onboarding process I had to complete a Jira epic that involved gathering insights from other people on how to be new at LaterPay and you’re probably assigned something very similar. I was asked to talk to my teammates and ask them for advice on how to get around the company when you’re new and, in general, to get to know them a bit better. At LaterPay human relationships are acknowledged and encouraged because we understand that working with people that you took the time to get to know is easier and more productive. Make sure to build that<a href="https://slackhq.com/psychological-safety-building-trust-teams"> psychological safety</a>.</p><p>That should be it for your first week. You’ll have a lot of onboarding meetings as well (check your Google Calendar) ranging from Product introduction, 1on1 with your onboarding buddy, 1on1 with your line manager, 1on1 with your Tech Lead, intro with Engineering Managers and, depending on the team you’re joining, intro to your tech stack and the like. Prepare yourself mentally for much socializing and if that isn’t your thing don’t sweat it and just divide it between the weeks so that it’s comfortable for <em>you</em>.</p><p>In the second week you might start feeling itchy about the fact you haven’t coded in a while. That should be your cue and you might want to start familiarizing yourself with the codebase and ask your team what would be the best task to start working on. In my case, I was lucky because my team was in the process of rolling out a new product. I could contribute by doing Quality Assurance and at the same time it was a massive learning experience for me. By doing QA you can learn about the different workflows of your application and explore various use cases it is satisfying. You may also find a bug or two before rolling it out to production. I can’t recommend this method enough but it depends a lot what stage your team is on at the moment. On the other hand, you can always pretend that you’re trying to find bugs and that will also work. Another great way to get you up to speed is to ask for a task that is preferably covering a lot of the product so you can get exposed to a lot of context. But, rest assured, it will still take a while to get the full picture and that’s OK.</p><p>A great piece of advice I got from my colleagues was to pretend to be a merchant and try to integrate with LaterPay products. This way you’ll be able to test different ways of integration, understand how different pieces of the product work together and help you connect the dots. During my first month, we had All Hands. All Hands is a week-long get-together of the whole team that takes place twice a year at LaterPay where we’ve got work-related sessions but also water-cooler gatherings. This year it all took place remotely due to obvious reasons (it’s year 2020 and we’ve got global pandemic). Two of the sessions were about acting as if you’re a publisher and trying to integrate with a product via <a href="https://docs.laterpay.net/connector/integration/connector_script/">Connector Script</a> and <a href="https://www.laterpay.net/academy/the-laterpay-wordpress-plugin">Wordpress</a>. It is an insightful exercise and will give you an entry to the rabbit hole to which you want to jump down to; it’ll make you dive into documentation, code and will spark many a-ha moments. Don’t hesitate to share your feedback afterwards if you decide to have a go at it.</p><p>Pair-debugging and pair-programming are always a good idea but especially when you’re a new team member. It will help you understand the context of the product and you’ll be able to follow the stream of thoughts of your pair-debugger that will trigger a lot of questions you may have.</p><p>Feel free to treat this manual as an inspiration. What worked for me might not necessarily work for you. Just remember to take it easy, reach out to people, seek out knowledge and you’ll be fine 🙌</p><p>Are you a bullet points type of person? So am I. Here’s a TL;DR version of this post:</p><ul><li>Join #social- channels 🐶 🥐</li><li>Connect with your teammates ☕</li><li>Connect with people from your functional area 👩‍🔬👨‍🔬</li><li>Browse Confluence 📎</li><li>Browse LaterPay docs 📃</li><li>Over-communicate 🖊</li><li>QA the product 🐞</li><li>Coordinate with your team what first tasks they recommend you to have a look at 👩‍💻</li><li>Integrate with LaterPay using various ways of integration — talk to your PM or a tech lead and they can help you get started 🚀</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b05389d57a5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/supertab-behind-the-scenes/how-to-be-new-at-laterpay-7b05389d57a5">How to be new at LaterPay</a> was originally published in <a href="https://medium.com/supertab-behind-the-scenes">Supertab— Behind the scenes</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[20 things to make your life easier as a developer]]></title>
            <link>https://medium.com/vizzuality-blog/20-things-to-make-your-life-easier-as-a-developer-1ee972f9317f?source=rss-589fc41d0bf1------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ee972f9317f</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[soft-skills]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Marta Gajowczyk]]></dc:creator>
            <pubDate>Wed, 29 Jan 2020 20:59:37 GMT</pubDate>
            <atom:updated>2020-02-03T09:58:30.372Z</atom:updated>
            <content:encoded><![CDATA[<h3>20 things to make your life easier as a developer.</h3><p>The life of a developer ain’t easy. We live double lives, torn between idealistic ideas (yackety-yack?) of a top-notch software quality and, well, life; deadlines, cutting corners and writing software without a single test. I know, I know, but uncover your bleeding ears, that’s the truth — your code will never be perfect because the circumstances will never be ideal. But here’s what you can and definitely should do to make your life as a developer better and easier for those (the future you counts as well) who will work on your code after you.</p><p>Have you ever worked on a piece of code that you couldn’t understand and after an hour of trying to understand what the heck is going on, you’d go in your VSC and hit Git Blame and you’re like <em>I swear, whoever wrote that code…</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/1*gcniB2fJY3CoKmaHdeOTmA.png" /><figcaption>StateOfTheArtComponent<em> my ass…</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/553/1*EdP97QygSDoZKa5lTcKhew.png" /><figcaption>Who the hell wrote it…</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/267/1*lmEmup2bzwzu0cAnOcmQuA.png" /><figcaption>Oh…</figcaption></figure><p>Yeah. Sounds familiar?</p><ol><li><strong>Document your code</strong></li></ol><p>Other people do not have the same context as you have. It might be as simple as naming the variables correctly as a way for your code to be self-explanatory. Do not use mysterious abbreviations; rename that getA to getActiveLayer — you might be surprised how misleading it can be.</p><p>Review your README file. When a new person comes aboard you want to make it smooth for her. You don’t want her to lose precious time on her first day on fighting with something as straightforward as setting up the project. You’re that newcomer and some things are not up to date in the README? Drink some herbs, swallow your frustration and FIX IT. Remember that the best way to teach others good practices is by setting an example yourself.</p><p>2. <strong>Do not trust the server</strong></p><p>…or anything that comes from outside into your shiny component. Check for nulls, implement fallbacks for potential errors or nonexistent data. I don’t care that the API promised to give these results; if it won’t, that’s your page that’s going to crash.</p><p>3. <strong>Communicate decisions</strong></p><p>Or better. Include your team to make them together. You’re just starting a new project and thinking of what routing solution to use. Or thinking of a perfect git flow for your use case. Communicate your thoughts and assumptions clearly but be open to other people’s suggestions. Do not leave it out of the discussion and go silently; you will leave your junior developers confused while it’s a perfect opportunity for them to learn about how you go about making decisions. And you never know, others may surprise you with a better solution to the problem. Once you all agree, go to step 1 and document that for future developers.</p><p>4.<strong> Estimate honestly</strong></p><p>Hey. I’ve been there. Deadline’s approaching and you want to get it over with. But that’s you right there lying to yourself. Estimations are hard so don’t make them even harder by assuming the best scenario. You might be thinking that this dropdown looks fairly easy; you used it a thousand times before and you implemented it, well, a bit fewer times. But have you considered the data parsing that’s included in this task? BTW, you know that the backend isn’t ready yet, right? And you remember that the backend engineers are evil and are not going to serve you the format that you’d love to have, yeah? If you decided that you will use a library to write that dropdown component, have you checked how to change the default CSS styles? How can you add functionality that’s missing? Is it even worth using that external library or better write your own? Think of all of these cases when estimating tasks. Have I convinced you to scratch out those 4 hours you initially thought of?</p><p>5.<strong> Give a thorough description of your PRs</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/707/1*DntpTyINgL6bEE0t9UdVng.png" /></figure><p>Maybe if you’re a mind reader you might know what are you going to be reviewing. I doubt it though, I think that person would have to sit with you in the same room and you’d have to be a 17th-century witch. The more information and context you give about your PR, the better; write about the business logic you introduced and that CSS !important you <em>had to </em>use because you’re using a 3rd party library — you will save yours and your reviewer’s time on reprimanding you about that !important and you explain why you had to use it. Before you open a pull request; give an additional scroll through the changes you made. Maybe you forgot about removing that <em>console.log </em>or you left a <a href="https://codeburst.io/software-anti-patterns-magic-numbers-7bc484f40544">magic number</a>.</p><p>6. <strong>Lift as you climb</strong></p><p>If you already have a couple of years of experience, you might not remember how difficult it was when you were a junior developer (<em>zapomniał wół jak cielęciem był</em>). Mind you that you also can be a junior in things that you haven’t encountered yet. We all have these moments at least a couple of times a day. Mentor others; explain why you did things the way you did. Come up with new metaphors for that <em>reduce </em>function. Do a pair programming session. Give a hand once in a while. Suggest someone else lead that meeting. Be kind in the process and be humble, no one likes condescending people.</p><p>I promised 20 things but here you have 6. You probably already hardcoded 20 items and now you have 14 <em>undefined’s. </em>Oh well, <em>don’t trust the server </em>and stay tuned for more 📻 🙌</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ee972f9317f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/vizzuality-blog/20-things-to-make-your-life-easier-as-a-developer-1ee972f9317f">20 things to make your life easier as a developer</a> was originally published in <a href="https://medium.com/vizzuality-blog">Vizzuality Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>