<?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 João Gonçalves on Medium]]></title>
        <description><![CDATA[Stories by João Gonçalves on Medium]]></description>
        <link>https://medium.com/@jpmgoncalves?source=rss-20720d2c5fc5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*iTRAx06T-rLDnVqq2qjmfg.jpeg</url>
            <title>Stories by João Gonçalves on Medium</title>
            <link>https://medium.com/@jpmgoncalves?source=rss-20720d2c5fc5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 16:57:22 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jpmgoncalves/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[We Have Some Recruitment News]]></title>
            <link>https://medium.com/redlight-software/we-have-some-recruitment-news-cdc944f3bf35?source=rss-20720d2c5fc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/cdc944f3bf35</guid>
            <category><![CDATA[recruitment]]></category>
            <dc:creator><![CDATA[João Gonçalves]]></dc:creator>
            <pubDate>Fri, 05 Mar 2021 15:51:33 GMT</pubDate>
            <atom:updated>2021-03-24T10:57:02.136Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pyj3cnJJTatH5_d3LU0Zzw.jpeg" /></figure><p>Hi there! We have some exciting news to share today. RedLight has now <strong>three</strong> open job positions. Read more about them on the links below.</p><ol><li><a href="https://blog.weareredlight.com/recruitment-news-job-offer-for-front-end-developers-d037b836e959">Front-End Development</a>.</li><li><a href="https://blog.weareredlight.com/recruitment-news-job-offer-for-back-end-developers-72eb81233a5e">Ruby On Rails Developer</a>.</li><li><a href="https://blog.weareredlight.com/recruitment-news-job-offer-for-designers-ccec1503f8b2">Designer.</a></li></ol><p>Update: Applications are open until <strong>they’re fulfilled (you’ll see a “[CLOSED]” on top title of post once that happens)</strong>. Shortly after receiving new submissions, we’ll get in touch with everyone who applied to RedLight.</p><p>If you’re interested in any of these job openings, feel free to apply or to share them with your friends.</p><p>For those who are applying, good luck. 👋</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cdc944f3bf35" width="1" height="1" alt=""><hr><p><a href="https://medium.com/redlight-software/we-have-some-recruitment-news-cdc944f3bf35">We Have Some Recruitment News</a> was originally published in <a href="https://medium.com/redlight-software">RedLight Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recruitment News: Job Offer for Back-End Developers.]]></title>
            <link>https://medium.com/redlight-software/recruitment-news-job-offer-for-back-end-developers-72eb81233a5e?source=rss-20720d2c5fc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/72eb81233a5e</guid>
            <category><![CDATA[back-end-development]]></category>
            <category><![CDATA[recruitment]]></category>
            <dc:creator><![CDATA[João Gonçalves]]></dc:creator>
            <pubDate>Fri, 05 Mar 2021 15:43:56 GMT</pubDate>
            <atom:updated>2021-04-08T16:00:12.930Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DOPrGYphst8NLusSmoyIpQ.jpeg" /></figure><p><strong>RedLight is now looking for a Ruby on Rails developer.</strong></p><p>We’re looking for Ruby backend or fullstack developers to help us lay a solid foundation for both internal and client projects. You must have great Rails and Ruby knowledge, and experience using common gems like devise, rspec, or pundit. We value people who can architect and implement solutions without overcomplicating things (but who can also recognize when a more complex solution is warranted) and who like well-tested, readable code.</p><p>You’ll also need to feel comfortable integrating ongoing projects, recognizing file structures, organization patterns and other project specific requirements/characteristics both on up-to-date and legacy Rails codebases.</p><p>Other common pieces of our work stack are Git, Github, Gitlab, Postgres, Redis, Linux, and Docker, so good working knowledge of any of these is definitely a plus. We’re also eager learners, so if there are other technologies that interest you, or which you’ve had good results with please let us know!</p><p><strong>What You’ll Do:</strong></p><ul><li><em>Bootstrap new Rails apps, either in a team setting or by yourself;</em></li><li><em>Implement features, bug fixes, and tests in existing Rails projects;</em></li><li><em>Monitor and analyze production logs and monitoring metrics, and implement improvements to the infrastructure or application based on hard data;</em></li><li><em>Integrate with other systems (external APIs);</em></li></ul><p><strong>Requirements:</strong></p><ul><li><em>Extensive Ruby on Rails experience;</em></li><li><em>Knowledge of testing frameworks — minitest or rspec (or both!);</em></li><li><em>PostgreSQL experience;</em></li><li><em>Familiarity with code lifecycle management: Gitflow, branches, pull requests, code reviews, etc;</em></li><li><em>Familiarity with kanban-like project management tools: Trello, JIRA, etc;</em></li></ul><p><strong>Nice to have:</strong></p><ul><li><em>2+ years of professional experience;</em></li><li><em>Javascript experience (both Nodejs or frontend frameworks like React or Vue are valued);</em></li><li><em>Ability to leverage Git in complex scenarios;</em></li><li><em>Sysadmin / Devops experience (ranging from linux server knowledge, to running Docker and Kubernetes clusters);</em></li><li><em>Experience in other programming languages or technologies.</em></li></ul><p><strong>What’s Like Working At RedLight</strong></p><p>Working at RedLight never really feels like a job. We work hard but as we “play hard”, so we are all pretty close.</p><p>Our people are our biggest asset and the future of RedLight. They’re the real brainpower behind our every achievement, and we make a real effort to make them feel valued and an integral part of the whole.</p><p>Every opinion matters and all opinions are heard, and each one of us has a voice and a real chance of deciding how everything is done at RedLight. RedLight is not just about work and software, but also about lifestyle, being part of a community and feeling fulfilled.</p><p><strong>Some benefits you’ll get:</strong></p><ul><li>Health Insurance;</li><li>Free fresh amenities;</li><li>Free Spotify Premium;</li><li>Yearly team tour.</li></ul><p><strong>Application deadline</strong></p><ul><li><em>Update: no deadline, job opening is available until fulfilled.</em></li></ul><p><strong>How can I apply?</strong></p><p><a href="https://apply.workable.com/redlight/j/ABFD57C234/">Apply here by submitting this form</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72eb81233a5e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/redlight-software/recruitment-news-job-offer-for-back-end-developers-72eb81233a5e">Recruitment News: Job Offer for Back-End Developers.</a> was originally published in <a href="https://medium.com/redlight-software">RedLight Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Recruitment News: Job Offer for Front-End Developers.]]></title>
            <link>https://medium.com/redlight-software/recruitment-news-job-offer-for-front-end-developers-d037b836e959?source=rss-20720d2c5fc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/d037b836e959</guid>
            <category><![CDATA[recruitment]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[João Gonçalves]]></dc:creator>
            <pubDate>Fri, 05 Mar 2021 15:29:09 GMT</pubDate>
            <atom:updated>2021-04-08T15:59:56.021Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="RedLight is now looking for a Front-end Developer." src="https://cdn-images-1.medium.com/max/1024/1*OdYD-TxqUJTo8NNdR2Y1-w.jpeg" /></figure><h3><strong>RedLight is now looking for a Front-end Developer.</strong></h3><p>We’re looking for someone interested in solving software challenges with an approach based on frontend patterns and conventions. You must be able to describe, architect and implement such solutions, detailing all the important steps in order to ease the understanding for the rest of the team.</p><p>You need to feel comfortable integrating ongoing projects, recognizing file structures, organization patterns and other project specific requirements/characteristics. We’re looking for someone with the following profile:</p><ul><li><em>A person who likes programming and problem solving;</em></li><li><em>Has great eye for detail and feels comfortable debating aesthetics and UI/UX;</em></li><li><em>Programming experience and distributed systems knowledge;</em></li><li><em>Basic understanding of web, API, algorithms and debugging.</em></li></ul><p><strong>What You’ll Do:</strong></p><ul><li><em>Implement features in Javascript projects;</em></li><li><em>Explore browser and native APIs;</em></li><li><em>Integrate other information systems (external APIs);</em></li><li><em>Quality control tests covering the implemented features.</em></li></ul><p><strong>Requirements:</strong></p><ul><li><em>Javascript experience;</em></li><li><em>React JS or Vue JS experience — </em><strong><em>important</em></strong><em>;</em></li><li><em>Experience with testing frameworks — plus;</em></li><li><em>Experience in React Native — plus;</em></li><li><em>Ability to do design tweaks if necessary — plus;</em></li><li><em>Experience using GIT and Gitflow: branch management, pull requests, code reviews and others.</em></li></ul><p><strong>Nice to have:</strong></p><ul><li><em>3+ years of experience;</em></li><li><em>Experience in other programming languages that you’ve used in personal/professional projects.</em></li></ul><p><strong>What’s Like Working At RedLight</strong></p><p>Working at RedLight never really feels like a job. We work hard but as we “play hard”, so we are all pretty close.</p><p>Our people are our biggest asset and the future of RedLight. They’re the real brainpower behind our every achievement, and we make a real effort to make them feel valued and an integral part of the whole.</p><p>Every opinion matters and all opinions are heard, and each one of us has a voice and a real chance of deciding how everything is done at RedLight. RedLight is not just about work and software, but also about lifestyle, being part of a community and feeling fulfilled.</p><p><strong>Some benefits you’ll get:</strong></p><ul><li>Health Insurance;</li><li>Free fresh amenities;</li><li>Free Spotify Premium;</li><li>Yearly team tour.</li></ul><p><strong>Application deadline</strong></p><ul><li><em>Update: no deadline, job opening is available until fulfilled.</em></li></ul><p><strong>How can I apply?</strong></p><p><a href="https://apply.workable.com/redlight/j/5389D1E6CE/">Apply here by submitting this form</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d037b836e959" width="1" height="1" alt=""><hr><p><a href="https://medium.com/redlight-software/recruitment-news-job-offer-for-front-end-developers-d037b836e959">Recruitment News: Job Offer for Front-End Developers.</a> was originally published in <a href="https://medium.com/redlight-software">RedLight Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Remote Collaboration At RedLight]]></title>
            <link>https://medium.com/redlight-software/remote-collaboration-at-redlight-50d86c75ec63?source=rss-20720d2c5fc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/50d86c75ec63</guid>
            <category><![CDATA[working-from-home]]></category>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[remote-collaboration]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[João Gonçalves]]></dc:creator>
            <pubDate>Wed, 16 Dec 2020 12:51:51 GMT</pubDate>
            <atom:updated>2020-12-16T13:00:57.634Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lldSMdN0WT733d8E5qAaFw.jpeg" /><figcaption><em>Photo by </em><a href="https://unsplash.com/@yasmina?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><em>Yasmina H</em></a><em> on </em><a href="https://unsplash.com/s/photos/remote-work?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText"><em>Unsplash</em></a></figcaption></figure><p>By the beginning of Summer, I’ve been asked several times:<em> “and how is your company holding up with the new mandatory restrictions of working at home? Is it hard?”</em></p><p>Every single time someone posed this question, I smiled at the temptation of giving that simple and quick answer:</p><p><em>“Pretty good. We were a remote-friendly company way before covid-19 showed up.”</em></p><p>But the long answer is…</p><p><em>It’s complex.</em></p><p>A recent study from <a href="https://www.steelcase.com/research/articles/topics/post-covid-workplace/competing-post-covid-era/#reality-2">Steelcase concluded</a> that “individual task is up, collaboration and creativity are down, short meetings are skyrocketing and longer meetings are decreasing”. At RedLight, we do feel exactly the same. We know by looking at our own metrics that colleagues who have their tasks set up pretty straightforward and can complete them independently, which is the case with most of our engineers and designers when projects start the development phase, are showing better productivity indexes since they started working from home.</p><p>On the other hand, people like me, project managers, product managers, Heads of HR and others, who have to keep a constant stream of communication, collaboration and inputs from teams to upper management, the lack of direct communication is not making my job easier.</p><p>Prior to the lockdown, most of the time, getting a message heard was as easy as stepping into a room and asking for everyone’s attention. Now it’s much harder, as we’re facing asynchronous communication and not everyone is online at the same time. People have their own schedules because of children, doctors appointments, taking their dogs out, whatever. This is not new for us but the scale is. Now you can’t invite everyone into a drawing board spontaneously. Instead, you have to schedule things first, which is clearly a barrier to the pace of collaboration we’re used to.</p><p>Thankfully, at RedLight, we already had systems in place to accommodate for semi-asynchronous, remote collaboration so we were used to some of the problems that many companies are facing for the first time. We just had to tweak our own processes so we can be 100% remote.</p><p>This came with challenges of course. And yes, we already had Google Meet and Zoom in our daily lives but making this our gold standard for collaborating remotely has its downsides which is the loss of non-verbal/non-written communication. If you’re attending in-person meetings, one can assess nonverbal cues like body language, gestures, facial expressions of a colleague — like getting if he or she is understanding the topic, getting the signal that they want to add something, or that they’re ready to fight with a new point of view. Most people talk with their own bodies even before saying something and this is very important because if you’re driving a meeting, you can fabricate a safe way for people to share what they have to say.</p><p>But by doing video calls, it’s not the same thing. In-person meetings allow me to look into everyone’s faces and see if they’re getting it or need further explanation. With video calls, I can’t even be sure if my colleagues are actively listening to me, which is frustrating to say the least.</p><p>Another issue with video calls — not just video calls but most collaborative tools of synchronous collaboration, is that they set an environment where extroverts can easily control the flow of communication at the expense of introverts. And if you are working in tech, you know this is a problem. A significant share of people I work with are introverts and they’re likely to pass on active communication unless they’re asked something directly. If this happened in an in-person meeting, I could easily sense their nervousness and create a safe space for them to share their thoughts.</p><p>These are, just to name a few, soft-skills problems that can damage our collaboration as a team, and ultimately, our results as a company. While video conferencing is providing a way to communicate, it’s still ineffective to support the flow of creativity that is felt in a physical space.</p><p>Which makes me wonder, how effective are the remote work tools that we’re using as a community of tech companies at recreating collaboration processes like the ones we had before?</p><p>So far we haven’t seen any tool that resembles an in-person interaction. This may seem obvious but remote workers don’t have access to situational chitchat, conversations at the café or kitchen or even being able to stand up and go discuss a problem at someone’s desk. Without a way to recreate this spontaneous social interaction, collaboration is very likely to be affected. And note that many companies, like RedLight, already supported remote-friendly workflows. But making it fully-remote is a whole new different thing. The organic sharing of knowledge that happens in a physical space is highly difficult to recreate and is lost very easily. The social fabric of a physical office is very fragile.</p><p>Furthermore, while working remotely, our social differences are exacerbated. These can be physical, cultural or even expressed in timezones. And that’s why you need to build a system of trust. To trust when your colleagues are not responsive on Slack. To trust when the tasks they have take longer than expected. To trust that they’re doing their job responsibly no matter where they’re working from.</p><p><em>Trust, by the way, is bidirectional — not only for you to trust your colleagues but for them to also trust you. And that’s why if you find problems by working at home, like being overly distracted, procrastinating over your tasks or just being unmotivated, you should talk to your manager or RH for the company to set out solutions for you.</em></p><p>Even with the main takeaway from Steelcase’s study, I don’t think we’re seeing the whole picture on long-term productivity. When working from home, the start and end times are getting eroded as the usual schedule you had before is now impossible to respect because of all your responsibilities at home, be it petting the cat, play with the kids, making lunch, <em>etc</em>. And this erosion of start and finish times are showing that people are working more than they have, which will lead to the offset of the work/life balance necessary to maintain mental health. One can easily foresee where this is going: working long hours for a long period of time will lead to burnout and no one wants that for their teams.</p><p>While workers were unconsciously protecting themselves from putting up long hours by practicing the log-on/log-off routines of commutes, now our workspace is almost overlapping our living space. Without an explicit separation between work and home, one needs to be able to set a system that reminds team members to stop working at reasonable hours. And this is something we have to look for in the future.</p><p>That said, it’s very important that team managers encourage the flexibility that people need while working from home, while still looking for work-life balance that suits everyone and works best in the long-run.</p><p>In Portugal’s current lockdown rules, there’s still no plans to allow “<em>working from home”</em> companies to go back to the office, making many companies embracing a full remote scenario, cutting on rental leases. At RedLight, we still want to provide an office solution for our team when all of this is over (will it ever?) so we’ll probably become even more of a mix between office purveyor and working from home company. All we can do right now is to provide the best conditions wherever our workers feel better and try to recreate an environment where collaboration and spontaneity are key characteristics of a platform where everyone can openly talk and feel included.</p><p>So what is different now at RedLight?</p><p>To address this, we moved all our morning status standups into a single one. It’s less time-efficient when it comes to merging all standups but at least everyone can listen to what’s going on across all of RedLight’s projects. It also works as our new smaller version of “chitchat by the coffee machine”.</p><p>We also rescheduled our All-Hands from once every two months to one in every three weeks. We’re also recording most of our meetings so if anyone is not able to show up, they’ll at least have a way to see what happened. Or products hands-on meetings were rescheduled from monthly to fortnightly. So yes, we’re spending a lot more time in meetings for sure, just to be certain that we all converge to the same page on what the next steps are and that the whole team is active. And yes, we’re pretty much aware of the trade-off between productivity and the amount of time spent in “unnecessary” calls. But these meetings are very necessary as they have become the most basic form of social interaction we can provide.</p><p>We started to take documentation more seriously. Not only do ALL meetings have a Google Doc to match it with notes on what was said and what the main decisions are but also all of our tasks now have a description where we state the context on WHY the task was created, what’s the GOAL with it and how’s the APPROACH to solve/implement. That way the engineering team has more information on the tasks even if the developers weren’t present at the meeting where tasks were outlined. By our experience, this action alone keeps team members informed, aligned with product vision and unblocked.</p><p>At RedLight, we want to keep the lively spirit from the office ever present within us and we need to fight loneliness and boredom at all costs. Instead of reducing team activities, we want to foster more and better connections with more agoges, more demos, more group calls. We need to create chances for team members to get to know each other. And instead of trying to replicate what we had before, we need to think how we can create a sense of belonging as a whole. It’s worth setting up a task force to outline how company culture is set to be kept alive mostly because we’re ought to be living in this scenario for a while.</p><p>To conclude, the question to <em>how are you holding up with the working from home restrictions</em> is more than complex. It’s a way to set your company apart from others when it comes to establishing proper collaboration while still respecting (and enforce in some cases) the work-life balance.</p><p>It’s something that as a team manager, I look forward to as this is one of the biggest challenges that our workforce generation will ever face.</p><p><em>Stay safe.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50d86c75ec63" width="1" height="1" alt=""><hr><p><a href="https://medium.com/redlight-software/remote-collaboration-at-redlight-50d86c75ec63">Remote Collaboration At RedLight</a> was originally published in <a href="https://medium.com/redlight-software">RedLight Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RedLight & Testing]]></title>
            <link>https://medium.com/redlight-software/redlight-testing-238116c14306?source=rss-20720d2c5fc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/238116c14306</guid>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[qa]]></category>
            <dc:creator><![CDATA[João Gonçalves]]></dc:creator>
            <pubDate>Tue, 16 Jun 2020 14:44:34 GMT</pubDate>
            <atom:updated>2020-06-16T14:44:34.444Z</atom:updated>
            <content:encoded><![CDATA[<h4>Our thought process to create Quality Assurance processes.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zPaH0mdVs6TJH-D4wtyx4g.jpeg" /></figure><p>Hello everyone. Now that we’re all quarantined at home living the forced dream of remote work, I think it’s a good time to share with you some thoughts about our internal development process at RedLight with a special focus on Testing &amp; QA.</p><p>TL;DR — I’ll be covering some of the key points around which we’ve built our own internal quality processes. Namely:</p><ol><li>Setting clear roles for everyone who takes part in a project;</li><li>Keeping the process simple;</li><li>Create a process prone to error mitigation (not just output for the sake of it);</li><li>Ownership;</li><li>Document &amp; Prioritize;</li><li>Project-wide transparency and accountability.</li></ol><p>Along the years I’ve dealt closely with testing and development teams, I got the chance to understand why testing is, in general, a very understated and underrated part of software development. Many people will tell you that automated testing is enough and others will praise that testing in production is also fine. Personally, I think that none is enough nor fine and you should take Quality Assurance seriously if you want to create products that work seamlessly. Note that while bugs are generally accepted in your social network or video game, they aren’t as easily accepted when they happen while launching a satellite into space or while monitoring vital data (like some projects we’ve worked on) because if things go wrong in space or healthcare products, your bugs are likely to have <em>real</em> <em>costly</em> consequences. That said, let’s dive into software development and quality assurance.</p><h4>The current state of software development for the web or mobile is like a jenga game.</h4><p>Most modern systems depend on other people’s systems. Once you start developing an app, to ease and speed up the process, you eventually use somebody else’s library. That library you just imported to your project uses a few other libraries that were created by someone else, whose libraries depend on code from other developers. You see where I’m going right?</p><p>The system you’re creating is at the top of your personal architectural pyramid and most times you don’t really know what’s really beneath the first layers. This means that if you think your app might be working correctly today, due to lack of maintenance from any other third party pieces it may stop working at all and this can happen without a warning.</p><p>These pieces of software aren’t always properly maintained and many owners/contributors won’t even bother to let you know that they have stopped putting effort into it, resulting in bugs over time and sometimes severe security problems. So it’s fair to say that once you deploy something into production, the system you created has started its path to partial degradation and to be filled with errors in the future - getting technologically rotten. What is working today, might not be working tomorrow.</p><p>To mitigate all the errors you can inherit, you can either let them happen and solve them — which is not what your client would be happy with, or you can try to test and perform quality assurance on your system, testing soon and properly.</p><p>And yet, testing is a process that’s made to fail, in the sense that it’s always only going to cover your known unknowns — all of the things you know that might not be working and the things that you have the tools to test. Everything else is the unknown.</p><p>At RedLight, testing has many phases: Unit Testing (automated), Integration Testing (automated), Functional Testing, System Testing, Stress Testing (automated), Performance Testing (automated), Acceptance Testing, Regression Testing, Security Testing (automated) and Beta Testing.</p><p>The way we do our software development is to leave Unit, Integration, Stress, Performance and Security Testing to our development team. Functional Tests, Acceptance Tests (also performed by the client himself but <em>that’s a whole new blogpost</em>) and Regression Tests are responsibility for the QA team.</p><p>Of course, any team should create a Quality Assurance role that is appropriate for their process and the responsibilities will vary from company to company.</p><p>Independently of how many responsibilities you place on your QA team, it’s important to know that software engineering is a team activity and not only led by the dev team as many think. Projects are maintained by several people that contribute differently to the ultimate result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LX5N_h80hfV2dPZHLCDO6g.jpeg" /></figure><p>That said, here are the big takeaways from what I’ve learned by being the lead QA on RedLight and how you can implement these in your company.</p><h3>1. Set clear boundaries for each role.</h3><p>Each company has their own process but it’s extremely important for everyone to understand where their responsibilities end and the next person’s start.</p><p>In our internal process, the big boundary is the code review: An engineer submits his changes for peer review and once all reviews are positive and/or acted upon, the changes are merged and deployed. And it’s only after this that the QA team comes in.</p><p>Even before the QA team gets the prime time to try to break the system, it’s still important to know if the engineer has cleared all his responsibilities like unit and integration testing. At RedLight we always make sure that for each merge request, we have automated tests. We do this to make sure that this new merge request does not break any previous tests and that the current merge request has high test coverage.</p><p>Despite the way your team specifically works, it’s always important to set clear expectations and responsibilities for each team member and phase of the process. Don’t let anything happen in a gray area.</p><h3>2. Keep the process simple and easy to understand.</h3><p>This is probably the broader advice I can give for a company’s process.</p><p>No one wants to have a 100 page process on how to do their job but it’s still important to be clear for everyone on the team, from project kick-off to delivery. And however you set your process, remember: faster isn’t always better.</p><p>For example, at RedLight, code reviews are performed by at least 2 engineers that have not been part of the development of the task related to the committed change. This methodology has impact on velocity but it’s much cheaper (and safe) to examine someone’s code before it gets merged. If the merge request shows something wrong like inconsistent implementation, mismatch of project requirements or buggy code, it gets sent back to the developer to rewrite it. If the merge request looks OK and has the two unanimous checks for approval, it moves on to be merged and tested. This method instills good practices of teamwork and is a virtual platform for knowledge sharing (both for the product you’re creating and engineering do’s and don’ts).</p><p>After that, the QA engineer comes into play and knows exactly what to test and what to do if there’s something wrong with the new changes. If the QA engineer finds bugs related to the task being tested, he sends the task back with a “QA failed” report for the engineer to act on. That task starts its process once again and it’ll need to go through the two unanimous successful code reviews before it gets merged to be tested again. If everything’s OK with the task, keep on moving.</p><h3>3. When things can go wrong, they’ll eventually go wrong.</h3><p>Many times during the development process, be it engineering or QA’ing, there will be pressure to do things fast. “Move fast and break things” is a motto that doesn’t apply to most companies but many still follow this approach.</p><p>Our experience tells us that if there’s something that suffers with the pressure to launch a newer version is the way things are tested. Usually, when there’s a lot of hurry to meet a deadline there’s no automated tests to be found in merge requests, QA only goes through the most basic cases and all the green lights light up for launch.</p><p>But when things are done this way, all the preconditions for a disaster are in motion.</p><p>So, one thing is the ever present tight deadlines but the other is not being careful with the tasks you’re dealing with. Cutting corners now will make you invest a lot more time and psychological effort into patching a solution directly to Production.</p><p>No one likes to be woken up at 4am because PagerDuty is notifying you that there is a critical bug in Production. So it’s better to invest some time on proper testing, code review and quality assurance to ensure a proper night’s sleep and potentially saving lots of money in business value and development effort.</p><p>The whole reason for pushing Testing + QA to your process is that it helps you or the client to keep the product stable. The less you do it, the more unstable a product is likely to be. It doesn’t help much if you let scope creep get the best of your process while competing with your timeline.</p><h3>4. “It worked fine in my computer. 🤷‍♂️”</h3><p>Everyone has heard this at least once in his lifetime. This is the most common case where accountability fails and someone in your team doesn’t want to be seen as the faulty member, placing the responsibilities on anything (or everything) else.</p><p>There’s nothing wrong with having some commits that introduce defects that get pushed through, but there’s a big difference between owning it or not.</p><p>Note that every time a developer is creating something, he’s doing that in a controlled environment where the outcomes are usually predictive or deterministic. Most of the problems that the development team doesn’t find will always appear in non-controlled environments with components that interact differently with the system.</p><p>Once a deploy is made, the QA engineer is not just testing the diff or the code change — he’s testing a system made up of users, infrastructure, third party libs — moving parts. Many of these pieces have unpredictable interactions that you wouldn’t think of while developing your task. And if your Staging environments may act oddly, imagine when your code meets Production where users act unexpectedly.</p><h3>5. A Wild Bug Appears. What Now?</h3><p>The QA team and all of the testing exists for the sole purpose of keeping a minimum amount of bugs reaching production.</p><p>But it’s not sane for any team member to think that you’ll have a bug-free Production. Yes, it’s very easy to think that you should’ve delayed the launch of a product to solve all errors or that the next version should be on hold until we solve all defects but that’s not how the world works. If there’s any universal truth about software is this: it has bugs.</p><p>So, at some point, instead of letting a feeling of collective failure sink in, you should stick to the process: document the defect, evaluate the criticality of it, prioritize and keep moving forward.</p><p>As someone who’s in the industry for a while, I’ve known people sharing disastrous step-by-step scenarios of project mismanagement and this — the amounting bugs — is something that has a much bigger impact than it should.</p><p>First, obsessing over specific errors is not healthy at all. You can see developers, project managers and clients falling for this, moving allocations, roadmaps and effort towards something that might not be on top the priority list.</p><p>Secondly, as a software development company, you need to know how to manage the perceived quality of a product. For example, we know that our clients have bigger tolerances to errors that they don’t see when they’re interacting with a product. On the other hand, clients have a much lower tolerance on errors that impact the products visually or user data. So you might want to educate your client on his <em>Perception Of Quality</em> so he can prioritize things correctly.</p><p>As an engineer, you’ll always feel the hidden hand that pressures for specific things to be solved ahead of schedule but in order to maintain sanity, it’s important for the client and the PM to be on the same page that errors and failures help us getting better at what we do and shouldn’t get in the way of following the major plan.</p><p>Wrapping up:</p><ol><li>You will never be 100% sure that you’ve sorted out all of the bugs. Yet, you can be 100% sure that somewhere in the software there’s a hidden bug waiting for the right time to show up.</li><li>Once you have bugs documented, prioritize them and start working from there.</li><li>Stay calm.</li></ol><h3>6. Transparency and accountability.</h3><p>Software development is a team job. Making sure that you have project-wide visibility for all the stakeholders involved (teams, PM and clients) in getting something pushed to Production will eventually lead to better results and increased collaboration.</p><p>With proper collaboration and transparency (like the one we see on our merge requests), your company will be better prepared for when that wild bug appears, by allowing engineers to read each other’s code and to make improvements on the spot.</p><p>On a project level, the Project Manager is the face that responds for the product’s final quality. But in the middle of the process the ownership of the accountability might belong to a specific developer or QA engineer.</p><p>Just to give you a glimpse, at RedLight the responsibility of a properly implemented task moves from the developer, to the code reviewers, to the QA engineer and finally it rests with the Project Manager and the QA lead. At the end of the day, all of these members share some of the responsibilities and good results tend to be seen when proper collaboration is in sight and when team members feel empowered for the quality of a product.</p><p>Independently of your company’s methodology, the key to keeping things flowing regularly is to track accountability with project-wide transparency. It gives everyone a sense of importance and responsibility towards their colleagues and usually leads to better results with an engaged and happy team.</p><h3>Conclusion</h3><p>The whole world of testing and QA is about mitigating present problems and future risk that are currently unknown. Yet, we take risks all the time every time we push something to a new environment. And even if we are, as a QA team, in the business of lowering the risks, there’s not any guarantee that our company will launch a risk-free product. So we should not let fear stop us from placing another piece on top of our jenga game.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*slvvDaHkSDAZlPr08E1iYQ.jpeg" /></figure><p>The best way to keep your product stable and low on your Sentry log is to make sure that every step of the process has clear ownership, transparency and accountability.</p><p><em>João Gonçalves is currently a Project Manager at RedLight, having worked as the head of the QA department for 4 years.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=238116c14306" width="1" height="1" alt=""><hr><p><a href="https://medium.com/redlight-software/redlight-testing-238116c14306">RedLight &amp; Testing</a> was originally published in <a href="https://medium.com/redlight-software">RedLight Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[CLOSED] QA Job Opening]]></title>
            <link>https://medium.com/redlight-software/qa-job-opening-8b1f2af8a325?source=rss-20720d2c5fc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8b1f2af8a325</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[recruitment]]></category>
            <dc:creator><![CDATA[João Gonçalves]]></dc:creator>
            <pubDate>Wed, 07 Feb 2018 16:26:36 GMT</pubDate>
            <atom:updated>2021-03-17T11:02:16.648Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/756/1*7_7CBrZwxTY12CxWPYH-Zw.png" /></figure><h3><strong>redlight is now looking for one QA Engineer.</strong></h3><p><em>QA Engineer</em> — You’re a quality assurance professional who can architect, manage and write tests for software development with efficiency in a way that’s transparent for the whole organization. You are able to learn quickly and understand the requirements of the software you will be testing, and have a natural knack for breaking things.</p><p><strong>What You’ll Do</strong></p><ul><li>Perform manual click-through quality assurance on client projects and internal products;</li><li>Review unit &amp; integration tests for most pull requests on the projects where you’ll be assigned;</li><li>Write stress tests and keep them updated;</li><li>Maintain a knowledge base for future reference for QA purposes;</li><li>Define and improve testing standards;</li></ul><p><strong>Requirements:</strong></p><ul><li>2+ years experience on Software Quality Assurance;</li><li>Experience in Software Development is a <em>plus</em>.</li></ul><p><strong>Nice to haves:</strong></p><ul><li>Masters/Bachelor in CS, Mathematics, Physics or any other area based on high capacities of abstraction and calculations.</li></ul><p><strong>What’s Like Working At RedLight</strong></p><p>At RedLight we live by the ‘Work Hard, Play Hard’ motto. We expect our employees to feel deeply integrated in our team for us to give back whenever we have the chance. We value people, we know we can’t go anywhere without our team that ultimately is our second family. We want you to be part of it. We want you to grow with us making awesome stuff.</p><p>Currently, RedLight has two offices in Portugal: Coimbra and Lisbon. Nevertheless, it is a remote-friendly company, meaning you are free to work anywhere.</p><p>RedLighters’ average age is 28 years old, which makes us a young and fun company to work with. Our communication is mostly made through Slack and our daily work is based on tools like JIRA, Trello, GitHub, Sentry, Mixpanel and G Suite.</p><p><strong>What We’ll Give You</strong></p><ul><li>Health Insurance</li><li>Free fresh amenities;</li><li>Free Wi-Fi hotspot;</li><li>Free Spotify Premium;</li></ul><p><strong>Application deadline/Team Presentation &amp; Starting Date</strong></p><p>23rd February, 19th March.</p><p><em>Apply by sending your CV to recruitment (at) weareredlight.com.</em></p><p><strong>UPDATE: </strong>Job offer closed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b1f2af8a325" width="1" height="1" alt=""><hr><p><a href="https://medium.com/redlight-software/qa-job-opening-8b1f2af8a325">[CLOSED] QA Job Opening</a> was originally published in <a href="https://medium.com/redlight-software">RedLight Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Looking for love in all the right places.]]></title>
            <link>https://medium.com/nest-collective-writing-wall/looking-for-love-in-all-the-right-places-59f36cd226f6?source=rss-20720d2c5fc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/59f36cd226f6</guid>
            <category><![CDATA[co-working-spaces]]></category>
            <category><![CDATA[coworking]]></category>
            <category><![CDATA[shared-office-space]]></category>
            <dc:creator><![CDATA[João Gonçalves]]></dc:creator>
            <pubDate>Thu, 30 Nov 2017 17:09:32 GMT</pubDate>
            <atom:updated>2017-11-30T17:09:32.157Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*WvnBpVmcz68Kkb9Mn4iaiQ.png" /></figure><p>Pedro Reis set himself for a big adventure. To ride a bicycle from Caldas da Rainha to Viana do Castelo, summing up 315km and stopping by places where companies and every freelancer can have their shared workspaces.</p><p>This goal from Pedro was created by his connection with <a href="http://mushrooming.fi/">mushrooming.fi</a>, a Finnish company that is used look for shared work spaces like co-working venues or just places like Nest.</p><p>Pedro went on with a conversation with Miguel, Tony and João Monteiro to tour our office and to understand a bit of how we work. <a href="https://www.facebook.com/events/342712916198480/permalink/343586752777763/">Here’s the link of the full video.</a></p><p>As said before, this visit was part of a bigger tour. Pedro visited <a href="http://www.usethisspace.com/">Use</a> (Caldas da Rainha), then moved to <a href="http://www.basecowork.net/">Base Cowork</a> (Leiria). He pedalled this Tuesday under bad weather conditions to Nest Collective, leaving in the next morning towards <a href="http://www.fusioncowork.com/">Fusion Cowork Aveiro</a>. Today he’s on <a href="http://porto.io/">Porto i/o</a> and he’ll pedal through the last stage tomorrow, heading to <a href="http://www.dinamo10.net/">Dinamo10</a>, in Viana do Castelo.</p><p><em>Just in case you’re wondering, and we know you do, here are the lengths of the stages, from starting point (previous shared space) to finish line (new shared space):<br>Caldas da Rainha — Leiria, 53Km.<br>Leiria — Coimbra, 67Km.<br>Coimbra — Aveiro, 58Km.<br>Aveiro — Porto, 63Km.<br>Porto — Viana do Castelo, 70Km.</em></p><p>We’d like to thank Pedro for choosing Nest to stop by, we’d also like to thank him for his kindness and support for Nest. We expect you at Nest again!</p><p>Thanks,</p><p>The Nest.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59f36cd226f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nest-collective-writing-wall/looking-for-love-in-all-the-right-places-59f36cd226f6">Looking for love in all the right places.</a> was originally published in <a href="https://medium.com/nest-collective-writing-wall">Nest Collective Writing Wall</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nest Collective é ponto de recolha para vítimas dos incêndios de 15 de Outubro.]]></title>
            <link>https://medium.com/nest-collective-writing-wall/recolha-cc37caf14422?source=rss-20720d2c5fc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/cc37caf14422</guid>
            <category><![CDATA[alerta-vermelho]]></category>
            <category><![CDATA[disaster-response]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[charity]]></category>
            <category><![CDATA[disaster-relief]]></category>
            <dc:creator><![CDATA[João Gonçalves]]></dc:creator>
            <pubDate>Mon, 16 Oct 2017 16:54:15 GMT</pubDate>
            <atom:updated>2017-10-24T13:44:55.022Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gXhH1B2yqyH9wyKKZPLFmQ.jpeg" /></figure><h3>ATENÇÃO A TODOS:</h3><p>Durante esta semana, o nosso <em>hall</em> de entrada é um ponto de recolha para colectar bens de primeira necessidade para os desalojados das comunidades mais próximas de nós.</p><p>Todos os bens deverão ser entregues no Nest Collective (Centro Comercial Avenida, Av. Sá da Bandeira, nº 33, 2ª Fase, 6A) das <strong>9h até às 19h, até esta Sexta-feira</strong>.</p><p>Os bens que estamos a colectar estão divididos em 4 tipos:</p><h3>ROUPA</h3><p>Precisamos de roupa para todas as idades, nomeadamente:</p><ul><li>Casacos;</li><li>Camisolas, t-shirts;</li><li>Calças;</li><li>Calçado;</li><li>Pijamas;</li><li>Roupa de cama como cobertores e lençóis.</li></ul><p>Para agilizar o nosso processo, é preferível que nos faças chegar estes artigos separados por sexo e por tamanho.</p><h3>HIGIENE</h3><p>Precisamos dos seguintes artigos:</p><ul><li>Artigos de primeiros socorros;</li><li>Artigos de higiene feminina;</li><li>Desodorizantes;</li><li>Fraldas;</li><li>Pasta e escovas de dentes;</li><li>Pomadas para queimaduras;</li><li>Soro para olhos.</li></ul><h3>COMIDA</h3><p>Precisamos de comida que possa ser consumida de imediato e/ou com alargado prazo de validade, nomeadamente:</p><ul><li>Azeite e óleo;</li><li>Cereais e bolachas e barras energéticas;</li><li>Conservas e enlatados;</li><li>Leites (pacotes de 20cl);</li><li>Massas e arroz.</li></ul><h3>OUTROS</h3><ul><li>Sacos e caixas para organização e entrega dos artigos recolhidos;</li><li>Ração para animais;</li><li>Sacos-cama;</li><li>Toalhas.</li></ul><p><a href="https://trello.com/b/UewdCfUv/ponto-de-recolha-15-out"><strong><em>Temos um board de Trello público</em></strong></a><strong><em> com as necessidades actuais, que vamos actualizado à medida que os artigos nos forem chegando.</em></strong></p><p><strong><em>Antes de trazeres alguma coisa, confirma que a necessidade ainda existe do nosso lado confirmando no link em cima.</em></strong></p><p>Relembro que toda a ajuda deve ser entregue no Nest Collective das <strong>9h às 19h</strong>, de Segunda-feira <strong>até Sexta-feira, 20 de Outubro</strong>.</p><p><em>A nossa porta, para quem não conhece, está no 6º andar do C.C. Avenida, entrando pela Av. Sá da Bandeira. Basta tocar à campainha e deixar os artigos.</em></p><p>Caso queiras ajudar mas não consegues entregar directamente em Coimbra ou preferes ajudar financeiramente, <a href="http://apbv.pt/ajude-nos-a-ajudar-donativos/">podes fazer uma doação do valor que bem entenderes à Associação Portuguesa de Bombeiros Voluntários através do PayPal ou transferência bancária</a>.</p><p><em>Obrigado.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cc37caf14422" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nest-collective-writing-wall/recolha-cc37caf14422">Nest Collective é ponto de recolha para vítimas dos incêndios de 15 de Outubro.</a> was originally published in <a href="https://medium.com/nest-collective-writing-wall">Nest Collective Writing Wall</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google’s lack of social graph could and should be solved with Android.]]></title>
            <link>https://medium.com/@jpmgoncalves/googles-lack-of-social-graph-could-and-should-be-solved-with-android-9f7af56d6203?source=rss-20720d2c5fc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f7af56d6203</guid>
            <category><![CDATA[google]]></category>
            <dc:creator><![CDATA[João Gonçalves]]></dc:creator>
            <pubDate>Fri, 02 Jun 2017 23:18:02 GMT</pubDate>
            <atom:updated>2017-06-02T23:18:02.101Z</atom:updated>
            <content:encoded><![CDATA[<p><em>I started this post two years ago. I really wanted to share this idea with the world so I’m rewriting it on Friday and posting it on Saturday, 00:17am. Enjoy the post.</em></p><p>If there’s something that’s really personal in this digital era is our smartphone. Our smartphone runs our apps, consolidates all our info in one device and lets us talk with everyone we know. It’s basically a person’s organ already.</p><p>It’s known that Google+ is by far <em>not</em> the most successful Google product but it’s also known that Google won’t leave social.</p><p>But along with every single smartphone, there’s a thing that I think it could be improved — the feed of our real world interactions, an app you’re really used to named <em>Contacts</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/1*3KvBfGxOIz56WPPYDdekow.png" /></figure><p><em>Contacts</em> displays all the info you have on someone you’re eager to have a register for on your contact list. I bet that there are some people on your list that you probably don’t want there, probably related with work — but at least you’re more eager to text, DM on Slack or call someone you work with than interacting on LinkedIn, right?</p><p>After a couple years of an <em>adhoc</em> contact list management, something that requires real contemplative qualities, I reached this state of a personal contact list that only includes family, real friends and work. I really don’t need anyone else. There’s lots of people I only interact with on Facebook, Twitter, Messenger, but I really don’t need their phone numbers or emails since we already communicate on those platforms.</p><p>So, on my end, I get this ultra precise list of people I want to connect with via text and calls. Everyone else has been dismissed to other platforms. But you know what tends to happen? People change their numbers, their addresses, their jobs, and we’re not always on the same loop and your contact profile for these people is now incorrect.</p><p>My contact list, although very precise and thoughtful, is filled with old pixelized pictures, wrong numbers (or old numbers that are not the priority), regretful adolescent email addresses, past companies they worked for, and I still have to change this manually.</p><p>And this something that <em>grinds my gears</em>.</p><p>I should be able to have this info updated because these people trusted me with it in the first place. People have filled in this info on their phones. Why can’t I access it?</p><p>That’s exactly why I think that Google should have a say on this.</p><p>It’s not a social network. It’s rather your personal network. Where you can add people into it (if they accept), with some previously defined layers of privacy.</p><p>For your own profile, you’re going to fill in every single info you’re asked. Phone numbers, email addresses, workplace, work address, home address, etc. But I’m sure you don’t want to share all this info with everyone. So you can create a work layer — to show only work related info, a personal layer — to show your phone number and email address, and any other combination you want to make.</p><p>Imagine this: you meet someone at night. And you just want someone’s connection in order to keep up with a conversation; you just need a username or a phone number. Ask someone for a small Google Contacts username, define the layer you want to share and they’ll get a contact request.</p><p>He or she will be able to accept or delete the request and define the layer (personal, professional or other) you’re going to have access to.</p><p>This way, once the other person changes anything you have access to, you’ll have an updated profile and the connection won’t be lost.</p><p>I have this dream that if someone trusts you with information, specially information that lets you connect with someone, this info should always be updated.</p><p>And Google could easily develop this on <em>Contacts, </em>providing it a massive scale at launch, which is really what matters: you don’t want to push people into another service or wait for them to be on it to be able to interchange simple phone numbers.</p><p>It’s also not a social network, but it gives Google a real social graph. One that’s probably more effective and more close to the <em>real </em>world.</p><p>And you are happy. Because you can share specific information freely without any fuss, saving you time and you still get to keep a connection with the person that trusted you in the first place.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f7af56d6203" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nest Collective Summer Internship’17 Blogpost]]></title>
            <link>https://medium.com/nest-collective-writing-wall/nest-collective-summer-internship17-blogpost-c379717be851?source=rss-20720d2c5fc5------2</link>
            <guid isPermaLink="false">https://medium.com/p/c379717be851</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[internships]]></category>
            <dc:creator><![CDATA[João Gonçalves]]></dc:creator>
            <pubDate>Thu, 06 Apr 2017 17:16:24 GMT</pubDate>
            <atom:updated>2017-04-06T17:17:51.915Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/466/1*Rsx_S5tUcbtjvS3goCmVhQ.png" /></figure><p>Hi there! For the second year in a row, we’re very happy to announce the 2017 edition of Nest Collective’s Summer Internship!</p><p>A year ago, our beloved interns developed a product that we’re very proud of, <a href="https://medium.com/nest-collective-writing-wall/tagged/internships">Aurora</a>. And since most of them have stayed to work with Nest Collective based companies, it’s now time to look for another batch of fresh interns.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cv5JQAmNV9G7UX5s6Ubdug.png" /></figure><p>If you haven’t heard about our program, Nest Collective’s Summer Internship consists in one of the best introductions to the world of product development one can have during the summer in Coimbra. And yes, sand &amp; waves are just about 30Km away, so you still can have some awesome time off . 😄</p><p>Our program includes the mentorship of some of the best Coimbra based companies that will help interns create amazing products. The internship will happen, of course, at the Nest Collective which is proudly the best office to work on Coimbra. And the best of all, is that with this internship:</p><ul><li>you’ll be challenged to create products that YOU can identify yourself with. Being part of the creative process, enables everyone to leave their fingerprints on the final output;</li><li>you’ll be pushed to use technologies &amp; tools that are actually used by the best companies in the industry and not things that are basically on their way to be forgotten in the world of product development;</li><li>you’ll have an income for your time here. It’ll help you cover all your food &amp; travel expenses.</li></ul><p>OK, now that you already know what the Nest Collective is, it’s time for us to explain you what you’ll be <em>really</em> doing with us.</p><p><strong><em>This Is How It Works</em></strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lH-opQEUpd4YuECBg-ZX2w.png" /></figure><p><em>The First Day,</em> actually known as Day Zero — you’ll be invited for a meet &amp; greet for everyone working on Nest, a detailed office tour and we’ll help setting you up on what will be your workspace from that day on.</p><p>After that, we’ll move quickly into action with a week-long Design Sprint. The still-top-secret-idea to iterate on will be given to you by the Nest team, and from there, you’ll be free to do whatever you want with it, as a team.</p><p>Depending on the time of month, all interns will go through a training stage lectured by Nesters, either before or after the Design Sprint. After this you’ll be left with a ~ 1.5 months of development. Each Friday there’s a showcase to present to the whole Nest the latest features, new design and any kind of advancements from last week’s showcase, when applicable.</p><p>In the end of the development step, there will be a final presentation of the product along with with a party we’ll gladly host to celebrate the launch of the product you’ve built.</p><p>So that’s it. Interested in applying to this Summer Internship? If you are, please read the instructions and apply through the <a href="https://nestcollective.typeform.com/to/GT3ugR">Typeform</a>.</p><p>P.S. — By the way, if you already talked with us on .works, you don’t need to apply again.</p><p>So here it is, the link that’s just the beginning of a unforgettable summer.</p><p><a href="https://nestcollective.typeform.com/to/GT3ugR"><em>Apply here</em></a><em> and good luck.</em></p><p><em>If you still have any questions left, please feel free to email us at internships (at) nestcollective.co.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c379717be851" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nest-collective-writing-wall/nest-collective-summer-internship17-blogpost-c379717be851">Nest Collective Summer Internship’17 Blogpost</a> was originally published in <a href="https://medium.com/nest-collective-writing-wall">Nest Collective Writing Wall</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>