<?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 Emelie Lindblom on Medium]]></title>
        <description><![CDATA[Stories by Emelie Lindblom on Medium]]></description>
        <link>https://medium.com/@lindblom.emelie?source=rss-f9d44bad11df------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0kyttQN-Vyn_sldj5GlJLA.png</url>
            <title>Stories by Emelie Lindblom on Medium</title>
            <link>https://medium.com/@lindblom.emelie?source=rss-f9d44bad11df------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:37:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lindblom.emelie/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 few valuable things from my journey in a web development boot camp.]]></title>
            <link>https://medium.com/@lindblom.emelie/a-few-valuable-things-from-learning-programming-in-a-boot-camp-8c28d5d6c72d?source=rss-f9d44bad11df------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c28d5d6c72d</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[bootcamp]]></category>
            <dc:creator><![CDATA[Emelie Lindblom]]></dc:creator>
            <pubDate>Sun, 05 Dec 2021 16:16:46 GMT</pubDate>
            <atom:updated>2021-12-05T17:12:04.643Z</atom:updated>
            <content:encoded><![CDATA[<p>As I’m wrapping up my fourth sprint as a front-end developer student at Technigo’s web development boot camp, I have looked back on passing yet another four weeks learning React and Redux. I’ve built a quiz using global state in redux in a mob programming project, created a todo-list by building my own reducers and actions, built a labyrinth game by learning how to use API’s together with redux in a pair programming project, and lastly, I finished off this sprint by building my first mobile app with React Native. In this article, I want to write about a couple of things I’ve been doing on a weekly basis and that has become an essential part of my learning process.</p><p><strong>1. Reviewing other people&#39;s code.</strong></p><p>This industry-standard practice is included in the boot camp — I’m talking about code reviews. Each week we are reviewing a fellow developer’s code from the previous week&#39;s project and get our own project reviewed in return. It is a great way to practice to critically and analytically read code, I’ve learned so much from reading other people&#39;s code, getting inspired by their solutions, and enrich my understanding of how problems can be solved, and simply getting used to reading code that I have not written myself. In the beginning, it might feel uncomfortable to give feedback on someone else&#39;s code, but this approach has helped me to become comfortable with giving reviews.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*NZKoM1USwRDz5esRNgWtUg.jpeg" /></figure><p>First off, go into the review with an empathetic mindset, remember that the person has probably spent a lot of time and effort into their code. A good reviewer asks open-ended questions, assumes that the owner of the code might have missed something or forgotten something. Ask the question as a way to make the person have another look at the part of the code that raises questions. If you are having suggestions, suggest them as an alternative instead of insisting that your solution or alternative is a better way (or the only way), code reviews are a conversation! Even if the person ends up not embracing your solution/alternative it has given both of you additional knowledge in solving a specific problem.</p><p>Lastly, applaud and complement nice and impressive solutions and stylings and add them to your own toolbox. This contributes to open and positive teamwork and to a better quality of code.</p><p><strong>2. Working with agile methods.</strong></p><p>Just like in most developer teams we work in a team, in our case we are a group of 10, pending between individual projects, projects in pairs, or in groups of 5 on the same project. We have sprints of four weeks with a main learning objective each sprint and 4 projects with specific learning outcomes of the main theme. To gain the experience of working as a developer team we follow a few principles and adopted some key ceremonies from the agile methodology. One of the valuable practices we are doing on a daily basis is stand-ups. They are a short meeting to synchronize the team and to keep everyone updated on what each person is working on, what we plan to work on that day, if there are any blockers, and if we need help.</p><p>Even if we are having individual projects the stand-up has been an important part of the day, usually, you will find that more people have the same problem as I struggled with or they can offer help and support and vise versa. I have also adopted the method of doing a personal agile kanban board which is a physical or digital board where you set up categories in columns (backlog, todo, doing, testing, done, etc.). Then adding items that need to be done in cards which can be moved as they get processed. It keeps me on track and helps to create a visual overview of a busy week, offering the satisfaction of moving cards from to do, doing, and finally done 🎉.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*57ZIh4oOSOTnGi8CNKdyiQ.jpeg" /></figure><p>Another important ceremony is retro, doing a retro at the end of each week is to summarize the week, reflecting on what I’ve done, what could have been better, and what to improve for the next week. I’ve found it valuable to write down for myself these points and make sure to also reflect on what was done well and to bring that with me for the future.</p><p>The last thing I want to highlight is the demo, practicing to demo your project to others has been an important part of the learning process. To show the project, explaining your code to others and daring to show what you have done is something you have to get used to. Personally, it was terrifying in the beginning, to show your work to others but as I practice it became a natural part of the process, and if you have an as supportive, helpful, and smart team as I have the privilege to have, it becomes a great environment for improvement and constructive feedback and to inspire each other with ideas and solutions.</p><p>There is so much more to the agile methodology and to code review but I’ve really come to enjoy these ways of working and it has really made me grow as a developer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c28d5d6c72d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[<Redirect path=”/endless/pathways”/>]]></title>
            <link>https://medium.com/@lindblom.emelie/redirect-path-endless-pathways-713bde8df08?source=rss-f9d44bad11df------2</link>
            <guid isPermaLink="false">https://medium.com/p/713bde8df08</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[changing-careers]]></category>
            <dc:creator><![CDATA[Emelie Lindblom]]></dc:creator>
            <pubDate>Fri, 05 Nov 2021 18:38:07 GMT</pubDate>
            <atom:updated>2022-10-25T13:39:04.756Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*JdnVLQK9huEF6jsdqZ_qSg.jpeg" /></figure><p>If you have ever come across the topic of neural networks, be it through biological neural science or as me being curious and intrigued but the massive topic that is artificial intelligence and it’s many sub-branches.</p><p>There is this area in machine learning called artificial neural networks and it is inspired by the biological neural network. By training the machine with inputs and outputs the networks get weighted and calculated every time it trains so that the output get more and more accurate through training itself over and over. Ok ok you are not here for a lecture on neural networks and I wouldn’t even be the right person to dive any deeper into this subject so hang in there and my point will get more clear in a moment.</p><p>A while back when I was trying to figure out what direction I wanted to take regarding my career change, programming was the perfect combination of creativeness and problem solving that I believe I’m made for, but that feels like a topic well covered by most people that choose to become a developer. So I want to tell you about an important metaphor and concept that has helped me in my toughest moments of learning programming halfway through an intense and fast paced boot camp.</p><p>Something that really stuck to me was the “image” of neural pathways and how important that metaphor as been to my journey. Here’s another explanation but bare with me, neural pathways are like physical pathways, the habits and routines you have done for a long time becomes more and more familiar and you might even be able to walk that way blindfolded, the path has become thick and wide and so easy to walk. So entering the first weeks of the boot camp I felt like I was standing in front of a completely untouched forest with no clear pathways to be seen, I just had to start walking aka start coding, creating pathways with html and css and when those paths started to feel familiar we entered another part of the forest that is Javascript that finally lead into this exciting but unknown territory called React.</p><p>I’ve been frustrated and lost in these woods, I felt like I didn’t recognize the pathways I’ve created because they weren’t “walked” enough. But I kept telling myself that I just need to continue walking the paths over and over and not be scared to create new paths. That’s the amazing part about the brain, it can create new neural pathways because the brain is flexible and adaptable (also known as neuroplasticity). So in any moment of weakness or reflection over how much I’ve learned halfway through the boot camp I think of my brains new pathways, when small concepts suddenly fall into place, when I’m writing an arrow function without peaking at any notes. I also Imagining the weights in neural network training myself with inputs and outputs calculating fails and successes to become the skillful developer that I know I will be after I graduate this boot camp, excited to continue learning and create endless new pathways.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=713bde8df08" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>