My Story: Curiosity, Code & The Relentless Pursuit of Craft

Chapter 1: The Humble Beginning — Curiosity Before Silicon

Growing up in Bangladesh, a career as a globally recognized software engineer and software founder was not something anyone in my immediate environment could map out for me. There were no elite coding academies down the street, no venture capital meetups, and no family members in tech who could hand down a blueprint. What I possessed was something far more durable: an unyielding obsession with understanding how digital systems worked beneath the polished surface.

My first encounters with programming took place on a modest computer that struggled whenever more than two browser tabs were open. In those early days, internet access was often slow, unreliable, and rationed. Whenever the connection dropped, I did not stop. Instead, I saved complete HTML documentation, language specifications, and tutorials onto local storage to study them line by line offline.

I will never forget the moment I wrote my first lines of HTML, styled them with raw CSS, and refreshed the browser. Seeing static text transform into a structured layout felt like nothing short of real-world magic. But while many people were satisfied with merely visual aesthetics, my curiosity immediately moved deeper: How does the browser parse this DOM tree? How does the CSS cascade calculate layout geometry? How does JavaScript manage memory and thread execution in the background? That fundamental question—how does this truly work under the hood?—became the engine of my entire engineering career.

Chapter 2: The Self-Taught Crucible — Learning How to Think in Systems

Like many aspiring engineers, I initially fell into what the developer community calls "tutorial hell"—watching hundreds of hours of video courses where instructors built polished applications in 20 minutes without showing the messy reality of architecture or debugging. It didn't take long to realize that passive video watching produces a dangerous illusion of competence. When you sit before a blank file without a video guiding your fingers, true capability is tested.

I abandoned passive tutorials and adopted a method of deliberate, aggressive engineering practice. I forced myself to build real, broken prototypes from scratch. Whenever a runtime error appeared in the DevTools console, I made a solemn rule: I would not copy-paste the error into a search engine or ask for a quick fix until I had read the entire call stack, inspected the memory state, and formulated a hypothesis about why the failure occurred.

I spent countless nights studying the ECMAScript specifications, dissecting the JavaScript Event Loop, understanding the differences between microtasks and macrotasks in the V8 engine, and mastering the nuances of asynchronous concurrency. I studied the open-source code of popular libraries, reading how senior engineers structured design patterns, abstracted interfaces, and prevented memory leaks. This self-taught crucible taught me the most valuable skill a programmer can possess: the ability to learn any technology from first principles without fear.

Chapter 3: The E-Commerce Awakening & The Shopify Frontier

When I entered the freelance arena, I made a crucial observation that changed the trajectory of my professional life. Most freelance marketplaces were flooded with generalist web developers competing in a desperate race to the bottom, offering $50 cookie-cutter websites built on bloated visual builders.

At the exact same time, e-commerce was exploding worldwide. Direct-to-consumer (DTC) brands were spending tens of thousands of dollars each month on paid acquisition (Meta, Google, TikTok ads), driving high-intent shoppers to storefronts that took 7 to 10 seconds to load on mobile devices. Store owners were bleeding money: 40% of prospective buyers bounced before the first product image even rendered.

Why were these stores so slow? Because merchants had installed visual drag-and-drop page builders (PageFly, Shogun, GemPages) on top of bulky pre-made themes, piling on 30+ conflicting third-party app scripts that mutated the DOM, blocked the main thread, and caused massive Cumulative Layout Shifts.

I saw an undeniable opportunity to provide massive, tangible business value: I would specialize deeply and uncompromisingly in high-performance Shopify engineering. I rejected visual page builders entirely and mastered native Shopify Liquid, the Online Store 2.0 component architecture, and headless integrations. I learned how to build bespoke, modular storefronts that gave merchants 100% visual customizability inside the native Shopify Theme Editor while delivering sub-second page loads and 95+ mobile Google Lighthouse scores.

Chapter 4: The Obsession with Sub-Second Speed & Core Web Vitals

