<?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: Yaser A.M. Sweity | ياسر سويطي</title>
    <description>The latest articles on DEV Community by Yaser A.M. Sweity | ياسر سويطي (@yasersweity).</description>
    <link>https://dev.to/yasersweity</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%2F4256242%2Fea3a25ca-126e-4ed1-826f-c9d7cfdb7a68.jpeg</url>
      <title>DEV Community: Yaser A.M. Sweity | ياسر سويطي</title>
      <link>https://dev.to/yasersweity</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/yasersweity"/>
    <language>en</language>
    <item>
      <title>One Platform, One Engineer: The Decisions That Built Glamora</title>
      <dc:creator>Yaser A.M. Sweity | ياسر سويطي</dc:creator>
      <pubDate>Fri, 20 Nov 2026 20:22:38 +0000</pubDate>
      <link>https://dev.to/yasersweity/one-platform-one-engineer-the-decisions-that-built-glamora-bm1</link>
      <guid>https://dev.to/yasersweity/one-platform-one-engineer-the-decisions-that-built-glamora-bm1</guid>
      <description>&lt;p&gt;When I decided to launch Glamora, an online store for gifts, home décor and fashion, I didn't have a team. No front-end engineer, no back-end engineer, no security specialist, no accountant.&lt;/p&gt;

&lt;p&gt;Today the platform runs end to end: a website and a mobile app, an admin dashboard for orders and products, an accounting system that calculates the real profit of every item, instant notifications, and a smart shopping assistant that answers customers.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F607zl5d1zeujw12y7k3p.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F607zl5d1zeujw12y7k3p.png" alt="Glamora platform architecture" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This isn't an article about what I built. It's about the decisions that made it possible. When you work alone, you can't afford big mistakes: every engineering decision either carries you or sinks you.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision 1: One truth, in one place
&lt;/h2&gt;

&lt;p&gt;Imagine a shop with three inventory notebooks: one with the seller, one with the accountant, one with the manager. Within a week, none of them match.&lt;/p&gt;

&lt;p&gt;The website, the mobile app and the admin dashboard are three different interfaces, but they all read from and write to a single PostgreSQL database. There are no copies to keep in sync, and no "website truth" that differs from the "app truth". When a price changes, it changes everywhere at the same moment. That single decision eliminated an entire class of bugs before they were born.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision 2: Rules live where the data lives
&lt;/h2&gt;

&lt;p&gt;Instead of writing instructions on every door, write them once, on the safe itself.&lt;/p&gt;

&lt;p&gt;The important rules don't live in the screens. They live inside the database as triggers that fire on every change. Glamora sells bundles made of several items, and a bundle's availability is never managed by hand: it is derived from the availability of its parts. Notifications work the same way. When one is created, it is pushed to phones automatically through a cloud function, without any screen being involved.&lt;/p&gt;

&lt;p&gt;The rule taught me something more valuable than the rule itself. I once found bundles still marked unavailable after their items were back in stock, because the trigger only reacted to one kind of change. Systems don't fail where you expect them to; they fail where you made assumptions. Since then, I ask of every rule: which cases haven't I thought of?&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision 3: Every drawer has its own lock
&lt;/h2&gt;

&lt;p&gt;Most systems only guard the front door. Once you're in, you can reach everything.&lt;/p&gt;

&lt;p&gt;In Glamora, every table is protected by Row Level Security policies. A customer can only see their own orders. Sensitive data, such as product costs and the questions customers ask the assistant, can only be read by the store owner, even if someone tries to query it directly. Security isn't a layer added at the end; it's part of the data model. Deny is the default. Access is the exception.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision 4: Design for the network your customers actually have
&lt;/h2&gt;

&lt;p&gt;Not every customer has fast internet, and if a page takes three seconds to load, they leave.&lt;/p&gt;

&lt;p&gt;Every product image is stored in three WebP sizes: small for lists, medium for product pages, large for zoom. A phone never downloads more than it needs. App updates ship over the air, without waiting for app-store review, so a bug can be fixed in minutes rather than days.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision 5: The smart assistant as a tool for understanding, not decoration
&lt;/h2&gt;

&lt;p&gt;I built a shopping assistant that answers customers and recommends products. It runs on the server, not on the user's device, with three safeguards: a rate limit per user to protect the system and its cost, anonymous logging of customer questions (the text only, no personal data), and read access to those questions for the store owner only.&lt;/p&gt;

&lt;p&gt;Why log the questions? Because what customers ask is the most honest market research there is: what are they looking for and not finding? That turns the assistant from a technical feature into a source of product decisions.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision 6: Engineering doesn't end at deployment. It ends at profit
&lt;/h2&gt;

&lt;p&gt;A store that sells a lot can also lose a lot, without noticing.&lt;/p&gt;

&lt;p&gt;Inside the dashboard, I built an accounting module that links every product to its real cost. When I designed the bundles, I didn't settle for a discount that looked attractive. I checked the margin of every bundle against the cost of every item in it before a single customer saw it. A system that works technically but loses money is a failed system. A good engineer reads numbers as carefully as code.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I learned
&lt;/h2&gt;

&lt;p&gt;Six decisions, and one principle behind them: when you're alone, don't build more. Build right.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;One source of truth instead of many copies.&lt;/li&gt;
&lt;li&gt;Rules in one place instead of scattered instructions.&lt;/li&gt;
&lt;li&gt;Security built into the structure, not a guard at the door.&lt;/li&gt;
&lt;li&gt;Design for the reality your customers live in, not the one you wish for.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Modern tools can give a single engineer the power of a whole team. What they can't give is the most important thing: knowing which decisions are worth making. That isn't bought. It's built, one decision at a time.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://medium.com/@yasersweity/one-platform-one-engineer-the-decisions-that-built-glamora-fc57b87374cd" rel="noopener noreferrer"&gt;Medium&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>architecture</category>
      <category>postgres</category>
      <category>startup</category>
    </item>
  </channel>
</rss>
