<?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 Muhammad Muizzsuddin on Medium]]></title>
        <description><![CDATA[Stories by Muhammad Muizzsuddin on Medium]]></description>
        <link>https://medium.com/@muizidn?source=rss-ab304432be0d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*N8MI0IpQSIZPBQPA.</url>
            <title>Stories by Muhammad Muizzsuddin on Medium</title>
            <link>https://medium.com/@muizidn?source=rss-ab304432be0d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 13:57:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@muizidn/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[Not every 500 error means a complex system failure]]></title>
            <link>https://muizidn.medium.com/not-every-500-error-means-a-complex-system-failure-b50c75efe862?source=rss-ab304432be0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b50c75efe862</guid>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[debugging]]></category>
            <dc:creator><![CDATA[Muhammad Muizzsuddin]]></dc:creator>
            <pubDate>Tue, 02 Jun 2026 06:33:35 GMT</pubDate>
            <atom:updated>2026-06-02T06:33:35.406Z</atom:updated>
            <content:encoded><![CDATA[<p>When you see a <strong>500 Internal Server Error</strong>, it’s easy to assume something big is broken.</p><p>A backend outage.<br>A failing service.<br>A distributed system issue.<br>A deep architectural bug.</p><p>But in reality, sometimes the cause is much simpler.</p><p>Today I ran into a situation where every API endpoint started returning <strong>500 errors</strong>.</p><figure><img alt="500 errors captured using Network Spy HTTP Debugger" src="https://cdn-images-1.medium.com/max/1024/1*PyycqSzgXac54AbztrhJJg.png" /><figcaption>500 Internal Server Errors captured in Network Spy HTTP Debugger</figcaption></figure><p>My first instinct was to assume the worst:</p><ul><li>broken deployment</li><li>database failure</li><li>infrastructure issue</li><li>service misconfiguration</li></ul><p>I immediately started digging through logs, tracing requests, and checking dependencies.</p><p>But after all that investigation, the root cause turned out to be something surprisingly simple — a basic issue in the database layer that triggered a chain of failures.</p><p>Nothing “architectural” was broken.<br>No system design flaw.<br>No complex distributed failure.</p><p>Just a straightforward issue that escalated into a full API failure.</p><h3>The lesson</h3><p>It’s easy to over-engineer the problem in your mind when you see a 500 error.</p><p>But a useful debugging mindset is:</p><blockquote><em>Start simple before assuming complexity.</em></blockquote><p>Most production issues usually fall into one of these categories:</p><ul><li>data inconsistency</li><li>missing configuration</li><li>invalid assumptions in code</li><li>small database constraint issues</li><li>failed external dependency</li></ul><p>Not always:</p><ul><li>system-wide architecture failure</li><li>complex distributed system bugs</li></ul><h3>Why this matters</h3><p>The danger in debugging isn’t just missing the root cause.</p><p>It’s <strong>jumping too quickly to a complex explanation</strong>.</p><p>Because when you assume complexity too early, you:</p><ul><li>over-analyze the wrong layers</li><li>waste time on unrelated systems</li><li>miss simple fixes hiding in plain sight</li></ul><h3>A better approach</h3><p>When you see a 500 error:</p><ol><li>Check the simplest possible causes first</li><li>Validate recent changes</li><li>Inspect shared dependencies (DB, config, auth)</li><li>Only then move to deeper system-level assumptions</li></ol><p>More often than not, the answer is not “distributed system failure.”</p><p>It’s something much simpler.</p><h3>Final thought</h3><p>Not every production issue is a “big architecture story.”</p><p>Sometimes it’s just a small mistake with a big impact.</p><p>And learning to recognize that difference is what makes debugging faster and more effective.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b50c75efe862" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You are NOT Vibecoder if you Do This.]]></title>
            <link>https://muizidn.medium.com/you-are-not-vibecoder-if-you-do-this-2e6498d775a2?source=rss-ab304432be0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e6498d775a2</guid>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[frontend-development]]></category>
            <dc:creator><![CDATA[Muhammad Muizzsuddin]]></dc:creator>
            <pubDate>Sun, 03 May 2026 01:59:57 GMT</pubDate>
            <atom:updated>2026-05-03T01:59:57.695Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8JyLx0Oh5BHhU4TY" /><figcaption>Photo by <a href="https://unsplash.com/@hdbernd?utm_source=medium&amp;utm_medium=referral">Bernd 📷 Dittrich</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>AI has changed how people write software. But it has also created a new stereotype: the <em>vibecoder</em>.</p><p>Someone who just asks AI to generate code, pastes it in, and hopes it works.</p><p>That is not development. That is outsourcing thinking.</p><p>Let’s break this down properly.</p><h3>1. What is a VibeCoder?</h3><p>A vibe coder is someone who:</p><ul><li>Prompts AI to write full features</li><li>Copies code without understanding it</li><li>Avoids debugging or deep inspection</li><li>Treats AI like a magic black box</li></ul><p>The workflow usually looks like this:</p><blockquote><em>“Write login system” → paste → “why doesn’t it work?” → repeat</em></blockquote><p>There is no ownership of logic. No mental model of the system.</p><p>Just vibes.</p><h3>2. Are You a VibeCoder?</h3><p>Be honest with yourself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tEGo0pdnKDRxyfGs" /><figcaption>Photo by <a href="https://unsplash.com/@darren1303?utm_source=medium&amp;utm_medium=referral">Darren Halstead</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If your workflow is:</p><ul><li>AI writes the code</li><li>AI fixes the code</li><li>AI deploys the code</li><li>You only test it like a user</li></ul><p>Then yes, you are very close to that category.</p><p>And the problem is not using AI.</p><p>The problem is <strong>not thinking beyond AI output</strong>.</p><h3>3. What You Should NOT Do</h3><p>If you are building real software, avoid this pattern:</p><ul><li>Ask AI to write the full system</li><li>Ask AI to review it</li><li>Ask AI to deploy it</li><li>Then just test it like an end user</li></ul><p>This turns you into a passive operator.</p><p>You are no longer engineering anything.</p><p>You are just validating outputs you do not understand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ybVnhzFP3OyQW9fm" /><figcaption>Photo by <a href="https://unsplash.com/@zulfugarkarimov?utm_source=medium&amp;utm_medium=referral">Zulfugar Karimov</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>4. What You SHOULD Do Instead</h3><p>Use AI as a <strong>multiplier, not a replacement for thinking</strong>.</p><p>Your role should be:</p><ul><li>Analyze system design</li><li>Review AI-generated code critically</li><li>Debug issues at runtime</li><li>Optimize performance and structure</li></ul><p>You stay responsible for:</p><ul><li>Architecture decisions</li><li>Data flow</li><li>Edge cases</li><li>Tradeoffs</li></ul><p>AI helps you move faster. It does not replace judgment.</p><h3>5. Tools That Make You a Real Developer (Not a VibeCoder)</h3><p>If you want to actually understand what your system is doing, use proper tooling.</p><h3>1. Traffic Inspector (NetworkSpy)</h3><p>Instead of guessing what your app sends or receives:</p><ul><li>Inspect API calls</li><li>View headers and payloads</li><li>Debug real network behavior</li></ul><p>You stop trusting outputs blindly and start verifying reality.</p><blockquote>Try NetworkSpy <a href="https://networkspy.app/">https://networkspy.app</a></blockquote><h3>2. Debugger (JavaScript / Browser DevTools)</h3><p>Do not rely on logs alone.</p><p>Use:</p><ul><li>Breakpoints</li><li>Call stack inspection</li><li>Step-through execution</li></ul><p>This is where real understanding happens.</p><h3>3. Code Review + Linting + Architecture Checks</h3><p>Before shipping anything:</p><ul><li>Run linters</li><li>Enforce structure rules</li><li>Review AI-generated code like it was written by another engineer</li></ul><p>Ask:</p><ul><li>Does this scale?</li><li>Is this modular?</li><li>What breaks under load?</li></ul><p>Not:</p><blockquote><em>“Does it run?”</em></blockquote><h3>Final Thought</h3><p>If your entire workflow is:</p><blockquote><em>AI writes → AI fixes → AI ships → you test like a user</em></blockquote><p>Then you are not building software.</p><p>You are just observing it.</p><p>But if you:</p><ul><li>Understand the system</li><li>Question the output</li><li>Debug reality</li><li>Improve structure</li><li>Use AI as acceleration, not replacement</li></ul><p>Then you are not a vibe coder.</p><p>You are a <strong>developer who happens to use AI to speed up their work</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e6498d775a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to make REST API client using Javascript Fetch API]]></title>
            <link>https://muizidn.medium.com/how-to-make-rest-api-client-using-javascript-fetch-api-74ad880918a0?source=rss-ab304432be0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/74ad880918a0</guid>
            <category><![CDATA[rest-api]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Muhammad Muizzsuddin]]></dc:creator>
            <pubDate>Sat, 02 May 2026 11:56:32 GMT</pubDate>
            <atom:updated>2026-05-30T12:29:34.649Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/711/1*7AYEVPU_HHl758U2XBiSQA.png" /><figcaption>from browser to internet</figcaption></figure><p>When you browse websites, your browser constantly sends HTTP requests behind the scenes.</p><p>However, you can also send HTTP requests manually in JavaScript using the built-in <strong>Fetch API </strong>no extra libraries needed.</p><p>This is especially useful when working with APIs, microservices, or third-party integrations.</p><p>For example, fetching JSON data can be as simple as:</p><pre>async function getQuotes() {<br>  const response = await fetch(&quot;https://dummyjson.com/quotes&quot;);<br>  const data = await response.json();<br>  return data;<br>}<br><br><br>getQuotes().then(console.log);</pre><p>Nice and clean, right?</p><p>But… as always, things get more complicated 😅</p><p>Working with fetch properly requires understanding how it handles errors, retries, timeouts, streaming, and more.</p><p>Think you’ve mastered it? Stick around, there’s more under the hood 😉</p><h3>Creating HTTP Requests</h3><p>Unlike C#, JavaScript doesn’t require factories or DI containers. The fetch function is globally available (in browsers and modern runtimes like Node.js).</p><p>Basic usage:</p><pre>fetch(&quot;https://dummyjson.com/quotes&quot;)<br>  .then(res =&gt; res.json())<br>  .then(data =&gt; console.log(data));</pre><p>Or with async/await:</p><pre>const response = await fetch(&quot;https://dummyjson.com/quotes&quot;);<br>const data = await response.json();</pre><p>Simple. But also… deceptively simple.</p><h3>Handling Errors (Important!)</h3><p>Here’s a common misconception:</p><p>👉 fetch <strong>does NOT throw errors for HTTP error status codes</strong> (like 404 or 500)</p><p>It only throws on <strong>network failures</strong>.</p><p>So this won’t work as expected:</p><pre>try {<br>  const res = await fetch(&quot;https://dummyjson.com/404&quot;);<br>} catch (err) {<br>  console.log(&quot;Error:&quot;, err); // ❌ won&#39;t run for 404<br>}</pre><p>Instead, you must check manually:</p><pre>const res = await fetch(&quot;https:/j/dummyjson.com/quotes&quot;);<br><br>if (!res.ok) {<br>  throw new Error(`HTTP error! Status: ${res.status}`);<br>}<br><br>const data = await res.json();</pre><p>Miss this, and you’ll debug ghosts for hours 👻</p><h3>Sending Different Types of Requests</h3><h3>GET</h3><pre>await fetch(&quot;/api/data&quot;);</pre><h3>POST</h3><pre>await fetch(&quot;https://example.com/api&quot;, {<br>  method: &quot;POST&quot;,<br>  headers: {<br>    &quot;Content-Type&quot;: &quot;application/json&quot;,<br>  },<br>  body: JSON.stringify({<br>    message: &quot;Hello world&quot;,<br>  }),<br>});</pre><h3>PUT / DELETE</h3><pre>await fetch(&quot;/api/resource/1&quot;, { method: &quot;PUT&quot; });<br>await fetch(&quot;/api/resource/1&quot;, { method: &quot;DELETE&quot; });</pre><h3>Reusable API Client</h3><p>Unlike C# typed clients, JavaScript typically uses wrapper functions or classes.</p><pre>class ApiClient {<br>  constructor(baseUrl) {<br>    this.baseUrl = baseUrl;<br>  }<br><br>  async getQuotes() {<br>    const res = await fetch(`${this.baseUrl}/quotes`);<br><br>    if (!res.ok) {<br>      throw new Error(&quot;Failed to fetch quotes&quot;);<br>    }<br><br>    return res.json();<br>  }<br>}<br><br>const client = new ApiClient(&quot;https://dummyjson.com&quot;);<br>const data = await client.getQuotes();</pre><p>This gives you:</p><ul><li>centralized logic</li><li>easier debugging</li><li>cleaner code structure</li></ul><p>Same idea as typed clients. Just more manual.</p><h3>Middleware (Sort of 😏)</h3><p>JavaScript doesn’t have built-in HTTP middleware like C#, but you can simulate it.</p><p>Example: logging wrapper</p><pre>async function fetchWithLogging(url, options) {<br>  console.log(&quot;Request:&quot;, url);<br>  const start = Date.now();<br>  const res = await fetch(url, options);<br>  console.log(&quot;Response time:&quot;, Date.now() - start, &quot;ms&quot;);<br>  return res;<br>}</pre><p>Or authentication:</p><pre>async function fetchWithAuth(url, options = {}) {<br>  const token = &quot;your-token&quot;;<br>  return fetch(url, {<br>    ...options,<br>    headers: {<br>      ...options.headers,<br>      Authorization: `Bearer ${token}`,<br>    },<br>  });<br>}</pre><p>You can chain these wrappers to mimic middleware behavior.</p><h3>Timeouts (Not Built-In 😬)</h3><p>fetch has <strong>no native timeout support</strong>.</p><p>You must implement it manually using AbortController:</p><pre>function fetchWithTimeout(url, timeout = 2000) {<br>  const controller = new AbortController();<br>  const id = setTimeout(() =&gt; controller.abort(), timeout);<br>  return fetch(url, {<br>    signal: controller.signal,<br>  }).finally(() =&gt; clearTimeout(id));<br>}</pre><p>If the request takes too long → it gets aborted.</p><p>Without this, your app can hang indefinitely.</p><h3>Retries</h3><p>Retries are not built-in either — you implement them yourself.</p><pre>async function fetchWithRetry(url, options = {}, retries = 3) {<br>  try {<br>    const res = await fetch(url, options);<br>    if (!res.ok) throw new Error(&quot;HTTP error&quot;);<br>      return res;<br>    } catch (err) {<br>    if (retries === 0) throw err;<br>    await new Promise(r =&gt; setTimeout(r, 200)); // delay<br>    return fetchWithRetry(url, options, retries - 1);<br>  }<br>}</pre><p>But be careful:</p><ul><li>Don’t retry 4xx errors blindly</li><li>Watch API rate limits</li><li>Add backoff (increase delay over time)</li></ul><h3>Streaming (Advanced ⚡)</h3><p>By default:</p><pre>const data = await res.json();</pre><p>👉 This loads the entire response into memory.</p><p>For large responses, use streams:</p><pre>const res = await fetch(url);<br>const reader = res.body.getReader();<br>const decoder = new TextDecoder();<br>while (true) {<br>  const { done, value } = await reader.read();<br>  if (done) break;<br>  console.log(decoder.decode(value));<br>}</pre><p>Benefits:</p><ul><li>lower memory usage</li><li>faster processing for large payloads</li></ul><p>But harder to debug 😅</p><h3>Canceling Requests</h3><p>You can cancel requests using AbortController:</p><pre>const controller = new AbortController();<br>fetch(&quot;/api&quot;, { signal: controller.signal });<br>// cancel later<br>controller.abort();</pre><p>⚠️ Be careful with non-GET requests:</p><p>Canceling a POST midway might leave the server in an inconsistent state.</p><p>Same warning as in C#:</p><ul><li>use cancellation mostly for <strong>GET</strong></li><li>ensure backend supports safe interruption</li></ul><h3>Resiliency (The Hard Part 😈)</h3><p>When calling APIs, things can go wrong:</p><ul><li>slow responses</li><li>failed requests</li><li>server downtime</li></ul><p>To handle this properly, you need:</p><h4>1. Timeout</h4><p>Prevent hanging requests</p><h4>2. Retry</h4><p>Handle temporary failures</p><h4>3. Backoff + Jitter</h4><p>Avoid hammering servers</p><h4>4. Circuit Breaker (manual or library)</h4><p>Stop requests when system is failing</p><p>Unlike C#, JavaScript doesn’t give you this out of the box — you build or use libraries.</p><h3>Idempotency</h3><p>Same concept applies:</p><ul><li>GET → safe</li><li>PUT → usually safe</li><li>DELETE → usually safe</li><li>POST → ⚠️ risky (can create duplicates)</li></ul><p>If you retry POST requests, consider adding a unique request ID:</p><pre>headers: {<br>  &quot;Idempotency-Key&quot;: crypto.randomUUID()<br>}</pre><p>Server must support it though.</p><h3>Final Thoughts</h3><p>Working with fetch looks simple… until it isn’t 😄</p><p>✔️ Always check response.ok<br>✔️ Implement timeouts manually<br>✔️ Be careful with retries<br>✔️ Use wrappers for cleaner architecture<br>✔️ Consider streaming for performance<br>✔️ Think about idempotency and failures</p><p>Unlike C#, JavaScript gives you freedom — but also responsibility.</p><p>No factories. No built-in resilience. No safety nets.</p><p>Just you… and the network 😅</p><p>💬 Have you ever shipped a feature and forgot to check response.ok?</p><p>Yeah… you’re not alone.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74ad880918a0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Tutorial: How to Write File using Typescript]]></title>
            <link>https://muizidn.medium.com/quick-tutorial-how-to-write-file-using-typescript-e7cee0472a32?source=rss-ab304432be0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7cee0472a32</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[typescript]]></category>
            <dc:creator><![CDATA[Muhammad Muizzsuddin]]></dc:creator>
            <pubDate>Mon, 17 Jul 2023 01:52:23 GMT</pubDate>
            <atom:updated>2026-05-02T12:27:06.520Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*c4d-LyLoh-X58jU4" /><figcaption>Photo by <a href="https://unsplash.com/@drscythe?utm_source=medium&amp;utm_medium=referral">Dominik Scythe</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Writing a file is common operation in programming languages and platforms. Be it mobile, web, or backend, you write file for various reasons.</p><p>In this tutorial, you will learn how to write file using Typescript.</p><blockquote>Let’s connect with me in X <a href="https://x.com/urugothor">@urugothor</a> . I am developing NetworkSpy HTTP Inspector so you can easily debug your application networking behavior with custom viewer!</blockquote><h3>Write File Synchronously</h3><p>You can use the fs module to write file synchronously.</p><p>You can follow this example code:</p><pre>import { writeFileSync } from &quot;fs&quot;;<br><br>console.log(&quot;Start Write&quot;)<br>writeFileSync(&quot;file.txt&quot;, &quot;My name is John&quot;, {<br> flag: &quot;w&quot;<br>})<br>console.log(&quot;End Write&quot;)</pre><h3>Write File Asynchronously</h3><p>You can use the samefs module to write file asynchronously.</p><p>You can follow this example code:</p><pre>import { promises } from &quot;fs&quot;;<br><br>console.log(&quot;Start Write&quot;)<br>promises.writeFile(&quot;file.txt&quot;, &quot;My name is Mozzlog&quot;, {<br> flag: &quot;w&quot;<br>}).then(() =&gt; {<br>  console.log(&quot;Finish Write&quot;)<br>})<br>console.log(&quot;Continue Working&quot;)</pre><p>Now you can write a file in Typescript quickly</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7cee0472a32" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Previously, I Didn’t Care About the Business. Then I Care as a Software Engineer.]]></title>
            <link>https://muizidn.medium.com/previously-i-didnt-care-about-the-business-then-i-care-as-a-software-engineer-66e75e62b839?source=rss-ab304432be0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/66e75e62b839</guid>
            <category><![CDATA[storytelling-for-business]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Muhammad Muizzsuddin]]></dc:creator>
            <pubDate>Sat, 08 Jul 2023 00:33:00 GMT</pubDate>
            <atom:updated>2023-07-08T00:33:00.326Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nf03cbpuvIHhGUai" /><figcaption>Photo by <a href="https://unsplash.com/@kaitlynbaker?utm_source=medium&amp;utm_medium=referral">Kaitlyn Baker</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Hi there! There are many times when we don’t get along with so many things. We are too busy with ourselves until, at some point, it changes. This point can be different for many people. As for me, in this post, I will talk about the transition from the growth phase to the profit phase in my company.</p><p>I worked with a team of 10 engineers at a multinational company. This company spans three countries and has a huge user base. They already have their system in place, so I just follow it. But when we started to expand our team and business, COVID came along. Raising money became difficult, and investors quit. We were doomed to close.</p><p>However, the upper management chose another path. They decided to close operations in other countries and keep the one in Indonesia. They even closed some operations in another city. The team underwent drastic changes in its goals. Previously, we aimed for growth, but then we shifted our focus to profitability. We started to implement tactics to increase user basket size, reduce operation costs, reduce overhead costs (that was the first time I got in touch with financial terms), make deals with our partners, and so on. Our efforts were not fruitless; we started to see growth.</p><p>And this is the story of how I started to care about the business. Upon seeing the struggle of businesses to increase their income while having to pay a huge amount of money for employees, I now understand how that burden feels. Businesses should make money, and engineers should help them by building and maintaining products. Previously, I didn’t care about it. All I cared about was being paid as an engineer; I built products as specified by my manager, made optimizations, and designed systems that allowed many engineers to work seamlessly. Then I realized this: I should add another variable to my success story to make an impact on the business.</p><p>Now I see that my code should be designed to provide fast insights for the business. It may not be part of the application that generates money, but the amount of data we can obtain from that part is also useful for making business decisions. Those decisions will steer the business goals for the next half-quarter, next quarter, next year, and beyond.</p><p>We conducted many A/B tests (which I previously didn’t care about). I started to see how product analysts make suggestions and request changes regarding the data we should send to the analytics platform. Observing how our platform and marketing team fight fraudsters also opened my eyes to something I had missed before: security is also a part of the business. You may run fast, but when security kicks in, you can get stuck for a long time because your money, efforts, data, and many other things can evaporate to nothing. So engineers should always keep security in mind.</p><p>Those are long processes. I started to care after I felt quite satisfied with my engineering skills, though I should always keep learning more. As engineers, we debate which frameworks or programming languages to use. We should also start debating what impact we can have on the business.</p><p>Should we debate? I think we should work together. We assess, we analyze, and we do. Together? Absolutely, together.</p><p>Hi, thank you for being with me until the end. I no longer work for the company. We parted ways amicably. Yes, it was a difficult decision for both of us. I had started to get along with my team, but now I have started my own venture. It began as a side project, but now I am fully committed to it and I hope to release it next year. Initially, I wanted to release it this fall, but it will be an immature product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cAgrpVNanNrbNjFyMsbM3A.png" /><figcaption>NetworkSpy</figcaption></figure><blockquote>With Network Spy, you can monitor, inspect, and modify your network traffic during development. Perfect for debugging and more analysis. 🙌</blockquote><blockquote>Join the Waitlist Today! <a href="https://mozzlog.com/projects/network-spy?utm_source=medium&amp;utm_medium=blog&amp;utm_campaign=article">https://mozzlog.com/projects/network-spy</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66e75e62b839" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Tutorial: Write String to File Asynchronously in Swift]]></title>
            <link>https://muizidn.medium.com/quick-tutorial-write-string-to-file-asynchronously-in-swift-840f2763352c?source=rss-ab304432be0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/840f2763352c</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[quick-tutorial]]></category>
            <category><![CDATA[code-snippet]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Muhammad Muizzsuddin]]></dc:creator>
            <pubDate>Fri, 07 Jul 2023 00:44:23 GMT</pubDate>
            <atom:updated>2023-07-07T01:27:08.151Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ESY5M8nt6h4loAFv" /><figcaption>Photo by <a href="https://unsplash.com/it/@cathrynlavery?utm_source=medium&amp;utm_medium=referral">Cathryn Lavery</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This quick tutorial is based on article from <a href="https://www.mozzlog.com/blog/how-to-write-the-content-of-string-to-a-file-in-swift">https://www.mozzlog.com/blog/how-to-write-the-content-of-string-to-a-file-in-swift</a></p><p><strong>Lets Go</strong></p><p>So, you’re looking for an asynchronous method to save a String to a file in Swift. Apple’s provided you with a simple API in the Foundation framework for creating Strings in Swift. Simply provide the file’s path and catch any resulting errors.</p><p>Unfortunately, despite this article&#39;s title, it is not asynchronous. Sorry. The API is not async. But you can call it in an asynchronous way. If your writing will take longer than a second to complete, you can put it in a queue in the background.</p><p>Okay. Let’s just jump to the code. To see if this code works, just copy and paste it into your Xcode.</p><pre>import Foundation<br><br>print(&quot;Start Write&quot;)<br>DispatchQueue.global(qos:.background).async {<br>  let content = &quot;My name is Mozzlog&quot;<br>  do {<br>    try content.write(toFile: &quot;file.txt&quot;, atomically: true, encoding:.utf8)<br>    print(&quot;End Write&quot;)<br>  } catch {<br>    print(&quot;Error: \\(error)&quot;)<br>  }<br>}</pre><p>That is all. To write a String to a file, you simply need to invoke its write method.</p><p><strong>Uh Snap! Error Happen!</strong></p><p>Well, no tutorial is perfect. Do you find mistakes? Does it crash?</p><p>Perhaps the tutorial is also obsolete. Please comment below if so. Let me update it as soon as possible. Thank you very much!</p><p><strong>Whats Next?</strong></p><p>You can read the full article of this quick tutorial in here: <a href="https://www.mozzlog.com/blog/how-to-write-the-content-of-string-to-a-file-in-swift?utm_source=medium&amp;utm_medium=blog&amp;utm_campaign=article">https://www.mozzlog.com/blog/how-to-write-the-content-of-string-to-a-file-in-swift</a></p><p>You can also read another article that talks about mobile, web, and backend in <a href="https://www.mozzlog.com/blog?utm_source=medium&amp;utm_medium=blog&amp;utm_campaign=article">https://www.mozzlog.com/blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=840f2763352c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick Tutorial: Write String to File in Swift]]></title>
            <link>https://muizidn.medium.com/quick-tutorial-write-string-to-file-in-swift-2c56afa5c7c1?source=rss-ab304432be0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c56afa5c7c1</guid>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[quick-tutorial]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[code-snippet]]></category>
            <dc:creator><![CDATA[Muhammad Muizzsuddin]]></dc:creator>
            <pubDate>Fri, 07 Jul 2023 00:28:52 GMT</pubDate>
            <atom:updated>2023-07-07T00:32:10.724Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kDtwOcDdGVudQxuu" /><figcaption>Photo by <a href="https://unsplash.com/@thoughtcatalog?utm_source=medium&amp;utm_medium=referral">Thought Catalog</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This quick tutorial is based on article from <a href="https://www.mozzlog.com/blog/how-to-write-the-content-of-string-to-a-file-in-swift">https://www.mozzlog.com/blog/how-to-write-the-content-of-string-to-a-file-in-swift</a></p><p><strong>Lets Go</strong></p><p>So, you want to know how to write a String to a file in Swift. Writing a String in Swift is easy because Apple has provided you with an easy API in the Foundation framework. You just need to supply the file path and catch the error, if any.</p><p>Without much talk. You can copy and paste this code to check how it works</p><pre>import Foundation<br><br>print(&quot;Start Write&quot;)<br>let content = &quot;My name is Mozzlog&quot;<br>do {<br>    try content.write(toFile: &quot;file.txt&quot;, atomically: true, encoding:.utf8)<br>    print(&quot;End Write&quot;)<br>} catch {<br>    print(&quot;Error: \\(error)&quot;)<br>}</pre><p>That’s it. You just need to invoke the write method from String to write it to a file.</p><p><strong>Uh Snap! Error Happen!</strong></p><p>Well, no tutorial is perfect. Do you find errors? Does it crash?</p><p>Maybe the tutorial is outdated too. If so, please comment below. Let me update it as soon as possible. Thank you!</p><p><strong>Whats Next?</strong></p><p>You can read the full article of this quick tutorial in here: <a href="https://www.mozzlog.com/blog/how-to-write-the-content-of-string-to-a-file-in-swift">https://www.mozzlog.com/blog/how-to-write-the-content-of-string-to-a-file-in-swift</a></p><p>You can also read another article that talks about mobile, web, and backend in <a href="https://www.mozzlog.com/blog">https://www.mozzlog.com/blog</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c56afa5c7c1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Swift Sectioned Array Filtering with O(n)]]></title>
            <link>https://muizidn.medium.com/swift-sectioned-array-filtering-with-o-n-fa0b86fbb159?source=rss-ab304432be0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa0b86fbb159</guid>
            <category><![CDATA[big-o-notation]]></category>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[sectioned-array]]></category>
            <dc:creator><![CDATA[Muhammad Muizzsuddin]]></dc:creator>
            <pubDate>Sat, 19 Jun 2021 00:03:21 GMT</pubDate>
            <atom:updated>2023-07-07T00:49:55.626Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S_62IajCWBVoSAD9DbK43Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@marcojodoin?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Marc-Olivier Jodoin</a> on <a href="https://unsplash.com/s/photos/speed?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>You want to filter a sectioned array quickly. But you hit the wall because it is difficult to find a tailored solution that has linear complexity.</p><p>Here is the code that you can use to quickly filter your sectioned array. This code is in Swift, but you can always adapt it to another language.</p><p>Right to the algorithm in here: <a href="https://gist.github.com/muizidn/15153af8df862260e694516988e3ea9c">https://gist.github.com/muizidn/15153af8df862260e694516988e3ea9c</a></p><p><strong>Network Spy</strong></p><p>Wait. This is a special invitation. You can move to another article if you want. 🙌</p><blockquote>With Network Spy, you can monitor, inspect, and modify your network traffic during development. Perfect for debugging and more analysis. 🙌 Join the Waitlist Today! <a href="https://mozzlog.com/projects/network-spy">https://mozzlog.com/projects/network-spy</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa0b86fbb159" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setup a New Machine for Apple Development is tiring! or?]]></title>
            <link>https://muizidn.medium.com/setup-a-new-machine-for-apple-development-is-tiring-or-3de6d62382b2?source=rss-ab304432be0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3de6d62382b2</guid>
            <category><![CDATA[apple-development]]></category>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[ios-development]]></category>
            <category><![CDATA[new-macbook-pro]]></category>
            <dc:creator><![CDATA[Muhammad Muizzsuddin]]></dc:creator>
            <pubDate>Wed, 14 Apr 2021 23:37:20 GMT</pubDate>
            <atom:updated>2021-04-14T23:37:20.828Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RRX2Ax1KGNU1Nl_gL_TsBw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@santsteink?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Santiago Steinkamp</a> on <a href="https://unsplash.com/s/photos/forge?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I am happy to have a new machine but it turns out I have lost so many hours to build my project. It turns out that upgrade from Mojave to Catalina is quite challenging yet it tells me a lot and uncover hidden meaning of every script, commandline, and whatever it is to let me back on the track.</p><p><strong>Xcode</strong></p><p>First thing first, switching different Xcode. My current project was built using Xcode11.2, Swift5.1. That of course cannot just be copied and build with current state using new Xcode12.4, new Swift version 5.3.</p><p>It tells me about the nightmare of having binary dependency which unless the technology handles this, different ABI will result to compilation error. Everyone know this but me 😭.</p><p><strong>Ruby, Gem</strong></p><p>As I need to rebuild my binary dependency, another wall blocking my way. Ruby is unforgiving with version difference, or I after quick browsing, it seems that I am not reading documentation enough. But it eventually solved. Spoiler, I should reinstall mac ruby with brew install ruby and manually updating PATH as follows in order to recognise plugin and gem installation.</p><pre>export PATH=&quot;/usr/local/opt/ruby/bin:$PATH&quot;</pre><pre>export PATH=&quot;/usr/local/opt/ruby/bin:$PATH&quot;</pre><pre>export PATH=&quot;/usr/local/lib/ruby/gems/3.0.0/bin:$PATH&quot;</pre><p><strong>Xcode-Select</strong></p><p>Yup, I think most of us (developers) will forget the last time doing xcode-select . This tool will handle CLI xcode version when we have different xcode installation. So, project A will use newest Xcode, while another one will use older version.</p><pre>xcode-select -s /Applications/Xcode11.3.app</pre><p><strong>Conclusion</strong></p><p>Maybe it’s just me. Or if you too, please share yours in comment to let me update this post and help another suffered one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3de6d62382b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Incorporate R.swift to Bazel.]]></title>
            <link>https://muizidn.medium.com/incorporate-r-swift-to-bazel-e9663d52d455?source=rss-ab304432be0d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9663d52d455</guid>
            <dc:creator><![CDATA[Muhammad Muizzsuddin]]></dc:creator>
            <pubDate>Fri, 11 Sep 2020 06:35:59 GMT</pubDate>
            <atom:updated>2020-09-11T06:37:32.857Z</atom:updated>
            <content:encoded><![CDATA[<p>Well, this is neither easy nor difficult. Just between the two. How to say it in English? Average?</p><p>Hello. I just have production experience with Bazel and I can’t wait to share it so everyone can benefit from it.</p><p>R.swift is a library to help us minimise stringy reference to resources. That’s my own word. Please check it out at <a href="https://github.com/mac-cain13/R.swift">https://github.com/mac-cain13/R.swift</a>.</p><p>To incorporate the workflow of generate R.generated.swift, we should have an xcodeproj where R.swift will <em>parse </em>and put the script in Build Phase.</p><p>Until now, I can’t find a solution built right inside bazel to invoke the script in a correct way. Besides, the <strong>rswift </strong>is an unforgiving tool that demands us to give it a lot of environment variables derived from xcodebuild which in turns, it should be invoked from xcodeproj.</p><p>The solution is quite simple.</p><p>Meet our friendly XcodeGen. This tool will help us generate an xcodeproj from a spec which we will write as follows,</p><pre><a href="https://gist.github.com/muizidn/26699fb4e3a1651eebcabe032a57dac3">https://gist.github.com/muizidn/26699fb4e3a1651eebcabe032a57dac3</a></pre><p>Then we can build using this code,</p><pre>xcodegen<br>xcodebuild -t rswift</pre><p>Thanks me later.</p><p><strong>Conclusion</strong></p><p>Easy. Peasy. Happy.</p><p>Thanks XcodeGen!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9663d52d455" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>