In e-commerce, web performance is not an engineering vanity metric; it is direct financial arithmetic. Comprehensive research by Google, Amazon, and Walmart has demonstrated repeatedly that every 100 milliseconds of latency reduction translates to a 1% increase in conversion rate. When an enterprise store generates $300,000 in monthly revenue, cutting page load time by 1.5 seconds can directly generate over $45,000 in incremental gross profits every year.

Armed with this understanding, I turned performance tuning into an art form. I developed repeatable, surgical frameworks for Shopify stores:

• Critical CSS Inlining: Extracting and inlining only the above-the-fold layout styles directly into the HTML head, deferring the remaining global stylesheet to prevent render-blocking delays.
• Zero Cumulative Layout Shift (CLS = 0.000): Enforcing explicit intrinsic aspect-ratio boxes and skeleton placeholders for all images, hero banners, and promotional announcements so pages never visually jump while loading.
• Self-Hosted Subsetting of Modern Fonts: Eliminating Google Fonts external render-blocking network handshakes by self-hosting latin-subsetted WOFF2 fonts, shaving 200–400ms off mobile First Contentful Paint.
• Interaction to Next Paint (INP) Optimization: Breaking long tasks on the main thread using requestIdleCallback and scheduler yielding to guarantee instant touch response on mobile product carousels and AJAX cart drawers.

Watching a client's mobile Lighthouse score leap from a sluggish 24 to a blistering 98—and seeing their mobile conversion rate double within three weeks of launch—confirmed that my focus on technical fundamentals was the right path.

Case Study in Latency: Rescuing a Multi-Million Dollar Brand from an 8.2s Mobile LCP

To illustrate this in practice, consider an international apparel merchant that approached me in early 2024. They were spending $65,000 monthly on paid advertising, but their mobile bounce rate exceeded 68%. An in-depth synthetic and real-user monitoring (RUM) audit revealed a disastrous reality: their mobile Largest Contentful Paint was clocking in at 8.2 seconds.

The root cause was a cascading failure of modern web anti-patterns:

• A popular visual page builder had generated 4,800 DOM nodes for a single product template, triggering severe browser layout thrashing during rendering.
• The hero product image was uncompressed (a 4.2MB PNG) being loaded without explicit dimensions, causing a massive layout shift (CLS of 0.42).
• Four separate review and countdown apps were injecting uncompressed jQuery libraries and remote CSS files before the DOM could paint.

Over a 14-day engineering sprint, I rebuilt the product detail experience entirely in native Liquid 2.0. We eradicated every page builder dependency, converted the hero media to responsive modern WebP/AVIF formats with preloading, inlined the critical above-the-fold CSS tokens, and deferred all non-critical third-party telemetry until after user interaction.

The results were staggering: Mobile LCP dropped from 8.2s to 1.1s, mobile bounce rates plummeted by 34%, and within 30 days the brand recorded a 42% increase in mobile checkout completions without increasing their ad spend by a single dollar. That is the transformative economic power of engineering craftsmanship.

Chapter 5: Transitioning to SaaS — The Genesis of Stockly & Kilo

While freelancing gave me intimate insight into client pain points, I knew that true technical mastery required building, launching, and maintaining my own commercial software products. In 2024, I set out to architect my first official SaaS product for the Shopify App Store.

Through dozens of theme audits, I noticed that merchants constantly struggled with stockouts. Popular products would sell out unexpectedly, resulting in lost revenue, frustrated customers, and warehouse chaos. At the same time, merchants had zero automated way to forecast demand based on seasonal velocity or notify interested shoppers when inventory returned.

I conceived, architected, and built Stockly: Inventory & Reorder (Shopify App Store). Built with Remix, React, Shopify Polaris, App Bridge v4, and the GraphQL Admin API, Stockly provides:

