<?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: Matan Lachmish</title>
    <description>The latest articles on DEV Community by Matan Lachmish (@mlachmish).</description>
    <link>https://dev.to/mlachmish</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F541366%2F11767cab-96c7-4ef2-a6f2-10dfd5d2b1f0.jpeg</url>
      <title>DEV Community: Matan Lachmish</title>
      <link>https://dev.to/mlachmish</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mlachmish"/>
    <language>en</language>
    <item>
      <title>Controlling the beast</title>
      <dc:creator>Matan Lachmish</dc:creator>
      <pubDate>Wed, 03 Mar 2021 16:15:49 +0000</pubDate>
      <link>https://dev.to/sanga/controlling-the-beast-17ff</link>
      <guid>https://dev.to/sanga/controlling-the-beast-17ff</guid>
      <description>&lt;p&gt;We have all seen these happen too many times:&lt;br&gt;&lt;br&gt;
Every big project starts as a small one.&lt;br&gt;
and a small project does not need a lot of stuff, right?  &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It doesn't need &lt;strong&gt;TESTING&lt;/strong&gt; 🙈&lt;/li&gt;
&lt;li&gt;It doesn't need &lt;strong&gt;SECURITY&lt;/strong&gt; 🙉&lt;/li&gt;
&lt;li&gt;It doesn't need &lt;strong&gt;CI/CD&lt;/strong&gt; 🙊&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://i.giphy.com/media/3o85xDWOG8Sbl9yQzm/giphy.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://i.giphy.com/media/3o85xDWOG8Sbl9yQzm/giphy.gif" alt="Alt text of image"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Well, if you plan for this project to stay grounded and never make the leap to become a production product then you are probably right 🐒&lt;/p&gt;

&lt;p&gt;This Byte is about another item that is usually left out until the project is too big and desperately needs it - &lt;strong&gt;CONTROLLING&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Controlling
&lt;/h2&gt;

&lt;p&gt;Every system needs a way to control its production product, for instance:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;User's data&lt;/li&gt;
&lt;li&gt;Content served by your app&lt;/li&gt;
&lt;li&gt;Feature flags&lt;/li&gt;
&lt;li&gt;Many more...&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The greedy way
&lt;/h2&gt;

&lt;p&gt;"For now, let's just create admin APIs"&lt;br&gt;&lt;br&gt;
Well, you do have a way to control but in the cost of:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Constant manual dev effort (the worst kind of dev effort 😉)&lt;/li&gt;
&lt;li&gt;Inconsistent way of use, the risk of breaking something up is always high&lt;/li&gt;
&lt;li&gt;Obscurity of implementation, APIs that are not consumed by any client can break/change without anyone knowing.&lt;/li&gt;
&lt;li&gt;Centralized knowledge of how to control your system&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The better way
&lt;/h2&gt;

&lt;p&gt;Some call it "Admin Panel", others "Back office", I've heard "Dashboard" and "Console".&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;In Sanga we call it Control™&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;An easy-to-use app that provides a safe and consistent way of using those notorious "Admin APIs".&lt;/p&gt;

&lt;h2&gt;
  
  
  Controlling the beast at Sanga
&lt;/h2&gt;

&lt;p&gt;As soon as we felt that those admin APIs are being used more than "just a couple of times" we've built our Control™ using Vue.js.  &lt;/p&gt;

&lt;p&gt;As straightforward as it may sound, our "definition of done" for a feature includes the ability to manage the feature through Control™.&lt;br&gt;&lt;br&gt;
That means that for every feature we:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Think what are the possible ways to control this feature&lt;/li&gt;
&lt;li&gt;Design the relevant admin APIs&lt;/li&gt;
&lt;li&gt;Enhance Control™ with the ability to interact with these APIs&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Fun fact
&lt;/h2&gt;

&lt;p&gt;Once you have such a capability, new features are being designed with control in place. That leads to some super cool capabilities that otherwise would probably be developed as stiff client-side logic that would be re-written endlessly.&lt;/p&gt;

&lt;h3&gt;
  
  
  Thank you for reading, look for our next Byte
&lt;/h3&gt;

&lt;p&gt;&lt;em&gt;Made with ❤️ by &lt;a href="https://www.sanga.app"&gt;Sanga&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>software</category>
      <category>admin</category>
      <category>sanga</category>
      <category>bestpractice</category>
    </item>
    <item>
      <title>Welcome to Sanga Bytes</title>
      <dc:creator>Matan Lachmish</dc:creator>
      <pubDate>Wed, 20 Jan 2021 12:09:18 +0000</pubDate>
      <link>https://dev.to/sanga/welcome-to-sanga-bytes-2el0</link>
      <guid>https://dev.to/sanga/welcome-to-sanga-bytes-2el0</guid>
      <description>&lt;p&gt;This is exciting...&lt;br&gt;&lt;br&gt;
Every big journey start with one small step,&lt;br&gt;&lt;br&gt;
and this is the very first (and very small) step of &lt;a href="https://www.sanga.app"&gt;Sanga&lt;/a&gt;'s &lt;a href="https://www.dev.to/sanga"&gt;tech blog&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Let us introduce you to our Byte size concept.
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://i.giphy.com/media/McgWV3RzDQZZNdFWRA/giphy.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://i.giphy.com/media/McgWV3RzDQZZNdFWRA/giphy.gif" alt="Alt text of image"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The theme of our company's tech blog is to share with the dev community the concepts we came to refine during our journey of developing Sanga.&lt;/p&gt;

&lt;p&gt;We aim to share ideas and ignite a thought process.&lt;br&gt;&lt;br&gt;
You will not find tutorials, or a very detailed step by step posts on how to write your first microservice or how to use Combine with Swift UI.&lt;/p&gt;

&lt;p&gt;Instead, you will find a very concise concept written in a Byte size format.&lt;br&gt;&lt;br&gt;
Meaning, &lt;strong&gt;no more than a couple of paragraphs and an image&lt;/strong&gt;.  &lt;/p&gt;

&lt;p&gt;We hope that this format will increase the relevancy of each post to all sort of backgrounds and stacks.&lt;br&gt;&lt;br&gt;
And we are positive that reading a Byte size post is easier than a Gigabyte one.&lt;/p&gt;

&lt;h3&gt;
  
  
  Thank you for reading, look for our next Byte
&lt;/h3&gt;

&lt;p&gt;&lt;em&gt;Made with ❤️ by &lt;a href="https://www.sanga.app"&gt;Sanga&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>firstpost</category>
      <category>sanga</category>
    </item>
  </channel>
</rss>
