<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Michael Machado</title>
    <description>The latest articles on DEV Community by Michael Machado (@machadomichael).</description>
    <link>https://dev.to/machadomichael</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1219773%2Fc38233b4-b9db-4bea-9a2f-f3cf5fcfeeef.jpeg</url>
      <title>DEV Community: Michael Machado</title>
      <link>https://dev.to/machadomichael</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/machadomichael"/>
    <language>en</language>
    <item>
      <title>Organize your team, project and life.</title>
      <dc:creator>Michael Machado</dc:creator>
      <pubDate>Sat, 27 Jun 2026 20:54:45 +0000</pubDate>
      <link>https://dev.to/machadomichael/organize-your-team-project-and-life-lgf</link>
      <guid>https://dev.to/machadomichael/organize-your-team-project-and-life-lgf</guid>
      <description>&lt;p&gt;I'm working on my postgraduate of Software Engineering on PUC-RJ and I have noticed that I should be more effective just organizing my company properly.&lt;/p&gt;

&lt;p&gt;Devtype is a three people company, as we have a short team, we have tried to avoid overwhelming the workflow. However after some projects we added Jira to manage the project, we created a weekly and now I want to do something kind a lean inception.&lt;/p&gt;

&lt;p&gt;Our workflow is I sharing my screen and using the &lt;a href="https://excalidraw.com" rel="noopener noreferrer"&gt;Excalidraw&lt;/a&gt; I create some diagrams to represent the system architecture. But I feel that is a mistake. I believe that we should to get the customer requires and chat about it, create a lean inception before starting draw class diagrams or the architecture.  &lt;/p&gt;

&lt;p&gt;After we have defined tasks, deadlines the things begins to run faster and better. The time spent chatting, defining, drawing is a shortcut to reach the MVP. And believe me, you need to reach the MVP, because before it everything is just an idea or a dream.&lt;/p&gt;

&lt;p&gt;Another tip. Create support tools to improve your efficiency. We have toolkit for backend basic requirements like database connection, AWS integration, queue consumer/producer, logs, cryptography and any other thing that you will use in more than one application.&lt;/p&gt;

&lt;p&gt;In addition to that I have packages for bank integration, authentication, WhatsApp integration and more. These packages/tools turn the development really easy and you will have a pattern and it increase the maintainability.&lt;/p&gt;

&lt;p&gt;The challenge is to create something functional and organized without stiffening the workflow.&lt;/p&gt;

</description>
      <category>startup</category>
      <category>workplace</category>
      <category>software</category>
    </item>
  </channel>
</rss>