• Sales-Velocity Demand Forecasting: Calculating exact inventory runways and reorder points based on 7-day, 14-day, and 30-day velocity.
• 1-Click Automated Purchase Orders: Generating supplier POs factoring in vendor lead times and minimum order quantities.
• Multi-Channel Staff & Customer Restock Alerts: Instant notifications to warehouse teams via Slack, email, and automated customer recovery alerts.

As Stockly grew, I noticed another pervasive issue: merchants were constantly uploading raw 10MB JPEG and PNG product photos directly from photographers into their Shopify catalogs, destroying their store speed. To solve this problem without charging merchants expensive cloud fees or risking their privacy, I engineered Kilo (kilo.nazmulcodes.org).

Kilo — Fast Media Compression & Format Converter

100% Client-Side Web App

In-browser image optimization & WebP converter with zero server uploads and 1-click Shopify catalog sync.

Launch Kilo (kilo.nazmulcodes.org)

The Architectural Philosophy Behind Kilo: 100% Client-Side Privacy

Traditional image optimization tools follow an outdated server-heavy paradigm: the user uploads gigabytes of proprietary product photography to a remote cloud server, where expensive backend CPU clusters compress the files before sending them back. This model introduces severe privacy vulnerabilities, bandwidth costs, and sluggish upload queues.

With Kilo, I engineered a radical alternative: 100% client-side, browser-native media compression. Utilizing modern WebAssembly (WASM), HTML5 Canvas, and OffscreenCanvas web workers, all image processing occurs entirely within the merchant's own browser sandbox.

Zero bytes of image data ever leave the merchant's device. Merchants can drag and drop dozens of heavy product photos and batch-convert them into modern WebP, AVIF, or ICO formats at near-zero latency, completely offline and free of subscription costs. For Stockly users, Kilo serves as an integrated companion tool, allowing store managers to optimize catalog assets before publishing them to their live storefront.

Alongside my own products, I also accepted high-impact technical contracts, such as working as the lead frontend engineer for DemandMind Technologies, building enterprise Shopify Admin Polaris interfaces to render complex seasonal forecasting data.

Chapter 6: The Upwork Journey — Competing Globally with Radical Integrity

Breaking into the international freelance market from Bangladesh is notoriously challenging. Many prospective clients harbor unconscious biases, assuming developers from South Asia only offer cheap, low-quality labor.

From day one, I refused to play that game. I made an unshakeable commitment: I would never compete on low price; I would compete on diagnostic superiority, engineering excellence, and transparent communication.

Whenever I submitted a proposal for a project on Upwork, I never used generic copy-pasted templates. Instead, I spent 30 to 45 minutes performing a live audit of the merchant's website. I recorded brief video walkthroughs demonstrating the exact JavaScript conflicts causing their checkout errors, provided the line numbers where their theme was leaking memory, and outlined a step-by-step remediation plan before asking for a single dollar.

Clients were astounded. They realized they were not talking to an order-taker, but to a senior engineering partner genuinely invested in the economic health of their business. This dedication resulted in a flawless 100% Job Success Score (JSS), the prestigious Top-Rated badge on Upwork, and long-term retainer partnerships with visionary founders across the globe.

Chapter 7: Technical Craftsmanship & Mental Models

Over the course of completing more than 33 major commercial projects and authoring 41 technical guides, I have codified the mental models that guide my engineering choices every day:

Chapter 8: The Vision Forward & A Message to Rising Developers

Looking to the future, e-commerce and web development are entering an exciting era of transformation. With the rollout of Shopify Checkout Extensibility, WebAssembly-powered Shopify Functions, Remix single-fetch pipelines, and edge computing, the boundary between web apps and native applications is blurring.

My goal is to continue pushing the frontier of what is possible on the web—building resilient apps like Stockly and Kilo, helping ambitious brands scale their infrastructure, and freely sharing everything I learn on the NazmulCodes Blog.

I want to leave a direct, heartfelt message for any aspiring developer reading this—especially those from Bangladesh or developing countries who feel that the odds are stacked against them: