<?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 Gabriela Preiss on Medium]]></title>
        <description><![CDATA[Stories by Gabriela Preiss on Medium]]></description>
        <link>https://medium.com/@gabriela.preiss?source=rss-2ef0b13bdfd7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*oSipiINTvlW4ZN6ys7PaXA.jpeg</url>
            <title>Stories by Gabriela Preiss on Medium</title>
            <link>https://medium.com/@gabriela.preiss?source=rss-2ef0b13bdfd7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:38:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gabriela.preiss/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[Navigating a New Industry Whilst Mentorless]]></title>
            <link>https://medium.com/swlh/navigating-a-new-industry-whilst-mentorless-b9d912bc27ff?source=rss-2ef0b13bdfd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9d912bc27ff</guid>
            <category><![CDATA[digital-nomads]]></category>
            <category><![CDATA[mentorship]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Gabriela Preiss]]></dc:creator>
            <pubDate>Mon, 11 Nov 2019 14:02:44 GMT</pubDate>
            <atom:updated>2019-11-13T13:11:38.128Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0WRbrVQvAPl9BGtzc1qjBg.jpeg" /></figure><p>Currently, I’m a digital nomad based in Barcelona, freelancing for an awesome American-based tech start-up. If you’ve had a minute to read my previous stories, you’d know I’m new to the tech/start-up world, navigating it mentorless. I made a 180° switch in my career and went from English HS teaching to web development two years ago. Honestly, scariest and best decision of my career. “Did you really hate teaching that much?” you may ask… and the answer is no, I loved teaching, but I craved easier mobility, faster progress, and less bureaucracy.</p><p>Over the last two years, I’ve had to build my career again, from the ground up, starting with no internships, no experience, no references, and no mentors, nothing but my education, studying at the global kick-a$$ bootcamp, <a href="https://medium.com/u/2fc79969c8eb">Le Wagon</a>. It’s been a test (note: “been”, meaning “it still is, and may always be”).</p><p>Over the course of these first two years, I’ve evolved, explored, and carved a small niche in this massive, competitive industry. The industry is growing, but that doesn’t mean it’s not drenched. The need for workers with coding skills is growing above and beyond… and rising, but that doesn’t mean you’re not competing against the best, and that can be intimidating for a newbie.</p><p>Essentially, I’ve evolved from web developer to web consultant, to coding curriculum developer, to QA testing and customer support + analysis, my current position. This has been a journey, to say the least. My career has made more evolutions in the last 2 years, than the previous 7. I’ve been seeking my niche, finding my groove, figuring out where I feel most driven and thriving, and where I can best combine my tech/coding world with my communication/teaching world.</p><p>Currently, I can say I’m thoroughly content with my current role, fusing my skills in customer service, problem-solving, code, and data while keeping it challenging. But it’s an uphill climb of uncertainty, the anticipation of the next change, the next learning curve, the constant “will I be ready for it?” feeling, the challenge of explaining to friends and family what I even do, the imposter syndrome, the sometimes lingering thoughts of “I can’t do this on my own, but I’m scared to ask for help”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YgtRG_MbAbdJ6Lgp-B5Vwg.jpeg" /></figure><h4>As I said, it can be a competitive industry. There is a lot of navigating through uncertainty and chaos, and a mentor goes a long way. A mentor is a beautiful heaven-bestowed person, assigned to you or who just takes you under their wing and basically shows you the ropes, teaches their tips and tricks, walks you through the nuances, breaks down their thought processes so you can get inside their head and understand a fresh approach to your work, and creates a safe environment for open communication, stupid questions, or the occasional rant, if need be.</h4><p>You see, I’m a bit burnt because as a teacher, I had the great fortune of having an amazing mentor, who changed my life and drive for teaching through compassion, nurture, curiosity, and her profound intellect and wisdom. We became best friends. Everyone needs one of those. And I didn’t realize how important a mentor was until I no longer had one.</p><p>If you scroll through LinkedIn, every other post talks about the impact and benefits of having a mentor, the statistics, the data, the emotional reliefs, etc, etc, blah blah blah… yeah, I’m bitter. I also agree with every one of those studies and opinions.</p><p>A lot of startups are nurturing, and promote curiosity, questions, open communication, including the one I’m currently with. But I’ve also had experience with not-so-nurturing startup environments, and it was very “every man for himself”. I’d ask for help, but help was brief and abbreviated. People are there only to help when asked, and honestly, I completely get it. They have their own roles, deadlines, responsibilities and don’t have the emotional space to mentor. I’m guilty of this too.</p><h4>So, my challenge is, how do I become my own mentor, in this new industry? And how do I step up as a mentor to others to continue this process?</h4><h3>Becoming My Own Mentor:</h3><ul><li><strong>Taking time for myself. </strong>This is one of the best takeaways previous mentors and leaders have taught me, to secure my work/life balance, and take care of myself before others. For me, this means exercising daily, getting outside, working from public places so I don’t go stir-crazy, eating right, getting enough sleep, making time for friends and family, and I’m sure you can think of 100 more.</li><li><strong>Educating myself. </strong>No one will take ownership of my professional development other than me. That means keeping on my toes, taking udemy classes, reading up on tech news, tech feeds, listening to up-to-date podcasts, whatever I can access. This doesn’t take up as much time as you may think, just reserving 30min here and there goes a long way, during my commutes, while drinking my coffee, or when I have extra downtime. One of my professors had told me he would interview for other jobs he knew he wasn’t going to accept just to keep himself sharp, and I’ve adopted this same practice too. I’ve interviewed for a few jobs I knew I wouldn’t take, and I’ve either bombed or been offered the next step that I later declined just to keep up with the interviewing process.</li><li><strong>Keeping myself a part of the team. </strong>This may be one of my biggest struggles. When working remotely, it’s easy to isolate myself. Even more so, because I work at an opposite time zone from most of my colleagues. A few days of isolation doesn’t bother me, but after a week or few weeks, things start to get verrrry lonely. Team rapport and daily catchups, whether professional or casual go a long way. It’s worth reaching out, sharing ideas, current reads, recipes, movies, and just being an active part of your remote team.</li><li><strong>Showing myself gratitude and reflecting on how far I’ve come. </strong>This may be the most important part of my personal self-mentoring because it can only come from me. I can have colleagues and mentors tell me “great job”, but if I don’t believe it, it won’t be worth anything. This is also what helps obliterate imposter syndrome and doubts over time. I quit a career, moved abroad, rebuilt a career, worked my way up, developed myself professionally, built a rapport, and am continuing to do so. I’m sure everyone reading this has a similar or greater list of feats. It’s important to take time and show some self-gratitude. <strong>If I find myself stuck or struggling with anything, I remind myself, it’s not because I’m new or a rookie, but because I’m still learning, I’m still being challenged, and that’s a good thing. You only stop learning when you’re dead.</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pwNQDNeZrlSLomm7n1hHZQ.jpeg" /></figure><h3>Becoming a Mentor to Others:</h3><ul><li><strong>Take time to share gratitude to them</strong>. We can all agree it pretty much rocks when someone tells us we’re doing well and our work is appreciated. Well, turns out others feel the same way when we tell them, so share it openly!</li><li><strong>Offer help. </strong>You don’t have to bend over backwards for another person’s work. Obviously, we all have our own workload, but let them know periodically you’re open to help and offering a hand, clarification, tutorial, rundowns, or feedback. This has always been much appreciated when offered to me, and I want to put this into greater practice.</li><li><strong>Give help, even when not offered. </strong>Have you ever heard offering to make someone soup when they’re sick is nice, but just showing up with the soup is much nicer? Sometimes, we offer ourselves, but people don’t take us up on it because they don’t want to burden us. If you have a helpful resource, tool, screenshot, tutorial, tip, trick, share it! If it makes your life easier, it will for others too!</li><li><strong>Share your thought process.</strong> This is the same tool I used when teaching in the classroom as well because <strong>the best way you can teach someone what you know is by vocally breaking down the thought process.</strong> If you’re helping with or instructing a new software tool that requires problem solving, for example, instead of just saying the question is A and the answer is B, share how you got to B. Maybe you noticed a detail that was peculiar, or a detail reminds you of a similar issue you’ve faced previously, or you remember there’s documentation on something related… Break down the process detail by detail. What is intuitive to you, the mentor, may be a black hole for the learner and require more clarification than you realize. Don’t take your knowledge for granted, and assume everyone is at the same level.</li></ul><p>Here ends my massive, self-therapeutic guide to self-mentorship, and by the way, this Medium story definitely counts as a step in my own self-mentorship and self-gratitude. Apparently, the journey never ends!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9d912bc27ff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/navigating-a-new-industry-whilst-mentorless-b9d912bc27ff">Navigating a New Industry Whilst Mentorless</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Spectre: a cool, lightweight CSS Framework]]></title>
            <link>https://medium.com/quick-code/spectre-a-cool-lightweight-css-framework-c54d06a5aa84?source=rss-2ef0b13bdfd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/c54d06a5aa84</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[css-framework]]></category>
            <category><![CDATA[spectre-css]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[respect]]></category>
            <dc:creator><![CDATA[Gabriela Preiss]]></dc:creator>
            <pubDate>Sat, 27 Jan 2018 12:44:23 GMT</pubDate>
            <atom:updated>2018-01-31T19:55:17.058Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/877/1*MWz9rGl_FP1RA7PEcSF_cA.png" /></figure><p>While Bootstrap is probably the most popular CSS framework, and easy to implement, it’s nice to branch out and experiment with different CSS libraries/frameworks every once in a while, just to know what else is out there.</p><p>There are many pros of Bootstrap, but the end results can be slower loading times and battery drains, and Bootstrap’s Javascript requires jQuery, a not-very-small dependency.</p><p>This is when I came across <a href="https://picturepan2.github.io/spectre/">Spectre</a>, a light-weight, easy-to-implement CSS framework (admittedly, I came across it more by force than choice, as I was working on a project for a company where Spectre was required… causing me to google what the heck it even was).</p><p>Some of the pros of Spectre:</p><ol><li>It’s pretty… check it out; you’ll see.</li><li>Easy to implement.</li><li>Lightweight: no JavaScript (100% smaller than Bootstrap), and uses less CSS (74% smaller than Bootstrap gzipped).</li><li>Easy to use responsive design with a modern approach, with Flexbox.</li></ol><p>How to Install:</p><p>You can either download the minified <a href="https://github.com/picturepan2/spectre/tree/master/dist">Spectre.css</a> file directly, install from CDN, use npm, yarn, or bower to install it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*vp7SprCrsDE1kpLZze73gg.png" /><figcaption><a href="https://picturepan2.github.io/spectre/getting-started.html#installation">https://picturepan2.github.io/spectre/getting-started.html#installation</a></figcaption></figure><p>Or you can add it the Rails way with a super handy <a href="https://github.com/zokioki/spectre_scss">gem</a> (a friend helped me come across this one):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/1*NRBxQPUZFHQHEipeiHVjsQ.png" /><figcaption>“There’s a gem for that.”</figcaption></figure><p>So what can it do? Spectre covers all of the basic CSS expectations from Bootstrap, such as buttons, forms, icons, etc. It also has it’s own responsive layout grid system, as well as a flexbox grid, and a navbar layout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/844/1*Rv1P6nk3B8I8vqwTNj0BDw.png" /></figure><p>It also has a really handy list of other cool, prettily(that’s a word, as far as I’m concerned) designed components, utilities and “experimentals” for you to use and implement just too easily, such as calendars, timelines, comparison sliders, all made of pure CSS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/870/1*1DfObmLibtT0gSroYu0tgA.png" /></figure><p>Check it out, try it out, and let me know your thoughts, any other cool features you’ve found with it, or if you have any CSS frameworks you like using, that are lighter and lesser known than Bootstrap!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fd083d1%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fd083d1%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/fc78cb15c51ca2cbc387138848d5e91f/href">https://medium.com/media/fc78cb15c51ca2cbc387138848d5e91f/href</a></iframe><p>Please click 👏 button below a few times to show your support! ⬇⬇</p><p>Thanks! Don’t forget to <strong>follow</strong> Quick Code below.</p><blockquote>Find out Free courses on <a href="http://www.quickcode.co/">Quick Code</a> for various programming languages. Get new updates on <a href="https://www.messenger.com/t/1493528657352302">Messenger</a>.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c54d06a5aa84" width="1" height="1" alt=""><hr><p><a href="https://medium.com/quick-code/spectre-a-cool-lightweight-css-framework-c54d06a5aa84">Spectre: a cool, lightweight CSS Framework</a> was originally published in <a href="https://medium.com/quick-code">Quick Code</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing, Implementing, and Shipping to Production a Rails App in 8 Days]]></title>
            <link>https://medium.com/le-wagon/designing-implementing-and-shipping-to-production-a-rails-app-in-8-days-2e0490d673da?source=rss-2ef0b13bdfd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e0490d673da</guid>
            <category><![CDATA[rails]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[coding]]></category>
            <dc:creator><![CDATA[Gabriela Preiss]]></dc:creator>
            <pubDate>Tue, 12 Dec 2017 15:53:14 GMT</pubDate>
            <atom:updated>2017-12-12T22:30:24.365Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dhtbZon7OPebZuUO9-yyjw.jpeg" /></figure><p>There are a lot of details that go into building and deploying an app. Now, condense that into 8 days, add a little blood, sweat and tears into the mix… and beer, a lot of beer, and you have something similar to the last two weeks of the <a href="https://medium.com/u/2fc79969c8eb">Le Wagon</a> Lisbon Batch #97.</p><p>This is the moment we’d been working toward. We’d already built and deployed a Rails prototype the week before, in 5 days, getting comfortable with our first collaboration, the technical workflow, and using Github as our VCS. Now, though, on our final project, there was no more time to get comfortable, the process needed to be perfect because we were demoing our apps live in (insert # of days left until demo) days.</p><p>The first thing we realized, as a group, made up of myself, two Portuguese developers, and a German developer, is we needed to approach this project with a solid foundation of what we <strong>wanted</strong> and <strong>expected</strong> from the function to aesthetics. So, that way we wouldn’t waste too much time with trial and error of “what looks good” or “works right” halfway through the development.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*odstHeuu4epA2Qe7bFVBXg.jpeg" /></figure><p>Implementing the following project management approaches made all the difference, especially when it meant saving hours of time later, or even just minutes, as the deadline neared:</p><ol><li>We spent more time <strong>pre-planning</strong> our models, using Sketch or often just paper and pencil, and being verbal about what got a thumbs up and what sucked (we were a tough crowd).</li><li>Programming with a MVC model, we spent time thinking and talking about what our <strong>database schema</strong> would look like, making sure the models were all in check, as well as their references, and checked it twice before moving on.</li><li><a href="http://trello.com/">Trello</a> was a life-saver in <strong>categorizing and prioritizing</strong> work. In the beginning, the work was divided between front-end and back-end, and even the smallest work details were added to our to-do list. As the development progressed and demo-day approached, it became a task-list of all the loose ends that needed to be tied, both back and front-end. We always made sure to move our tasks from “To Do” to “Completed” after being reviewed by each other.</li><li>We aimed for three <strong>standups</strong> a day, once in the morning before coding, after lunch, and again in the evening before taking off to do it again the next day. We’d review what were the priorities of the day, what had been completed, what we were currently working on, as well as having open communication to talk about what needs improvement or needs to be changed all together.</li><li>Having a <strong>positive mindset</strong> made the whole process… fun! Especially when we were down to the last two days, and the stress and anxiety were kicking in full force, we were still laughing with high energy. When code broke (and it often did, regardless of how many prayers you made, candles you lit, sacrifices you made), we’d either 1. shout expletives into the air (all in good humor), or 2. just laugh, because hey, you laugh to keep from crying right?</li><li>Finally, we were <strong>ambitious</strong> about the process. This was the most ambitious app we’d developed, considering the complexity of the features and the restrictive time restraints. A lot of our conversations started with, “I don’t know how to code that yet, but I’ll figure it out!” And we did. Sure, we were all coding independently, lost in our own mind maps, but in the end we always came back together to discuss the code, improve it, and scrutinize it.</li></ol><p>If you want to see for yourself what we created, check it out <a href="https://www.youtube.com/watch?v=LT9Ta7OpCr4&amp;feature=youtu.be">here</a>, a link to our Demo Day @ TimeOutStudio in Lisbon. My group and I are the second presenters, with our app, Medi-Co: developed to strengthen communication between doctors and patients, using instant messaging, secure transfer of documents and easy medication and appointment tracking.</p><p>Finally, if you’d be so kind, I’d like to hear what works for you and your collaboration teams, as well as any other kind of feedback/questions you have… and some claps would be nice too!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e0490d673da" width="1" height="1" alt=""><hr><p><a href="https://medium.com/le-wagon/designing-implementing-and-shipping-to-production-a-rails-app-in-8-days-2e0490d673da">Designing, Implementing, and Shipping to Production a Rails App in 8 Days</a> was originally published in <a href="https://medium.com/le-wagon">Le Wagon</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[21-day Coding Challenge]]></title>
            <link>https://medium.com/@gabriela.preiss/21-day-coding-challenge-ea553681541e?source=rss-2ef0b13bdfd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea553681541e</guid>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[goal-setting]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Gabriela Preiss]]></dc:creator>
            <pubDate>Wed, 06 Dec 2017 09:38:46 GMT</pubDate>
            <atom:updated>2017-12-06T09:42:59.457Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ONdNQ3p797leNHddmNGcrw.jpeg" /></figure><p>Disclaimer: I’m a bit of an enthusiast/sucker for all things related to boosting productivity and tapping into one’s highest mental potential, along with all those other sappy self-help stuff like experimenting with brain-food diets, meditation routines, etc. … I’m also looking into how not to be that obnoxious person who won’t stop talking about said new study or diet to boost creativity, productivity, health, or whatever it may be… so, let me know if you have any tips… I’m asking for a friend.</p><p>Now, onto the main point here, and that is as of December 1st, I am officially a <a href="https://medium.com/u/2fc79969c8eb">Le Wagon</a> coding bootcamp alumni! Well, maybe December 2nd at approximately 2ish am, when the Demo day after party ended. Demo day, being the public presentation of the app you and your teammates develop in two weeks, using Ruby on Rails.</p><p>Side note: if you’re not too familiar with the rise of coding bootcamps, or are currently shopping around for the right bootcamp for you, check out this <a href="https://www.switchup.org/research/best-coding-bootcamps">guide</a>, but also allow me to preface this short article with fair warning of the nature of coding bootcamps. They are incredibly challenging, ambitious, and fast-paced (or should be, if you choose well).</p><p>I can’t honestly speak for other courses, but this was the experience for me and 20-something others at the <a href="https://www.lewagon.com/apply/lisbon">Lisbon LeWagon</a> coding course this fall: 9 weeks, everyday, 10 hours a day… non-stop cycle of lectures, coding, coding some more, sleep, wake up at 4am thinking about code, then cursing your brain to just give it a break for 3 more hours until your alarm goes off, finally a bit more coding, and you do it all again.</p><p>I don’t know how unique my experience was, but I feel like I had a super privileged experience of being with a star-team of instructors and fellow-students. There was a constant air of ambition, drive, and of course, merciless exhaustion, yet you keep going, because everyone else does. That kind of motivation and positive peer pressure you don’t find everyday. So, the question is- <strong>how do you keep the momentum going?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KC3RTyxsbu5wGlRAGPNBvQ.jpeg" /><figcaption>Set a plan to keep the momentum going</figcaption></figure><p>Now the course is over, and I still have the adrenaline of the last few months. And I don’t want it to fizzle. So, here’s my plan…</p><p>From what I understand, it takes approximately 21 days to form a habit. Now I know that number has been debated and debunked in many ways, but for me personally, it still seems like a moderately okay starting point to creating a new routine.</p><p>When I was in class at LeWagon, it was easy to code long hours everyday, because I had my fellow students and instructors, but on my own, that may turn out to be a different story, even though I’m not deep into post-LeWagon life yet. So, to get comfortable with coding on my own, at the intense pace I had during the course, and finding a daily routine that works for me, to keep me sharp and proactive, I propose a <strong>21-day coding challenge</strong>.</p><p>That’s three weeks. For three weeks, code everyday. Take time in the morning, during a lunch hour, in the evening, whenever. Find a place you feel comfortable and productive, and mark off the days as they pass. I try to expose myself to as much code as possible or even just <a href="https://medium.com/@gabriela.preiss/the-learning-curve-of-an-aspiring-developer-4c684c974bbc">code talk</a>, via articles, podcasts, books, whatever, but nothing compares to writing code itself, creating it. So, I plan to spend the next three weeks coding a little or a lot everyday, until it feels like a natural part of my daily routine, like reading a novel, or going for a run.</p><p>I intend to see if not all, at least three personal pet projects done by the end of the three weeks. I have plenty to keep me busy, and a lot to work with. That’s 21days of December… then when the new year comes, I’ll be on to the REAL productivity resolutions… I’m looking at you, gym membership, that’s been sadly collecting dust by my front door during the last 9weeks of the bootcamp.</p><p>Finally, I’ll try to document how the 21-day coding challenge goes, and my experience with it. As for now, share any personal coding challenges you’ve set for yourself, or any personal challenges you’re working on for that matter. I’m also looking for claps, feedback, and anything else you have to share, if you’d be so kind.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea553681541e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The learning curve of an aspiring developer]]></title>
            <link>https://medium.com/@gabriela.preiss/the-learning-curve-of-an-aspiring-developer-4c684c974bbc?source=rss-2ef0b13bdfd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c684c974bbc</guid>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[codingbootcamp]]></category>
            <category><![CDATA[full-stack-developer]]></category>
            <category><![CDATA[full-stack]]></category>
            <category><![CDATA[junior-developer]]></category>
            <dc:creator><![CDATA[Gabriela Preiss]]></dc:creator>
            <pubDate>Fri, 10 Nov 2017 10:47:08 GMT</pubDate>
            <atom:updated>2017-11-10T15:40:29.768Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QH4RGlNwXUFnJSytytvb6A.jpeg" /></figure><p>Allow me to begin at the near-end of the beginning. I am seven- count them, highlight them, cherish them- SEVEN weeks into the <a href="https://www.lewagon.com/lisbon">LeWagon</a> Full-stack Web Development Bootcamp in Lisbon, Portugal (and may I just add, as proud as a freakin’ parent, that LeWagon was just named “Best Coding Bootcamp Worldwide” by <a href="https://www.switchup.org/bootcamps/le-wagon">SwitchUp</a>, and I fully back that title). I’ve been planning, preparing, and studying over the last year to pave the way for this new experience, and still, nothing could have truly helped me to anticipate the deep dive into new, bright, foreign territory of vast experiences I’ve gained from being here.</p><p>Unlike many of my fellow students(… wagon-mates… wagoners?), I don’t have a background in the tech, science, or math industry. My background is in liberal arts and education. I have been teaching High School English in the United States for the past four years. Obviously, now I’m not doing that anymore, and the reasons being, I can save for another story, but I was always interested in the other half of my brain- the side that cultivates algorithms, computer logic, formulaic design. Still, software development is very new, unchartered territory for me.</p><p>So, venturing into this new industry, field, realm, world, UNIVERSE (how much more alien can I make myself sound, because that’s how I feel), I recognize there are sharp knowledge gaps in cases as simple as vocabulary, vernacular phrases, big names in the tech world, new innovations… just tech lingo in general, compared to that of my classmates and instructors. It has definitely been a learning curve for me bridging that gap, because there is an undeniable language and culture to software development that I’m learning. Paul Ford touches on it hilariously and sarcastically, but also honestly in <a href="https://www.bloomberg.com/graphics/2015-paul-ford-what-is-code/">“What is Code?”</a>. Now if you’re good at something, and you enjoy something, then who cares about the culture and status quo of it, right? I’m already being told “you don’t look like a software developer;” whatever the hell that means. BUT I do recognize getting into development means entering into a non-stop cycle of constant learning, updating, and revamping what you know, how you practice, how you code, how you collaborate- it’s one of the few industries that is affirmably guaranteed to increase in supply and demand, but no one can predict how or in what form, because it’s always changing. As a junior developer, that’s exciting and frightening, and I want to narrow this learning curve by keeping up with the language and culture.</p><p>Immersing yourself in the tech world, is in itself a full-time job(a fun one), and I’ve learned to be selective but also inclusive about it. First of all, you gotta be passionate about it, and if you’re not, become passionate about it. Software developers are probably the most efficient people at collaborating, sharing knowledge, taking risks, helping each other, building communities (online and in the real-world), and it’s very easy to gain insight into that. I have a few tips I’ve been using to step into that community.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1XekYEWIALsRlbCssl_BiQ.jpeg" /><figcaption>There are many opportunities to be a part of coding culture on and offline</figcaption></figure><ol><li>Use and contribute to <a href="https://pt.stackoverflow.com/">Stack Overflow</a> and <a href="https://github.com/MunGell/awesome-for-beginners">open source projects</a>; if you’re gonna take info, try giving back too.</li><li>Read programming and coding <a href="https://peterdaugaardrasmussen.com/2017/01/18/great-programming-books-that-i-still-recommend-in-2017/">books</a>; to my pleasant surprise (English teacher here), coders are readers, and fast readers too (well, more like skimmers, but still…).</li><li><a href="https://medium.com/topic/technology">Medium</a> has changed my life in keeping up with the things that interest me- sweet, short, aesthetically pretty articles/stories/essays about anything that interests me, from guides to opinions? Come on now; it’s too easy.</li><li>Hate reading? I get it (well, really I don’t, but I understand time is not always on our side). Try <a href="https://stackoverflow.blog/2017/08/09/5-great-podcasts-developers/">podcasts</a>! Same idea as articles and books, different medium.</li><li>Attend <a href="https://www.meetup.com/">Meetups</a> and conferences where you get to talk to other developers, pick their brains, spit out your ideas. There are so many scenes for developers and digital nomads; I’ve had the opportunity to check out cool meetups, workshops, and <a href="https://websummit.com/">conferences</a> while here in Lisbon, and it makes a difference. Like the saying goes “If you’re the smartest person in the room, you’re in the wrong room.” So, get yourself into the right one.</li><li>Join online communities. There’s a developer scene on almost any platform- Twitter, Reddit, Slack… this is probably the easiest, least time-consuming way of immersing yourself in the developer culture. Just browse it, take a few minutes a day to see what the big topics are. It goes a long way.</li></ol><p>This is definitely not an exhaustive list, or a mandatory one, but it has been a help for me. My time at LeWagon is winding down, and more than once, over beer with my classmates in the evening, we get all somber and sentimental about how we don’t want it to end, because it’s been such an awesome, bonding experience. Community does make a difference in how you process an experience, especially a new, grueling experience as a full stack developer. It can be intimidating and exhausting, but so very cool and rewarding. And of course, never forget, take moments to unplug. Immerse yourself, but also put yourself in different environments too, away from a computer, away from code, and let your brain… dare I say… reboot? I know; my own eyes just rolled at that too.</p><p>Share your own tips, tricks, and Gandalf-wise advice on your journey as a developer! I’m also looking for claps, feedback, and anything else you have to share… because I’m needy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c684c974bbc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>