<?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 Rares Golea on Medium]]></title>
        <description><![CDATA[Stories by Rares Golea on Medium]]></description>
        <link>https://medium.com/@rgolea?source=rss-ae2c7d70a2e5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*NlhsV5RTwiU6nH4O</url>
            <title>Stories by Rares Golea on Medium</title>
            <link>https://medium.com/@rgolea?source=rss-ae2c7d70a2e5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 17:18:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rgolea/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[New to Enterprise Application Architecture?]]></title>
            <link>https://medium.com/@rgolea/new-to-enterprise-application-architecture-9b4858028eb7?source=rss-ae2c7d70a2e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b4858028eb7</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[enterprise-architecture]]></category>
            <category><![CDATA[application-development]]></category>
            <dc:creator><![CDATA[Rares Golea]]></dc:creator>
            <pubDate>Thu, 07 May 2020 10:53:24 GMT</pubDate>
            <atom:updated>2020-05-07T10:53:24.258Z</atom:updated>
            <content:encoded><![CDATA[<h4>A beginner’s guide to start planning your application</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-6jqnVGOqYUoC_Vh" /><figcaption>Photo by <a href="https://unsplash.com/@sctgrhm?utm_source=medium&amp;utm_medium=referral">Scott Graham</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Introduction</h3><p>Want to start your first enterprise product and don’t know where to start? I know, it seems very difficult and you go through it on your first product as well as your 1000th, or maybe it’s just me but hey, it doesn’t matter. The only thing that really matters is to be patient with yourself and your team. You might make mistakes and that is okay, we all do. Just give yourself time, you’ll get there.</p><h4>Okay, okay… I know, but where do I start?</h4><figure><img alt="I know GIF — Hercules" src="https://cdn-images-1.medium.com/max/403/1*Z6GAsoGBtlDaMcsTIx1qtg.gif" /></figure><p>When you’re starting to plan for enterprise applications you should take into consideration the current picture and situation of your enterprise. The first thing you have to take into consideration when trying to build a structure for your enterprise is the developers. This might be shocking but the developers have different skills, different knowledge and even different approaches to the same problems. They are the raw power of the application and not thinking developer first, cause burnouts, frustrations and might even break your team.</p><p>The second thing you need to take into account is best practices. I know, I know, everyone says that but having best practices and following community guidelines it’s not the best only for your team, but it translates when bringing new developers to the team. They can quickly follow the stack you are using without any major time delays. They can get up to speed and help in a record time.</p><p>The third thing you need is tests. Make sure your tests are meaningful and that they are written sometimes right before the components you are writing. Writing tests is not a waste of time. It helps not only to ensure product quality but it helps you ensure new changes don’t break other parts of the code.</p><p>Last thing and not less important is growth. Your application will grow and you have to account for it. You need to make sure you code can be split into smaller parts and even deployed in smaller chunks. This can translate into microservices, smaller chunks on your apps, or even making some abstract code to reuse in your apps. Make sure your code is decoupled. This is one of the most complicated parts of planning for your app because you can overthink everything or not well enough. <a href="https://medium.com/u/a76fa51de1ba">Max Lynch</a> had a tweet about this that is too accurate and hits way close to home that said:</p><blockquote>Duplicate code solves the problem inefficiently. Over-abstracted code solves the wrong problem. — Max Lynch</blockquote><p>So don’t overthink it but don’t underestimate the problem. Rely on your team, they can help you bring amazing ideas that can help not only the team, but all the parts involving the project.</p><h4>What now?</h4><figure><img alt="Stay Calm — The Office GIF" src="https://cdn-images-1.medium.com/max/245/1*JX-EDjhiJLR8FT70QKfaZw.gif" /></figure><p>It can be quite scary sometimes to be responsible over a product that an entire enterprise can depend on and getting out of the comfort zone can be scary but the most important thing is to know that you are not alone. You have your fellow developers that can bring ideas, there are out there amazing communities that can help you. Remember that you can’t know everything and it’s okay to ask.</p><p>Also, you will keep improving and keep learning from mistakes. Every single time you look at your product you will see stuff that can be improved, and after some time, you will think you would have done it differently and that is one of the best things that can happen to you: it means you’re evolving.</p><p>This is a first post of many, hopefully. If this helps you out, please comment and post your questions. I will be happy to help out.</p><p>To deeper dive you can check out <a href="https://medium.com/u/ca9a54f776a4">Elman Hasa</a>’s post about Enterprise Architecture here: <a href="https://medium.com/swlh/what-i-learned-studying-enterprise-architecture-cafbde9e6dc2">https://medium.com/swlh/what-i-learned-studying-enterprise-architecture-cafbde9e6dc2</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b4858028eb7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>