<?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 Aria Rouco on Medium]]></title>
        <description><![CDATA[Stories by Aria Rouco on Medium]]></description>
        <link>https://medium.com/@AriaRouco?source=rss-f4bdc7a2de5d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4xb02ch6FjyRgCO5sXspwg.jpeg</url>
            <title>Stories by Aria Rouco on Medium</title>
            <link>https://medium.com/@AriaRouco?source=rss-f4bdc7a2de5d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 21:38:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@AriaRouco/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[  -     ✨]]></title>
            <link>https://medium.com/@AriaRouco/-0390b1142be0?source=rss-f4bdc7a2de5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/0390b1142be0</guid>
            <dc:creator><![CDATA[Aria Rouco]]></dc:creator>
            <pubDate>Thu, 05 Mar 2026 10:06:37 GMT</pubDate>
            <atom:updated>2026-03-05T10:06:37.805Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s been almost a year since I joined my current team, and I have to say that these have been some interesting months regarding the way that my team works.</p><p>From the very first day, I’ve had some personal reflections about how the team works and how we do <em>things</em>.</p><p>One example is 𝘱𝘭𝘢𝘯𝘯𝘪𝘯𝘨 𝘮𝘦𝘦𝘵𝘪𝘯𝘨. Planning hasn’t always felt convenient: it often required pre-work before the session and post-work afterward, just to make Jira reflect what was actually decided and done during planning.</p><p>Another example is our 𝘦𝘹𝘱𝘦𝘳𝘪𝘮𝘦𝘯𝘵𝘢𝘵𝘪𝘰𝘯 𝘥𝘢𝘺𝘴. Every two weeks, we have two days dedicated to exploring, learning, and trying new things. Currently, those days are set on a Monday and Tuesday.</p><blockquote>If you are not doing this, I highly recommend you to negociate having these days.</blockquote><p>Interestingly enough, during the past months, I’ve heard some team members questioning some of our “dynamics”.</p><p>As a result, I’ve been assigned to lead the conversations on our ways of working.</p><blockquote>By “𝘄𝗮𝘆𝘀 𝗼𝗳 𝘄𝗼𝗿𝗸𝗶𝗻𝗴”, we mean the agreements we make around guidelines, practices, and habits that help us succeed on a daily basis.</blockquote><p>Over the past few weeks, we’ve been having meetings to review them and , just in case you are interested in proposing a review on your ways of working, here’s how I’ve done it:</p><p>𝗗𝗶𝘀𝗰𝗼𝘃𝗲𝗿𝘆 𝘀𝗲𝘀𝘀𝗶𝗼𝗻s<br>We had two session of discovery. We created a collaborative board to put the things that we 𝗹𝗶𝗸𝗲, the things we 𝗱𝗼𝗻’𝘁, 𝗽𝗿𝗼𝗽𝗼𝘀𝗮𝗹𝘀 and 𝗮𝗰𝘁𝗶𝗼𝗻𝘀.</p><p>We started reviewing only the things we like and would like to keep, and the things we don’t and want to change. <br>As we reviewed each of the ‘thoughts’ on each section, we clustered them (trying to put all the notes that are similar together) and commented on each of them.</p><p>Once we had , wrote down the agreements and some actions were assigned to different member of the team.</p><p>𝗥𝗲𝘃𝗶𝗲𝘄 𝗦𝗲𝘀𝘀𝗶𝗼𝗻<br>We continued reviewing the next two sections: <strong>proposals and actions.</strong> Going one by one and coming to an agreement with the team.</p><p>𝗖𝗲𝗿𝗲𝗺𝗼𝗻𝗶𝗲𝘀<br>We had a collaborative board where we put all the ceremonies we had and put a timer to add sticky notes saying things we liked or wanted to change. I’ve also added some criteria to help the team to review different aspects of the meetings we have and make a good evaluation. Some examples I put:</p><p><strong>1. Structure</strong></p><p><strong>2. Frequency</strong></p><p><strong>3. Pre-work</strong></p><p><strong>4. Post-work</strong></p><p><strong>5. Usefulness &amp; Value</strong></p><p><strong>6. Participation &amp; Roles</strong></p><p>Reviewing all our ceremonies and our thougts took two sessions but it was completely worth it.</p><p>As a result, we have now an updated version of the 𝘁𝗲𝗮𝗺 𝗮𝗴𝗿𝗲𝗲𝗺𝗲𝗻𝘁𝘀 or 𝘄𝗮𝘆𝘀 𝗼𝗳 𝘄𝗼𝗿𝗸𝗶𝗻𝗴 where everyone in the team had a saying, was present during the review and agreed on how we should work from now on.</p><p>I highly recommend to review the ways of working if you haven’t done that in a while. Specially if your team has a high rotation. Most of the agreement you see in the teams come from a long time ago, build by people that left the team and no longer represents how the team wants to work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nkFyR9duKKdHKqIOCT9yeg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0390b1142be0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Switching Jobs After 5.5 Years — My First 4 Months]]></title>
            <link>https://medium.com/@AriaRouco/switching-jobs-after-5-5-years-my-first-4-months-6a3a20f971a8?source=rss-f4bdc7a2de5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a3a20f971a8</guid>
            <dc:creator><![CDATA[Aria Rouco]]></dc:creator>
            <pubDate>Thu, 17 Jul 2025 06:38:02 GMT</pubDate>
            <atom:updated>2025-07-17T06:38:02.574Z</atom:updated>
            <content:encoded><![CDATA[<h3>Switching Jobs After 5.5 Years — My First 4 Months</h3><p>Starting a new position can be really challenging. Changing jobs after five and a half years is a big shift, and that was definitely the case for me.<br> It’s not just about the fact that you switched jobs. There were a lot of side effects to this change that I couldn’t foresee.</p><p>It’s been 4 months since I joined Spotify, and these are my thoughts on what’s changed, what I’ve learned, and what I would tell myself (or you) before making the next job switch.</p><h3>What changed?</h3><h3>Office Life: Same City, Different Routine</h3><p>My commute changed. I used to walk every morning to the office, and it only took me 15 minutes — and that’s at a slow, relaxing pace.<br> Now it takes me 30 minutes to walk to the office, uphill. Even though I usually ride these days to get there faster, I still have to ride on one of the busiest avenues in the city, which makes the commute a bit intense.</p><p>Even my lunch routine has changed: I used to have a canteen with food service. Now I don’t have that anymore, so I have to plan ahead of time what I want to “Tupperware” for the next day.<br> The upside? We have several snacks available for those mid-afternoon cravings.</p><h3>Relationships: A Subtle but Deep Shift</h3><p>I used to have good relationships at work that I really enjoyed. Even the ones I didn’t see that much — I would really enjoy just seeing them around at the office.<br> Now I don’t get to see those people anymore for the obvious fact that we don’t work in the same place. But also, I don’t have such a relationship to see them outside of work, and even if I did, it would feel different.</p><p>Even out-of-office interactions — weekend drinks, sports, random plans — started fading. I would even spend my weekends with some of them, and that suddenly started to decrease organically. I attribute this to the fact that some of the best plans come up at the coffee area or even within corporate Slack because it’s easier and more practical.</p><p>I used to work at the same company as one of my best friends, and even though we talk and see each other very often, not being able to meet at the office changed the dynamic.</p><h3>The New Job: Learning Curve of a New Ecosystem</h3><p>Starting a job is almost like doing an intensive course. Every day you get a lot of new information, and your brain needs to process it — from HR-related tasks to actual lines of code, from business context to organization charts. Everything you are told is a new piece of information that your brain needs to process at some point.</p><p>This new position got me going back to coding as a backend engineer, so I had to refresh old Java concepts and retrieve from my mental “cold storage” knowledge about the JVM and dependency injection that I thought were too far back to even remember.</p><p>Each company has its own way of doing things, and each team also has its own way of doing things. So when you join a team, you need to observe how the team works and why they do things the way they do. Even if you were using Kubernetes before, the way it’s used in the new job can be completely different from your previous job.</p><h3>✨ What’s New &amp; What I’m Grateful For</h3><p>Over these past months, I had the opportunity to get introduced into one of the largest companies and best products there are out there in the music industry, and I’m so glad to be part of it.</p><p>I got to learn how my most-used application actually works — inside out — to actually see how the <em>maquinaria</em> works and the values that the company has.</p><p>I got to meet people that are insanely nice. When I say this, I really mean it. The atmosphere is ridiculously amazing.</p><h3>📘 Learnings &amp; Friendly Reminders</h3><p>I wrote the following lines thinking about what I’d like to remember in the future if I have to switch jobs. I hope you find them useful, and feel free to add a comment if you think of something I missed. Would love to hear your thoughts.</p><h4>1. Be patient — changes take time</h4><p>I think this is the most important one. I had, and still have, to remind myself to be patient. To let time do its work. There’s a lot of change going on, and it takes time to get used to it. Trust the process.</p><h4>2. Frustration will be by your side, but keep going</h4><p>There are a lot of things that are going to be done differently, and a lot of things that you will need to figure out — like where to find the source of information. I got to a point where every step of the way involved double-checking documentation several times. It can get frustrating. Be prepared to feel frustrated.</p><h4>3. Find your sources of wisdom</h4><p>I think a key point here is to find the people and the sources of information that can be handy to execute your work. Keep a notepad or bookmarks to track useful links you can refer back to.<br> People are the key: usually you can identify pretty quickly who has more knowledge within the team. Make sure to stay close to them.</p><h4>4. Find people who can explain how things work and are actually nice to be around</h4><p>This one is more related to how the company works in terms of benefits, culture, and activities that might be interesting. Seek kind and helpful people. This tends to make the onboarding process more human.</p><h4>5. Work on your sense of belonging</h4><p>My metric for this is the day I bring my mate to the workplace. I’m addicted to that thing and I need it. But for me, it also means that I feel at home somehow.<br> Whether it’s your mate or a coffee mug, make the office feel like home.</p><h4>6. Changes can be really tiring</h4><p>Get proper rest. I mean it. Your body needs it, your brain needs it. Get your 8 hours of sleep. You need more energy during the onboarding period.</p><h4>7. AI made my life easier</h4><p>Thank God for AI. AI tools made my onboarding process much easier. Going back to Java might have taken a lot of time. With AI, I was back in the blink of an eye.</p><h4>8. Stay around the coffee area</h4><p>The power that a coffee machine has is amazing. A lot of interesting and key conversations happen surrounding the coffee machine. Make sure you visit the coffee area often.</p><h4>9. Observe in the beginning, understand the why, then challenge</h4><p>As someone who has onboarded too many teams in my professional life, I know that this one works. Before coming with your “right” way of doing things, understand the history of the team — then you can make suggestions.</p><h4>10. Start early on with your Worklog</h4><p>Block 10–15 minutes weekly to update your worklog with clear, simple bullet points. Include as mush as you can— learning, docs read, bugs fixed, questions asked, even Slack threads. It doesn’t have to be perfect.<br>It’ll make self-reviews, feedback sessions, and promo prep way smoother.</p><h3>Conclusion</h3><p>Change is constant — even when things feel stable, they’re evolving.<br> Switching jobs after a long time brings both gains and losses, and it can feel overwhelming.<br>Be patient with yourself. Get real rest — your brain and body will need it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fYcpIPi7inN00R3eOUZMaw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a3a20f971a8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Shortcut Way to Rule Them All]]></title>
            <link>https://medium.com/@AriaRouco/the-shortcut-way-to-rule-them-all-5b7eb491b2b1?source=rss-f4bdc7a2de5d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b7eb491b2b1</guid>
            <dc:creator><![CDATA[Aria Rouco]]></dc:creator>
            <pubDate>Mon, 26 May 2025 07:31:19 GMT</pubDate>
            <atom:updated>2025-05-26T07:31:19.344Z</atom:updated>
            <content:encoded><![CDATA[<h4>For macOS users only… Sorry!</h4><p>Last week, we were given some time to experiment and explore anything we found interesting in the world of AI.</p><p>While many people embarked on ambitious model training projects or integrations, I ended up focusing on something a little more foundational to my daily flow: <strong>speed</strong>.</p><p>I took the opportunity to dive deeper into the AI tools available to us — both the internal ones and the <em>many</em> others out there — and how to use them effectively to work in my favor. I already knew most of them and had been using them <strong><em>heavily</em></strong> over the past two months, which made my onboarding process incredibly fast and smooth.</p><p>Like many people working in tech, I use <strong>browser-based tools</strong> for almost everything. And like many people, I have <strong>multiple Chrome profiles</strong> — one for work and one for personal stuff. I want to keep these two separated: access personal stuff in my personal Chrome profile and my work stuff in my work Chrome profile.</p><p>A good example of this is <strong>ChatGPT</strong> — I have one account for work and another for personal use, and I use them both frequently.</p><p>Another example is GitHub, or even tools that are only accessible through my work profile, like Workday. On the other hand, some pages, like WhatsApp Web, are linked to my personal profile only.</p><p>The problem is, every time I want to access one of these tools, I open Spotlight (⌘ + Space), type “Chrome”, check if I’m in the correct profile — and if I’m not, I have to switch — and then type the URL manually.</p><p>There’s one tool in particular that I use constantly at work, and it’s only available through the browser. That means I go through this entire process <strong>multiple times a day</strong>. For reference, I had to open that tool at least 12 times just two days ago.</p><p>So I had a brainstorming session with <strong>ChatGPT</strong> to make this process easier.</p><p>The suggestion was to use the <strong>Shortcuts</strong> app — and it worked surprisingly well. Here’s how to do it:</p><blockquote>1. Open the <strong>Shortcuts</strong> app.</blockquote><blockquote>2. Click <strong>+</strong> to create a new shortcut.</blockquote><blockquote>3. Name it something simple like <strong>chatgpt</strong>.</blockquote><blockquote>4. Add the action <strong>“Open URLs”</strong> and paste in: <a href="https://chat.openai.com/">https://chat.openai.com</a></blockquote><blockquote>6. Save it.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zOzMo26cypjIM3IME-9u7Q.png" /><figcaption>Shortcut screenshot</figcaption></figure><p>Now you can hit ⌘ + Space, type “<strong>chatgpt</strong>”, and your browser opens <strong>ChatGPT</strong>’s page. Except that I ended up having another issue: the page opened in a random Chrome profile.</p><p>So I got back to my brainstorming chat and decided to be a bit more specific with my needs. I polished a bit more the prompt to be very specific on what i was expecting:</p><blockquote>I have two chrome profiles, one for work and one for personal stuff. is there a way I can open the url in the chrome where I have a specific profile?</blockquote><p>Turns out that there’s an Automator app in macOS that you can do all crazy stuff to customize your computer with whatever you want or need.</p><h3>Create a profile-specific launcher with Automator</h3><p>You can build your own mini app to open a webpage in the right Chrome profile. Here’s how:</p><blockquote>Open <strong>Automator</strong> → create a new <strong>Application</strong>.</blockquote><blockquote>Add the <strong>“Run Shell Script”</strong> action.</blockquote><blockquote>Paste this script to launch ChatGPT in your profile:</blockquote><pre>&quot;/Applications/Google Chrome.app/Contents/MacOS/Google Chrome&quot; - profile-directory=&quot;&lt;PROFILE_NAME&gt;&quot; &quot;https://chat.openai.com&quot;<br><br># Tip: If you&#39;re unsure which profile is which, open each Chrome profile, <br># go to chrome://version, and look for the Profile Path.</pre><blockquote>4. Save each app with a name like <em>ChatGPT Work </em>or <em>ChatGPT Personal.</em></blockquote><blockquote>5. Close Chrome</blockquote><blockquote>6. Use ⌘ + Space to open Spotlight and launch your new app name</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0E3__vdPn5GhtXtaJzA-UA.png" /><figcaption>Automator screenshot</figcaption></figure><h4>Go the extra mile</h4><p><strong>✑ Give it a custom icon</strong></p><ul><li>Right-click your app → <strong>Get Info</strong></li><li>Copy an image or icon (like ChatGPT’s logo) from Preview</li><li>Click the small app icon in the corner and <strong>paste</strong> (Cmd + V)</li></ul><p><strong>✑︎︎︎︎ Improve easy access</strong></p><ul><li>Put the app in your Applications folder (or anywhere Spotlight indexes).</li><li>Drag it into your Dock for one-click access.</li><li>Use Cmd + Space to launch it by name (e.g., chatgpt work).</li></ul><h3>Closing words</h3><p>No, this isn’t rocket science — and I know that. AI can do so much more, especially if you’re a software engineer. But still… I kind of love this shortcut.</p><p>This was more about redefining how you do everyday things with AI. Sometimes the real value of AI isn’t about doing the work for you, but helping you <strong>think differently</strong>, <strong>explore faster</strong>, and <strong>build smarter</strong>.</p><p>Reevaluate the way how you do things — you might end up getting a completely different experience of your daily work with just a few minutes of assisted brainstorming sessions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JyH1C8N30rPWv1kqx7A6_A.png" /><figcaption>Ai created image</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b7eb491b2b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>