<?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 Ivan Arrizabalaga Getino on Medium]]></title>
        <description><![CDATA[Stories by Ivan Arrizabalaga Getino on Medium]]></description>
        <link>https://medium.com/@ivanarrizabalagagetino?source=rss-1404c2ab5286------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*_AHw2ru1b7FXh7UZ.jpg</url>
            <title>Stories by Ivan Arrizabalaga Getino on Medium</title>
            <link>https://medium.com/@ivanarrizabalagagetino?source=rss-1404c2ab5286------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:33:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ivanarrizabalagagetino/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[Getting back to basics: Ownership]]></title>
            <link>https://medium.com/joor-engineering/getting-back-to-basics-ownership-f015e3c0bcff?source=rss-1404c2ab5286------2</link>
            <guid isPermaLink="false">https://medium.com/p/f015e3c0bcff</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[ownership]]></category>
            <dc:creator><![CDATA[Ivan Arrizabalaga Getino]]></dc:creator>
            <pubDate>Mon, 17 Feb 2025 17:12:13 GMT</pubDate>
            <atom:updated>2025-02-21T13:32:42.652Z</atom:updated>
            <content:encoded><![CDATA[<p>I still play basketball two or three times a week.</p><p>At this stage, most of us on the court are dealing with old injuries and aging bodies, but we keep playing. Why?</p><p>Because we love it, and because we take ownership — not just of our game, but of everything that comes with it.</p><p>Yesterday morning, as I was cleaning my basketball, I realized how deeply that mindset extends beyond the court. Ownership is why I still play. It’s also why we care so much about the systems we build at <strong>JOOR</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5eB4CLkg310YwM0gMXD_sA.jpeg" /><figcaption>Who would have thought you could clean a basketball?</figcaption></figure><p>The past few weeks have been challenging for our team.</p><p>With the <strong>first major markets of the year</strong>, platform activity surged — something we welcome, but also something that tests the limits of any system. While we proactively planned for this, we also faced unexpected slowdowns and downtime, and we take full responsibility for that.</p><p>Since January, we have implemented:</p><ul><li><strong>10</strong> significant optimizations in our <strong>application features</strong></li><li><strong>6</strong> improvements in our <strong>APIs and integration</strong> subsystems</li><li><strong>6</strong> upgrades in our <strong>infrastructure</strong></li><li>Additional enhancements to our <strong>monitoring</strong> systems</li><li>and counting …</li></ul><p>If you’re one of our customers and experienced disruptions, we sincerely <strong>apologize</strong>. We know how critical JOOR is to your business, and don’t take that lightly.</p><p>If you’re on our team, you know we’ll stay vigilant. We’ll <strong>continue</strong> to improve performance and stability week after week.</p><p><strong>And now?</strong></p><p>We have identified different opportunities to make JOOR faster and more reliable like:</p><ul><li>Better thresholds and limits on our <strong>alerts</strong> for early detection</li><li>Implementing <strong>data archiving</strong> policies on non-needed data</li><li>Optimizing <strong>scaling</strong> policies on our clusters</li><li>Reviewing <strong>legacy services</strong> with not-so-great queries</li><li>…</li></ul><p>The job is not done, we <strong>own it </strong>— end to end.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f015e3c0bcff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/joor-engineering/getting-back-to-basics-ownership-f015e3c0bcff">Getting back to basics: Ownership</a> was originally published in <a href="https://medium.com/joor-engineering">JOOR Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why was I rejected from my JOOR interview?]]></title>
            <link>https://medium.com/joor-engineering/why-was-i-rejected-from-my-joor-interview-f7af1aafa2dc?source=rss-1404c2ab5286------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7af1aafa2dc</guid>
            <category><![CDATA[team-culture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Ivan Arrizabalaga Getino]]></dc:creator>
            <pubDate>Tue, 19 Mar 2024 17:03:36 GMT</pubDate>
            <atom:updated>2024-03-21T12:53:16.935Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Let’s say you interview for one of our engineering positions, you feel like you have crushed every little thing, and, yet, … no offer. What happened?</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/0*AIXodaa3PScNAKBO.jpg" /></figure><h3>How do we organize our hiring pipeline?</h3><p>We recognise that applying to any position sucks no matter what, that’s why we are transparent with our processes.</p><p>Everything starts with the <strong>job description.</strong></p><p>We try to include some context about us, our expectations, the future type of work, available locations, and, above all, a comprehensive list of perks, including the compensation range for the position, no mystery, we don’t want you to lose your time.</p><p>Once the offer is published, we <strong>review internally</strong> every applicant looking for potential fits. Surprisingly, many of the candidates can’t qualify for the position: non-viable locations, total lack of experience in the role (not talking about tech stacks), a salad of buzzwords with no rhyme, resumes with lots of typos…</p><p>When we find you (😉 a lovely candidate), <a href="https://www.linkedin.com/in/naomi-granshaw-31121550/">Naomi</a> will arrange a super brief <strong>HR intro screening</strong> with you. Don’t be afraid, we ain’t gonna challenge your talent yet, but we need to confirm a few things: a legit interest in the role, you can speak good enough English, and our mutual expectations are aligned. <strong>15mins or less</strong>.</p><p>99% of people will move quickly from the HR call to the <strong>leveling interview</strong>. Our goal here is to discover if the candidate can fill our expectations for the role: experience, knowledge, appetite, and, above all, humanity 😅. <strong>30mins</strong>.</p><p>No kidding, like any other organization, we have our fair share of challenges but we can’t afford to hire a bad teammate regardless of how great (s)he codes.</p><p>One or two days after the leveling interview you receive an invite to our final boss… the (remote) <strong>onsite</strong>.</p><h3>The onsite</h3><p>The last stage consists in a series of 3 interviews that we try to run in a row to close our mutual discovery:</p><ul><li><strong>Culture fit</strong>: An open talk with 1 or 2 future teammates where they try to answer the question “Would you like to work with this person?” <strong>30mins</strong>.</li><li><strong>Technical interview</strong>: A longer session with a couple of other people to do some work together. Mostly consists of a few closed technical questions, a brief open design question, and some pairing on a minimalistic exercise. <strong>1hour</strong>.</li><li>[<strong>Management interview</strong>]: Lastly, depending on the role, we will have a last session with one of the managers to close the process. <strong>30mins</strong>.</li></ul><blockquote>In total a JOOR process for you should no longer than <strong>2h45mins</strong> with no take-home assignment 🚀</blockquote><h3>😴 I crushed it, why no offer?</h3><p>Maybe you:</p><ul><li>Only talked about <strong>frameworks</strong> instead of designs decisions.</li><li>Didn’t <strong>listen</strong> while pairing with your future teammates.</li><li>Coudn’t recognize any <strong>mistake</strong> from your past.</li><li>Didn’t care about the <strong>big picture</strong>.</li><li>Navigated the code with no rhyme or <strong>reason</strong>.</li><li><strong>Copied and pasted</strong> until a miracle happens.</li><li>Didn’t show <strong>curiosity</strong>.</li><li>Didn’t recognize the value of <strong>writing</strong> and reading.</li><li>Have a gigantic <strong>ego</strong>. 🙅</li></ul><p>or … maybe you actually did a very good job on your interview but somebody else did better.</p><p>In the end, the question is not if you are qualified for the role but if you’re the one that, we think, can help us the most.</p><h3>That’s all folks!</h3><p>You might be wondering why anybody should care about the hiring philosophy of a mid-sized scale-up.</p><blockquote>It’s just a testament of our vision for building the right company, with the right values and, above all, <strong>the right people</strong>.</blockquote><p>Neither you as a candidate nor we as a company are perfect. We may surely lose some incredible candidates along the way 🤷‍♂. However, if you’re curious, we often have some open positions here👇</p><p><a href="https://www.joor.com/current-openings">https://www.joor.com/current-openings</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7af1aafa2dc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/joor-engineering/why-was-i-rejected-from-my-joor-interview-f7af1aafa2dc">Why was I rejected from my JOOR interview?</a> was originally published in <a href="https://medium.com/joor-engineering">JOOR Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting back to basics]]></title>
            <link>https://medium.com/joor-engineering/getting-back-to-basics-358ba3d0f1dc?source=rss-1404c2ab5286------2</link>
            <guid isPermaLink="false">https://medium.com/p/358ba3d0f1dc</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[teams-and-teamwork]]></category>
            <dc:creator><![CDATA[Ivan Arrizabalaga Getino]]></dc:creator>
            <pubDate>Wed, 04 Oct 2023 09:53:37 GMT</pubDate>
            <atom:updated>2023-10-04T09:53:37.406Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>What if I told you that the latest framework is not what you need to become a better engineer?</blockquote><p>I spent many years thinking that reading books about the latest and finding time to catch up with the newest language or framework was the way to become a successful professional (whatever that means).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/551/1*H4B1_p2dk_sLc0nEzxvWkA.png" /><figcaption>Some of the things you end up reading for no particular reason</figcaption></figure><p>Lately, I realised that even though there is value and some fun, that’s not the key aspect to growth, let’s talk about other factors.</p><h3>What areas of growth come to your mind?</h3><p>Think about it.</p><p>Surely there are things like Agile, CD/CI, Kubernetes, DDD, … popping into your head.</p><p>Do you remember how you felt the last time someone told you they were working with <a href="https://www.reddit.com/r/rust/comments/sdqwsz/what_can_we_predict_about_the_future_of_rust/">Rust</a> instead of your boring backend language?</p><p>That’s just <a href="https://en.wikipedia.org/wiki/Fear_of_missing_out"><strong>FOMO</strong></a> (fear of missing out) and if you just follow those breadcrumbs you never gonna feel satisfied.</p><p>Whether you like it or not, we all have tons of exposure to external media and information: Udemy, Coursera, LinkedIn… even mainstream press tell you that if you complete the next “<em>Crash course in PinkyWinky</em>” you’ll get a six-figure salary and your life will be made of unicorns and exotic islands.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lIl-d0w9TTUqJSj8xL-rWg.png" /><figcaption>Look at this beautiful people discussing how to draw a chart with no axis or legend or sense at all</figcaption></figure><p>Then you see an ad for trendy technology, spend $9.99, a couple of hours, share your new badge on LinkedIn, get some likes from a network made of ghosts and now you’re a better professional, really? 🤔</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/0*17ZkVce67XvfUPN8.jpg" /></figure><p>Keeping up with technology it is indeed an important piece of our career but, by no means, as important as other basic factors.</p><h3>What are the basics?</h3><p>Software engineering is a collaborative craft, sorry. 🤷‍♂</p><p>We were told for so long that as software engineers we could be lone rangers but that’s false.</p><p>Our work is about listening to people, reading docs, gathering information, modeling the problem, and then, right at the very end, typing the code.</p><p>That’s why there are some basic stuff that we should focus on instead like:</p><ul><li><strong>Reading</strong>: Every day millions of dollars are wasted because people don’t read the damn docs, requisites, or feedback coming from the rest. It is sad cause it is true. This is not about remembering stuff, is about understanding the problem you’re solving and the tools you have at your disposal.</li><li><strong>Trust</strong>: As with any other collaborative stuff, like any other team sport, software engineering at its finest needs high trust dynamics within the team. Without trust, every single step turns into a check, double check, eta updates, private DMs, never-ending slack threads, and politics, tons of politics.</li><li><strong>Transparency</strong>: As easy as sharing where you are, what worries you, and how you think we should move forward. No sugarcoating and lots of <a href="https://en.wikipedia.org/wiki/Radical_Candor">radical candor</a> regardless of your position.</li></ul><p>There are more, I’m sure, but if you excel in these ultra-simple practices you’re likely to be a great teammate and the foundations for being a great software engineer.</p><h3>Wrap it up</h3><p>The industry, your colleagues, your parents, your bosses, hr, and your neighbors will tell you that you have to focus on learning new technologies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*e1eHRwiM6cxONJah" /></figure><p>That’s ok BUT misses some critical aspects with even higher value and lower cost of acquisition, I called those “basics”.</p><p>Look for teams where these basics behaviours are encouraged, make those part of your professional DNA and spread them out.</p><h3>Looking for more</h3><ul><li><a href="https://medium.com/joor-engineering/the-lost-art-of-writing-24265c7a489f">https://medium.com/joor-engineering/the-lost-art-of-writing-24265c7a489f</a></li><li><a href="https://www.goodreads.com/book/show/18077875-essentialism">https://www.goodreads.com/book/show/18077875-essentialism</a></li><li><a href="https://www.goodreads.com/en/book/show/29939161">https://www.goodreads.com/en/book/show/29939161</a></li></ul><h3>Bonus: what about those multipliers in the chart?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2Johj4D6SJ-fiXDu.jpg" /><figcaption>This is me every time somebody scrolls down and reads the article this far</figcaption></figure><p>You’re right.</p><p>I’ll be back with more writing about these <strong>multipliers factors</strong> since they are the key for senior people and the future of any engineering organisation. 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=358ba3d0f1dc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/joor-engineering/getting-back-to-basics-358ba3d0f1dc">Getting back to basics</a> was originally published in <a href="https://medium.com/joor-engineering">JOOR Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Theseus’s software engineering team]]></title>
            <link>https://medium.com/joor-engineering/theseuss-software-engineering-team-d5be2003d9f9?source=rss-1404c2ab5286------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5be2003d9f9</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[teams-and-teamwork]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Ivan Arrizabalaga Getino]]></dc:creator>
            <pubDate>Mon, 24 Apr 2023 09:23:51 GMT</pubDate>
            <atom:updated>2023-04-24T09:23:51.444Z</atom:updated>
            <content:encoded><![CDATA[<p>According to legend, <a href="https://en.wikipedia.org/wiki/Theseus">Theseus</a>, the mythical Greek founder-king of Athens, rescued the children of Athens from King <a href="https://en.wikipedia.org/wiki/Minos">Minos</a> after slaying the <a href="https://en.wikipedia.org/wiki/Minotaur">minotaur</a> and then escaped onto a ship going to <a href="https://en.wikipedia.org/wiki/Delos">Delos</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/0*M2zl3-6CbJdhnC-4.jpg" /><figcaption>A fresco from Pompeii depicting Theseus and Ariadne escaping from Crete.</figcaption></figure><p>Each year, the Athenians commemorated this by taking the ship on a pilgrimage to Delos to honor <a href="https://en.wikipedia.org/wiki/Apollo">Apollo</a>. A question was raised by ancient philosophers: After several centuries of maintenance, if each individual part of the Ship of Theseus was replaced, one at a time,<em> was it still the same ship?</em></p><p>Heraclitus, Plato, Plutarch and more recently Hobbes, Locke engaged into the talk bringing their thinking and perspective but there is simply no right answer.</p><p>Some say the physical components made the ship, other say the mission made the ship, other stick with the navigators… 🤷‍♂</p><p>As a director of engineering I question pretty much everything all the time:</p><ul><li>Is there are a better way of building software?</li><li>Are people learning and growing?</li><li>Are we picking the right battles?</li><li>…</li></ul><p>but there is a question that stands up among the others:</p><p><em>What turns a group of people into a team?</em></p><p>Surprisingly after 19 years in the industry I can’t give you a straight answer, I just barely developed the instincts to distinguish between a group of ticket eaters and a real team, let’s scratch the surface.</p><p><strong>Is the constitution?</strong></p><p>We can think that a team is simply made by people, just the names…but what about their circumstances? what about their motivations? what about the challenge they are facing?</p><p>The same group of people having great dynamics for a mission will fail miserably if the mission changes or simply stop behaving as they had because their own motivations change in time.</p><p><strong>Is the mission?</strong></p><p>Maybe a fixed mission determines the reality of a team, as long as the group chases one well defined goal in a windowed fraction of time the team remains…🤔</p><p>But the same group of people with a given name will face several challenges in a few months and as long as the dynamics stay around nobody would ever say those are different teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*OhPj6KtEK9Xpb2Myq46xyg.png" /><figcaption>Homer struggling to find foundational roots of a team</figcaption></figure><p><strong>Is the behaviour?</strong></p><p>Think about it…maybe the closest to reality? I agree.</p><p>A team is what the group does when there is a requisite gap, when production is down, when there is something to celebrate, when somebody gets blocked.</p><p>If you have a repetitive, foreseeable and desirable behaviour in all these and other circumstances you have a team.</p><p><strong>Why is any of this important?</strong></p><p>Team chemistry is everything.</p><p>If curious, you can look for “Team work”, “High productive teams” and things like that in <a href="https://www.researchgate.net/">https://www.researchgate.net/</a> or <a href="https://scholar.google.com/">https://scholar.google.com/</a> , the scientific evidences are clear.</p><p>Identifying desirable behaviours, praising them in public, bringing new people into them, reviewing and adapting your ways is the foundational aspect of team chemistry development.</p><p>Your quarter goals will change, your mission statement will change and your people, unfortunately, will change too but the culture, the identity of the group can remain if you take care of it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tleLk0eCBWDyaGztKkMt2A.png" /><figcaption>Some teammates with their video game background of the week</figcaption></figure><p>That’s why here in JOOR we praise behaviour such as Audrey’s focus to improve our pipelines through the storm or Melanie’s desire to unblock any teammate or Antonella’s instinct to document any decision or Paula’s eye to a identify a problem coming or, weird stuff like Alberto’s collection of Pope’s emojis, Omar &amp; Claudia’s themed backgrounds or Edu’s obsession to clap out of meetings.</p><p>In the end, a team is more than a list of names, technologies and projects, a team is a set of behaviours.</p><p><strong>Hiring?</strong></p><p>It depends on when you read this but mostly always yes 😎</p><p><a href="https://www.joor.com/current-openings">Current Openings | Careers at JOOR</a></p><p><strong>Reference</strong>:</p><p><a href="https://en.wikipedia.org/wiki/Ship_of_Theseus">https://en.wikipedia.org/wiki/Ship_of_Theseus</a></p><p><a href="https://www.researchgate.net/publication/236838989_Work_Team_Effectiveness_A_review_of_research_from_the_last_decade_1999-2009">https://www.researchgate.net/publication/236838989_Work_Team_Effectiveness_A_review_of_research_from_the_last_decade_1999-2009</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5be2003d9f9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/joor-engineering/theseuss-software-engineering-team-d5be2003d9f9">Theseus’s software engineering team</a> was originally published in <a href="https://medium.com/joor-engineering">JOOR Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The lost art of writing]]></title>
            <link>https://medium.com/joor-engineering/the-lost-art-of-writing-24265c7a489f?source=rss-1404c2ab5286------2</link>
            <guid isPermaLink="false">https://medium.com/p/24265c7a489f</guid>
            <category><![CDATA[soft-skills]]></category>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ivan Arrizabalaga Getino]]></dc:creator>
            <pubDate>Mon, 27 Feb 2023 11:33:27 GMT</pubDate>
            <atom:updated>2023-02-27T11:33:27.383Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>“Writing is the <strong>most underestimated skill</strong> in the software industry.”</blockquote><h3>A personal story from the early 2000&#39;s</h3><p>It was summer of 2006, maybe even 2005, when I started working in a data consulting company. I had been working there for just a few months and I was trying my best to show that I was ready to handle on my own a data visualisation project for a huge media company.</p><p>Spoiler, I <strong>couldn’t 🙈</strong>, at least in the beginning.</p><p>The team had only two members: Marc and I; Marc, an awesome guy, was in charge of diving into the data, looking for interesting metrics and setting the formulas to calculate them, I was in charge of turning that into real.</p><p>UX, ETL transformations, backend services, frontend navigation, deployments, infra requirements, documentation,… everything in 3 months.</p><p>So there I was, sat in a bus on my 5h 30min weekend trip from Madrid to Oviedo to see my family and girlfriend (now my wife 😉) with my head on fire trying to come up with a plan for all the problems I can’t figure out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/852/1*o3F-0o7TgYX8JL8nqoKhVg.png" /><figcaption>Madrid-Oviedo, still 5h 30min in 2023. 😒</figcaption></figure><p>I had been struggling for days at that point, trying my best to give some structure to the all the information I had, but it seemed like I just couldn’t make any sense of it.</p><p>Suddenly I had the simplest idea, I closed my laptop, <strong>took paper and pen</strong> and started writing all the different ingredients of the problem I had to solve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xqdschD--71sVnT_" /><figcaption>Photo by <a href="https://unsplash.com/@neonbrand?utm_source=medium&amp;utm_medium=referral">Kenny Eliason</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>The business goals, the expected user experience, the frequency of the calculus, the expected size of the problems, the dashboards, the widgets per dashboard, and then …after a couple of hours of just writing down the pieces something happened in my head.</p><blockquote>All of a sudden there was no puzzle.</blockquote><p>It was a clear system made of decoupled pieces, I didn’t have the implementation details yet but I couldn’t care less.</p><p>The whole problem was flushed out of my head into those pages and now that the structure is clear I knew <strong>the project was done even without a single line of code</strong>.</p><p>That was the first project I completed just by writing and I never stop doing that.</p><h3>Why underestimated?</h3><p>Ok, check the following questions and just think about them:</p><ul><li>Did you have a <strong>writing class</strong> while studying (college, bootcamp, …)?</li><li>Have you ever enrolled in a writing <strong>course</strong>?</li><li>Have you ever been requested to write something during a <strong>hiring</strong> process?</li><li>Has your <strong>organisation ever trained</strong> you to develop writing skills ?</li></ul><p>Now go through the same questions changing “<em>writing</em>“ for the most common suspects of our industry: the latest programming language, the latest agile practice, managing people, you name it, you got it.</p><p>The industry couldn’t care less about your ability to put your thoughts in order by writing them down and that’s a gigantic mistake.</p><h3>Why matters?</h3><p>Same exercise, let’s go through the following common activities on your daily routines:</p><ul><li>Capturing needs from customers.</li><li>Refining needs from product.</li><li>Explaining technical options and architecture decisions.</li><li>Documenting acceptance criteria.</li><li>Define contracts or tests (BDD).</li><li>Consolidating and sharing technical knowledge.</li><li>Improving onboarding experiences in a remote world.</li><li>Working async.</li><li>Or simply, finding the right words in slack.</li></ul><p>Do you see it now? One more.</p><ul><li>Programming</li></ul><p>In the end, programming might be the <strong>final boss of writing</strong>, just a different taste of the same exercise which sits on top of your technical skills, previous experiences, and mental processes.</p><p>Your writing skills help you get your code organised and turn weird commands and algorithms into a comprehensive story.</p><h3>What about writing at JOOR?</h3><p><a href="https://en.wikipedia.org/wiki/Johannes_Gutenberg">Gutenberg</a> would be proud of us, 😅.</p><p>Slowly, the last months, we have introduced some changes to benefit from all the goodness of writing:</p><ul><li>A better Confluence with a known structure to navigate information.</li><li>Basic intro articles to explain the main domains of the platform.</li><li>Written ARBs (architecture review boards) for reviewing meaningful architecture decisions.</li><li>Structured async updates on slack to help work-life balance.</li><li>…</li></ul><h3>What’s next?</h3><p>It’s just a process, none of the previous stuff is perfect, but we have already tasted the goodness of getting better at writing and we have some ideas to go further.</p><p>What if we ask you to write a short tale on your next interview for a role at JOOR?</p><p>What if we ask our engineering team to complete a writing course this year rather than finishing another Kubernetes intro in Udemy?</p><p>What if we started sharing learnings, failures and experiences more often here? Yep, definitely we will do that 😉.</p><h3>Looking for more?</h3><ul><li><a href="https://benmccormick.org/2019/03/01/190000.html">https://benmccormick.org/2019/03/01/190000.html</a></li><li><a href="https://stackoverflow.blog/2021/08/09/how-writing-can-advance-your-career-as-a-developer/">https://stackoverflow.blog/2021/08/09/how-writing-can-advance-your-career-as-a-developer/</a></li><li><a href="https://blog.codinghorror.com/is-writing-more-important-than-programming/">https://blog.codinghorror.com/is-writing-more-important-than-programming/</a></li><li><a href="https://betterprogramming.pub/why-every-developer-needs-to-learn-to-write-better-d5974e38e64c">https://betterprogramming.pub/why-every-developer-needs-to-learn-to-write-better-d5974e38e64c</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24265c7a489f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/joor-engineering/the-lost-art-of-writing-24265c7a489f">The lost art of writing</a> was originally published in <a href="https://medium.com/joor-engineering">JOOR Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Los veranos del informático]]></title>
            <link>https://medium.com/@ivanarrizabalagagetino/17-a%C3%B1os-trabajando-y-en-verano-siempre-tengo-la-misma-rutina-323d8a11f7d?source=rss-1404c2ab5286------2</link>
            <guid isPermaLink="false">https://medium.com/p/323d8a11f7d</guid>
            <dc:creator><![CDATA[Ivan Arrizabalaga Getino]]></dc:creator>
            <pubDate>Thu, 08 Jul 2021 13:41:23 GMT</pubDate>
            <atom:updated>2021-07-08T13:45:06.362Z</atom:updated>
            <content:encoded><![CDATA[<p>17 años trabajando y en verano siempre tengo la misma rutina.</p><p>No es nada planificado, pero siempre acabo metiéndome más a fondo en alguna tecnología o repasando cosas básicas.</p><p>Asi tirando de memoria...</p><ul><li>2005: patrones, plugins de eclipse, swt.</li><li>2006: spring</li><li>2007: librerías Ajax (prototype, scriptacoulous)</li><li>2008: agile, técnicas de comunicación</li><li>2009: python</li><li>2010: algoritmos de inteligencia colectiva (asi llamaban al ML entonces)</li><li>2011: PNL, comunicación, Photoshop</li><li>2012: lenguajes dinámicos (groovy, grails, griffon)</li><li>2013: certificaciones Mongo, aws, android</li><li>2015: angularjs, ionic</li><li>2018: nlp, bots</li><li>2019: fastai (mucho menos de lo q me hubiera gustado, volveré)</li><li>2020: ddd, docker, kubernetes</li><li>2021: mas ddd, arquitectura, rails</li></ul><p><strong>Y ¿qué?</strong></p><p>La lista no vale para nada, siempre tendré la duda de si debería haberme centrado en <strong>1 o 2 cosas</strong> en vez de tirarme a aprender un poco de todo pero creo que me he divertido mas así.</p><p>Comparto porque varias veces me he visto bloqueado pensando que deberia saber más de x.</p><p>X era mejor para mi trabajo, pero me apetecía hacer el chorras con otra cosa nueva.</p><p>No pasa nada, lo que sea estará bien.</p><p>Si lo que te apetece es <strong>NO hacer</strong> ni leer nada, también estará bien.</p><p>Cada uno tiene sus tiempos, y cada tiempo es diferente para cada uno, me ha costado, pero con los años he dejado de fruncir el ceño por esto y estoy más cómodo con mi rol de <em>aprendedor</em> incansable en anchura.</p><p><strong>Y ¿ahora?</strong></p><p>Lo que venga, las tecnologías vienen, van ...vuelven con otro nombre, los fundamentos son siempre los mismos, no cambian con o sin <a href="https://copilot.github.com/">copilot.</a></p><p>Disfruta el verano, disfruta lo que venga.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=323d8a11f7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[30/12/17: Y ahora que?]]></title>
            <link>https://medium.com/@ivanarrizabalagagetino/30-12-17-y-ahora-que-71eba1614b1f?source=rss-1404c2ab5286------2</link>
            <guid isPermaLink="false">https://medium.com/p/71eba1614b1f</guid>
            <category><![CDATA[zapiens]]></category>
            <category><![CDATA[life]]></category>
            <dc:creator><![CDATA[Ivan Arrizabalaga Getino]]></dc:creator>
            <pubDate>Sat, 30 Dec 2017 21:56:21 GMT</pubDate>
            <atom:updated>2017-12-30T21:58:19.237Z</atom:updated>
            <content:encoded><![CDATA[<p>30/12/17: Y ahora que?</p><p>Escribo esto desde el móvil, la noche antes de fin de año. Mis hijos acaban de decir a gritos no se qué sobre un “campo de fuerza” así que no cabe duda están felices, nadie habla de campos de fuerza triste, y menos si tienes 9 y 6 años.</p><p>Yo estoy bien, ya sabes, pero no cabe duda de que acabar un año tan difícil, en muchos sentidos, como el 2017 me hace sentir lo suficientemente raro como para escribir esto del tirón.</p><p>El 2017 fue el año en que Blunder evolucionó a Zapiens y, en lo profesional, fue también el año en el que descubrimos que, como le pasaba a Sir William Wallace, lo que nuestro pequeño Brainteam más ama es su propia libertad.</p><p>En las próximas semanas acabaremos la primera versión de Zapiens y en este sentido tengo la fortuna de trabajar con unos seres humanos únicos, honestos e inteligentes que sólo se merecen lo mejor. 2018 queremos que sea, como diría Barney Stinson “Legen… wait for It … dary&quot;.</p><p>Pero la vida es muchísimo más que aquello que te da de comer. Es lo que sientes, lo que piensas, lo que callas y sobretodo aquello que no controlas.</p><p>Quienes me conocen ya lo saben, en 2017 mi madre murió de cáncer. No hubo batalla, fue una paliza y por muy listo que a veces me crea lo único que pude hacer fue estar ahí y joderme.</p><p>Acabo, no controlamos una mierda de las cosas que nos pasan. Así que, hagas lo que hagas no dejes de hacer aquello que te haga feliz.</p><p>Aprovecha para estar con quién quieres, trabajar con quién quieres y si, como yo, tienes sueños lucha por ellos con todo lo que tengas.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=71eba1614b1f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>