<?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 Tadeu Sarro on Medium]]></title>
        <description><![CDATA[Stories by Tadeu Sarro on Medium]]></description>
        <link>https://medium.com/@tadeusarro?source=rss-39cd7ffcdfc8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*a6JBXenpo7JWsoLX</url>
            <title>Stories by Tadeu Sarro on Medium</title>
            <link>https://medium.com/@tadeusarro?source=rss-39cd7ffcdfc8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 23:32:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tadeusarro/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[HTMX, the basics]]></title>
            <link>https://medium.com/@tadeusarro/htmx-the-basics-65a00f2045f9?source=rss-39cd7ffcdfc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/65a00f2045f9</guid>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[htmx]]></category>
            <dc:creator><![CDATA[Tadeu Sarro]]></dc:creator>
            <pubDate>Sat, 03 Feb 2024 15:22:15 GMT</pubDate>
            <atom:updated>2024-02-03T15:22:15.292Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello guys!</p><p>Today I’d like to talk about <a href="https://htmx.org/">HTMX</a>. You might not have heard about it, but it’s creating quite a fuss in social media.</p><p>On one hand, some people are religiously defending it as the next disruptive thing in web development while other guys say it’s nothing but a meme.</p><p>So, I’ll leave this feud aside and assume it’s pretty much like everything else in programming: It’ll have its strengths and weaknesses.</p><p>Instead, I’ll focus on what it is, what’s good at, and how to use it within your Ruby on Rails application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/509/1*cPqRCnwoO2sQaO6b9f75FQ.jpeg" /></figure><h3>What is HTMX?</h3><p>It’s a <strong>dependency-free</strong>, <strong>browser-oriented JavaScript library</strong> that provides a powerful set of tools for building dynamic and interactive web applications using plain HTML.</p><p>It has some key things:</p><p><strong>It’s focused on HTML</strong>, it emphasizes using HTML attributes and data attributes to define the behavior of your web application.</p><p><strong>It has server-side integration</strong>, meaning that you won’t have to write extensive JS scripts to connect to your server.</p><p><strong>It allows partial updates</strong> without the need to reload the full page, leading to a better user experience.</p><p><strong>Supports animations and transitions </strong>making your web pages more appealing.</p><p><strong>It’s relatively easy to learn</strong>, which favors inexperienced developers and allows you to avoid larger frameworks.</p><h3>The downside of HTMX</h3><p>Well, life is not all sunshine and rainbows, and there are some potential drawbacks, we might consider…</p><p>Learning curve: Besides being relatively simple, it still brings a new paradigm to web development, so at least some practice would be required.</p><p>State management: It’s much weaker than React or Vue for instance when it comes to state management, so if your application is getting too big, it will not be the best tool.</p><p>Limited client-side control: As stated, it focuses on server-driven updates, which limits the ability to perform complex logic directly into the browser.</p><p>Smaller community: It has a smaller community when compared to popular frameworks, which might make it difficult to find support, resources, and whatnot.</p><p>Not everything is HTML: White HTML is the focus some functionalities might require JS libraries, introducing some dependencies.</p><h3>How to use it with Rails?</h3><p>We need to <a href="https://htmx.org/docs/#installing">install it</a>.</p><p>So inside our controller we:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/574/1*NTITR7SJrodubeeF858xBw.png" /><figcaption>app/controllers/expenses_controller.rb</figcaption></figure><p>Our views:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/519/1*qmGcrjjKuKIrk0MLN0eTxw.png" /><figcaption>app/views/expenses/index.html.erb</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/524/1*GfVHM_TkwisAwGdVlqbcuw.png" /><figcaption>app/views/expenses/show.html.erb</figcaption></figure><p>As a result, we now can issue AJAX requests:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/454/1*Uu249XMvGkVDZvgXpXRo7Q.png" /><figcaption>Expenses Index</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/455/1*6mE3D7RFYVWeBksn4Sp_ew.png" /><figcaption>First Expense Show</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/455/1*1ageNUXh-TFYt4hhDGRgfQ.png" /><figcaption>Third Expense Show</figcaption></figure><p>And there you go, we can visit each expense and come back, and notice that our URL doesn’t change. :)</p><h3>Conclusion</h3><p>What I liked the most was that it took me 20 minutes from running rails new to taking these screenshots, and I have never used HTMX before. So it’s pretty easy to use.</p><p>As for my opinion, I’d say it’s pretty good when it comes to smaller and simpler applications, or maybe if you’re working solo on a project. As it’s easy to use/ learn and allows you to create appealing interfaces.</p><p>But as the complexity of the application grows, some other tools are gonna be needed…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65a00f2045f9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good Practices on Manual Deployment]]></title>
            <link>https://medium.com/@tadeusarro/good-practices-on-manual-deployment-ed29c58aad7a?source=rss-39cd7ffcdfc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed29c58aad7a</guid>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[capistrano]]></category>
            <dc:creator><![CDATA[Tadeu Sarro]]></dc:creator>
            <pubDate>Tue, 02 Jan 2024 21:17:39 GMT</pubDate>
            <atom:updated>2024-01-02T21:17:39.764Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello guys. :)</p><p>Today I’d like to talk a little bit about the deployment process. Quite recently I made a small mistake while releasing (which I promptly fixed), and that gave me the idea to write this down.</p><p>I believe automatic deployment has become “the usual way” of doing this, but manual deployment has its advantages/ disadvantages.</p><p>So we’re gonna talk about some of these pros and cons, and also some best practices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*cdDzNgJPiIDGx5KzjabFYQ.gif" /></figure><h3>Why manual deployment?</h3><p>Hands down, it’ll give you a much better perspective on how every bit of an application works to make it all come together. So I’d say that’s the biggest advantage, if something goes south you’re much better prepared for a response.</p><p>That leads to another very good aspect, doing things manually will allow the developer to have a better understanding of the application, watching for improvement opportunities before they become critical.</p><p>Another thing to consider is the context in which this application exists, automatic deployment might not be the best strategy if your team is small, or if the application is rarely released, or even if you don’t have that many resources available.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/967/1*51B0VMDzgJ8yY6zlqVGOFw.png" /></figure><h3>How to manually deploy?</h3><p>Ok, so I decided to keep things simple and deploy it manually, how do I do that? There are some good practices that we can follow:</p><ol><li>Version Control: It’s fundamental to have a contingency plan for when things don’t work as planned and we need to roll back the changes, using tools like Git might help you with that.</li><li>Backups: Take backups of your production environment, it’s a solid way of recovering from disasters in case all data is lost.</li><li>Create a Checklist: Very good for reducing human errors, bonus points if it comes with troubleshooting on usual problems people might face.</li><li>Configuration Management: Sharing the same configuration across environments will help detect and prevent failures when they could be disastrous.</li></ol><h3>Conclusion</h3><p>It’s not written in stone, so it will vary depending on the context in which you are involved… If you want your developers to have more control over a versatile and flexible process, then manual deployment is the way to go.</p><p>And as for me, I’m using <a href="https://en.wikipedia.org/wiki/Capistrano_(software)">Capistrano</a> to make deploys, it’s “a framework for building automated deployment scripts”. You can check <a href="https://github.com/capistrano/capistrano">their repository out</a>.</p><p>Maybe I’ll write something about automating a deployment process with Capistrano and GitHub Actions next... Take care, everybody!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed29c58aad7a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A short introduction to task estimation]]></title>
            <link>https://medium.com/@tadeusarro/a-short-introduction-to-task-estimation-bfc3f0b3e704?source=rss-39cd7ffcdfc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfc3f0b3e704</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[task-estimation]]></category>
            <dc:creator><![CDATA[Tadeu Sarro]]></dc:creator>
            <pubDate>Mon, 31 Jul 2023 21:56:22 GMT</pubDate>
            <atom:updated>2023-07-31T21:56:22.111Z</atom:updated>
            <content:encoded><![CDATA[<p>These days agile methodologies are quite popular, and estimating your efforts is a core activity for any professional in this context. And it doesn’t matter if you are a scrum master or a software developer, you might profit from it.</p><p>And while, it’s usually a team effort activity, in my daily routine I use to plan my tasks by myself. So I’ll try and focus my writing on solo task estimation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/615/1*aUWEgJz8CwO7BQBQa0wjHw.gif" /></figure><h3>What is it?</h3><p>Task estimation is the process of determining the effort, time, and resources to complete a given task. In an agile environment, it would mean breaking down tasks into smaller and more manageable sub-tasks.</p><h3>The Importance of estimating your tasks</h3><p>As potential benefits, we could point out some things such as better planning of the sprints, improved resource allocation, consistency in delivering new features, and identifying and preventing bottlenecks.</p><h3>Task estimation techniques</h3><ol><li>Planning Poker: So it’s a game and the players (team members) collectively estimate each task by assigning points based on complexity, effort, and risk. It’s meant to be used by a group, and then there is <a href="https://planningpokeronline.com/">this tool</a>.</li><li>Bucket System: Also known as “T-shirt sizing”. The idea is to categorize the tasks into “buckets”, where each bucket represents a range of effort and complexity. It’s good when precision is not required.</li><li>Relative Estimation: The team members compare one task to another, assessing their relative complexity and effort. It’s good when you need to establish priorities.</li></ol><h3>Best Practices</h3><p>Task estimation is much better when you have different perspectives, which reinforces the advantages of making a team effort out of it. Also comparing the current task to previous tasks makes it easier to learn what went wrong previously and makes it more relative.</p><p>And remember, it’s a continuous improvement activity.</p><h3>Solo Estimation challenges</h3><p>It’s not impossible to estimate your tasks alone, the only problem is that you might have a limited perspective on a given task, which then will lead to inaccurate estimation because some part of it was misunderstood or even unacknowledged.</p><p>I hope I’ve shown how important task estimation is in an Agile environment. And if you’re doing it by yourself, remember to rely on historical data, use relative sizing and seek external input.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*zylAHkLzh5QrUJKea71v0w.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfc3f0b3e704" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rails, Sidekiq, and Redis]]></title>
            <link>https://medium.com/@tadeusarro/rails-sidekiq-and-redis-f661f8ae60ab?source=rss-39cd7ffcdfc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f661f8ae60ab</guid>
            <category><![CDATA[sidekiq]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <category><![CDATA[redis]]></category>
            <dc:creator><![CDATA[Tadeu Sarro]]></dc:creator>
            <pubDate>Tue, 20 Jun 2023 19:48:58 GMT</pubDate>
            <atom:updated>2023-06-20T19:48:58.817Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello everybody, today we’re gonna talk a little bit about Sidekiq, how it depends on Redis, and how it’s all connected via Ruby on Rails.</p><p>Ruby on Rails is a web development framework, it follows the MVC architectural pattern and provides developers with a set of conventions that streamline the development process. Rails incorporate a range of tools and libraries, <a href="https://github.com/sidekiq/sidekiq">one of which is Sidekiq</a>.</p><p>And what is Sidekiq?</p><figure><img alt="Sidekiq" src="https://cdn-images-1.medium.com/max/1024/1*Mn6sxtcBdfjRrd6iTFNjVQ.png" /></figure><p><a href="https://sidekiq.org/">Sidekiq</a> is a background processing library for Ruby. It allows you to offload time-consuming or resource-intensive tasks to background workers, ensuring that your application remains responsive and scalable. Sidekiq relies on Redis as its message broker and for managing the job queue.</p><p>And what is Redis?</p><figure><img alt="Redis" src="https://cdn-images-1.medium.com/max/1024/1*7VHGduVKWxANKMed_cfMaQ.png" /></figure><p><a href="https://redis.io/">Redis</a> is an open-source, in-memory data structure store that provides fast and efficient data storage and retrieval. It acts as the communication layer between the Rails application and the Sidekiq workers, facilitating the transfer of jobs and job-related data.</p><p>To summarize:</p><ol><li>The Ruby on Rails application enqueues jobs to Sidekiq using Sidekiq’s API. This involves pushing jobs onto a Redis list.</li><li>Sidekiq, which is running as a separate process, continuously monitors the Redis list for new jobs.</li><li>When Sidekiq detects a new job in the Redis list, it dequeues the job and assigns it to an available worker for processing.</li><li>The worker retrieves the job data and performs the necessary computations or tasks defined within the job’s perform method.</li><li>During job execution, the worker may interact with external resources such as databases, APIs, or other services.</li><li>Upon job completion, the worker updates the job status, and if configured, may store the job’s result or any relevant metadata in Redis.</li></ol><p>By leveraging Redis, Sidekiq achieves efficient job processing and communication within Ruby on Rails applications. Redis’s in-memory nature provides fast data access, and its data structures enable Sidekiq to implement robust job queue management, concurrency control, and job tracking functionalities.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f661f8ae60ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Rails World and more]]></title>
            <link>https://medium.com/@tadeusarro/rails-world-and-more-5f6ed837ea3e?source=rss-39cd7ffcdfc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/5f6ed837ea3e</guid>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <dc:creator><![CDATA[Tadeu Sarro]]></dc:creator>
            <pubDate>Tue, 02 May 2023 21:41:12 GMT</pubDate>
            <atom:updated>2023-05-02T21:41:12.044Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello guys! Welcome back to our monthly journal on the Ruby and Rails universe.</p><h3>Ruby World is coming!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/755/1*jzaWKVij5NhYcrUjfIcY-w.png" /></figure><p>Amsterdam is gonna host the first-ever <a href="https://rubyonrails.org/2023/4/6/rails-world-is-coming">Rails Foundation conference</a>. It’s gonna happen on October 5 &amp; 6. The conference will feature technical talks, demos, workshops, networking, and keynotes. A limited number of early bird tickets will be available, so check it out!</p><h3>Secure Device CLI Support</h3><p>Now you can use your registered secure device as a multi-factor authentication method on the RubyGems CLI. Available from RubyGems 3.4.12. You can read about it <a href="https://blog.rubygems.org/2023/04/11/security-device-cli-support.html">on the blog</a> and also <a href="https://guides.rubygems.org/setting-up-multifactor-authentication/">in the guides</a>.</p><h3>Ruby 3.2.2</h3><p><a href="https://www.ruby-lang.org/en/news/2023/03/30/ruby-3-2-2-released/">Ruby 3.2.2 has been released</a> and with it some <a href="https://en.wikipedia.org/wiki/ReDoS">ReDoS</a> fixes. The problem was that the URI and Time parsers would mishandle strings with specific characters, leading to an increase in execution time.</p><h3>Better Features Specifications</h3><p>I have found <a href="https://remimercier.com/how-to-write-better-specifications/">this very interesting article</a> about creating a template that would work as a guide for describing and documenting tasks in an agile environment. It’s totally worth checking out!</p><h3>Challenges of a Jr. RoR Dev</h3><p><a href="https://dev.to/makisushi/challenges-of-a-junior-ruby-developer-24f0">This is another cool article</a>, whether you’re an unseasoned ruby developer, or even a tech/ squad leader searching for a new talent for your team. It will go through some concepts that a junior RoR should know about when it comes to a job interview.</p><h3>5 Tips to Optimize an RoR Application</h3><p>Speaking of cool articles, I think <a href="https://dev.to/ahmadraza/5-tips-to-optimize-your-ruby-on-rails-apps-performance-248a">this one</a> is very useful. Not because it states revolutionary stuff, but actually because it remembers me of simple best practices that we can follow, and that causes a huge impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/1*6GfiXJyZtuR6iK1dnPdXYw.gif" /></figure><p>That’s all we have for this edition. I hope you have liked it, and if you did, don’t forget to like it! See you all next month, take care!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f6ed837ea3e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ruby turns 30 and more]]></title>
            <link>https://medium.com/@tadeusarro/ruby-turns-30-and-more-ec7dfe481808?source=rss-39cd7ffcdfc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec7dfe481808</guid>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <dc:creator><![CDATA[Tadeu Sarro]]></dc:creator>
            <pubDate>Sun, 02 Apr 2023 22:09:24 GMT</pubDate>
            <atom:updated>2023-04-02T22:11:16.393Z</atom:updated>
            <content:encoded><![CDATA[<p>Alright everybody, welcome to march’s article about Ruby’s news. My name is Tadeu and I’m gonna summarize the stuff that recently caught my attention the most on the <em>rubyist</em> world!</p><h3>Happy birthday!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/623/1*C1KftMNlOJZl9_qcnBMBuQ.png" /></figure><p>Thirty years ago Ruby was conceived by Yukihiro Matsumoto — even though the first release was in 1995 with version 0.95. If you don’t know much about its history you might wanna check <a href="https://www.ruby-lang.org/en/about/">this</a>, <a href="https://developer.oracle.com/learn/technical-articles/what-is-ruby#:~:text=it%20in%20Ruby.-,Where%20Ruby%20Came%20From%3F,Smalltalk%2C%20Lisp%2C%20and%20Ada.">this</a>, and <a href="https://en.wikipedia.org/wiki/Ruby_(programming_language)">this</a> out.</p><h3>VS Code and Ruby</h3><p><a href="https://code.visualstudio.com/docs/languages/ruby">VS Code</a> now has official support for Ruby. You can check the Ruby LSP extension on the official <a href="https://marketplace.visualstudio.com/items?itemName=Shopify.ruby-lsp&amp;ssr=false#overview">Microsoft marketplace</a>. It was released this month and already has over 100k installs!</p><h3>Not installed gems support</h3><p>You can now use the gem exec command to run executables from gems that might or not be installed into your application. <a href="https://github.com/rubygems/rubygems/pull/6309">This is the PR</a> with the merge of the feature.</p><h3>Rails 7.0.4.3 and 6.1.7.3</h3><p>Both of these are security releases, with fixes for <a href="https://en.wikipedia.org/wiki/Cross-site_scripting">Cross-site scripting</a>. And as explained in the official <a href="https://rubyonrails.org/2023/3/13/Rails-7-0-4-3-and-6-1-7-3-have-been-released">RoR blog</a>, even though these vulnerabilities are not considered high-risk, it is still recommended to upgrade to the latest versions ASAP.</p><h3>Improved namespace support</h3><p>Rails 7.1 has improved support for custom namespaces, in short, we can do it in classicon zeitwerk mode. You can check <a href="https://blog.saeloun.com/2023/03/28/improve-support-for-namespaces">this article out</a> and the <a href="https://github.com/rails/rails/pull/47583">PR on the Rails repo</a>.</p><h3>Search algorithms</h3><p>At last but not least, I have found <a href="https://dev.to/daviducolo/search-algorithms-in-ruby-3nbj">this article </a>about searching algorithms using Ruby. This topic is not very advanced but I reckon it’s the kind of stuff always worth to be checking out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*jLQMDBDJr49oIpy6LZpdIA.gif" /></figure><p>That was it for this month, of course, there is a lot of stuff more out there about Ruby and Rails, but the idea is to make it nice and quick to read.<br>And don’t forget, pet the pets, drink water, and be kind. See you next month!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec7dfe481808" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ruby on Rails sources on the internet]]></title>
            <link>https://medium.com/@tadeusarro/ruby-on-rails-sources-on-the-internet-fda3030aca0e?source=rss-39cd7ffcdfc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/fda3030aca0e</guid>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[ruby-on-rails]]></category>
            <dc:creator><![CDATA[Tadeu Sarro]]></dc:creator>
            <pubDate>Mon, 27 Feb 2023 14:24:04 GMT</pubDate>
            <atom:updated>2023-02-27T14:24:04.158Z</atom:updated>
            <content:encoded><![CDATA[<p>Alright, so long story short, I’ve been working with RoR for a couple of years now, and I feel like I should be more involved within the Ruby/ Rails community. So, the idea is to choose a couple of sources, gather the stuff that I like the most, and write down a monthly article.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*JYraHT0Xsj854y5z5fDHJg.png" /></figure><p>And for the first edition, I’ve decided to choose the sources and explain a little bit about them.</p><h3>Ruby Weekly</h3><p><a href="https://rubyweekly.com/">Ruby Weekly</a> is a newsletter so up front that’s an advantage. Plus you can browse through the editions, which might be handy for writing monthly articles.</p><h3>Official RoR blog</h3><p>I couldn’t leave the <a href="https://rubyonrails.org/blog/">official RoR blog</a> out of this list. Usually, it doesn’t take a week for its content to be updated, and the posts are made by active contributors of the Rails project. Their posts include a comprehensive collection of how-to, tips, and guides</p><h3>Ruby Flow</h3><p><a href="https://rubyflow.com/">This is a global RoR community</a>. Usually, it’s updated with news, concepts, tips, and tricks, but also covers more general coding and testing topics. The link log gathers RoR-related data from all over the web and brings you the most relevant content.</p><h3>Rubyland</h3><p><a href="http://rubyland.news/">Rubyland</a> is a platform you need to visit if you’re an RoR dev. They offer in-depth, easy-to-read, and effective guides on everything related to Ruby on Rails. They even take <a href="https://www.akitaonrails.com/">Fabio Akita</a> (a renowned Brazilian RoR developer) as a source.</p><h3>RoR - Dev Community</h3><p><a href="https://dev.to/">Dev.to</a> is a social network for software developers, where you can find technical articles, posts, and tutorials with code examples. Ruby on Rails framework has its <a href="https://dev.to/t/rails">own section.</a></p><p>So, that was it for this edition, I’ve tried to keep it as succinct as I could. Please take it with a grain of salt, I’m just a simple junior RoR developer, on the to learn the most that I can.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*Tc8kHnCUA6h9tRTk3zET9Q.gif" /></figure><p>See you all next month!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fda3030aca0e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to use the 5S technique in software development]]></title>
            <link>https://medium.com/@tadeusarro/how-to-use-the-5s-technique-in-software-development-962f4b9cc4ca?source=rss-39cd7ffcdfc8------2</link>
            <guid isPermaLink="false">https://medium.com/p/962f4b9cc4ca</guid>
            <dc:creator><![CDATA[Tadeu Sarro]]></dc:creator>
            <pubDate>Thu, 18 Jun 2020 22:03:47 GMT</pubDate>
            <atom:updated>2020-06-18T22:03:47.018Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I4-o0GucjLmSzPnphFKvhA.jpeg" /></figure><p>Hello, children all over the world. In today’s class, we’re going to talk about the importance of keeping your code/ script well organized and tidy. Please take it with a grain of salt, I don’t believe there is right or wrong in development.</p><p>In particular, I’d like to talk about a Japanese technique called 5S. In short, it consists of five “ways” that help to create an organized work environment that pursues effectiveness and efficiency. Those are:</p><p>Seiri, Seiton, Seisō, Seiketsu &amp; Shitsuke.</p><p>Ok, so far so good “but does it have to do with software development” you might ask me, and I’m glad if you did. In my personal opinion, it seems that this tool might be very useful if applied in software development.</p><h3>Seiri</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*XPD5JiZYwfob22ui" /></figure><p>Seiri means sorting through all items in a location and removing all unnecessary items.</p><p>Not to mention all of those W3schools, MDN and Stackoverflow tabs opened about one and half hour ago, that are still open even though not being used, let’s focus on actual development.</p><p>In front-end development, one thing that leaves a mark on is the planning ahead. In the image below we can see there are some unnecessary lines of code there, which could have been avoided if the display properties of the &lt;p&gt; and &lt;span&gt; tags would have been understood.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/555/0*dN5KhBlRkL1ydm_c" /></figure><h3>Seiton</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/479/0*uLc0DSkknNmK_sIv" /></figure><p>Seiton means putting all necessary items in the optimal place for fulfilling their function.</p><p>In this matter, I can’t help but think about grouping information that is related together. In really big projects this can make a huge difference, in terms of maintaining the code.</p><p>Let’s think about CSS for instance, in the image below, we can see in the left example that the information is not grouped, in the example to the right it’s grouped and commented.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/812/0*f4f0F6OIoKloko-q" /></figure><p>In the back-end, a persistent example is class declaration, when doing so it’s important to try and keep pertinent information grouped together. As we can see in the example beneath.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/386/0*VfwFbj0NM9NVcRY4" /></figure><h3>Seiso</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*LJxqTk98ESDRRcCH" /></figure><p>Seiso is to clean and inspect the workplace, tools, and machinery on a regular basis.</p><p>By my personal experience, rushing through a project is probably leading to a whole bunch of bugs, and that later on can be quite troublesome to be fixed. While developing an application, inspecting the script with tools such as <a href="https://en.wikipedia.org/wiki/Lint_(software)">linters</a> and <a href="https://validator.w3.org/#validate_by_input">code validators</a> can be very helpful to assure a certain level of reliability on the expected output.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1008/0*1ujbZPt-SRmP6zXZ" /></figure><p>Another approach to this would be the so-called <a href="https://en.wikipedia.org/wiki/Test-driven_development">Test-driven Development</a>. As described:</p><blockquote><em>Relies on the repetition of a very short development cycle, in which requirements are turned into very specific, test cases then the code is improved so that the tests pass.</em></blockquote><h3>Seiketsu</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*fWKuZPMmhzTSjOW2" /></figure><p>Seiketsu is to standardize the processes used to sort, order, and clean the workplace.</p><p>I reckon this is probably one of the most relevant topics in software development, especially when working remotely. The importance of creating standards can be identified in many different aspects. Probably you have already heard of <a href="https://en.wikipedia.org/wiki/World_Wide_Web_Consortium">World Wide Web Consortium</a> and <a href="https://en.wikipedia.org/wiki/Camel_case">Camel Case</a>.</p><p>Let’s bring this subject to a development example. In the image below it’s quite tricky to understand the parent/ child relation between those elements, that could be easily avoided using appropriate indentation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G21CHyCN5bsk7TA0" /></figure><h3>Shitsuke</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*yyw4vpsrfAPn8wDr" /></figure><p>Shitsuke is to sustain the developed processes by self-discipline.</p><p>This one is the hardest to exemplify, it means to create and develop the habitude, in everyone who’s involved in the project, to practice what’s being told in the previous steps. In remote working maybe it’s the toughest to achieve since we’re dealing with people of many different cultures and backgrounds.</p><h3>To sum up</h3><p>Of course, these principles can be used in many other examples, not only in the professional sphere but also in personal and academic. As I’ve said before, I believe there’s no right or wrong in software development. What we can rely on are good practices and, in my opinion, using 5S can be very helpful in accomplishing those.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=962f4b9cc4ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>