<?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: S.M.Rejuanul Islam</title>
    <description>The latest articles on DEV Community by S.M.Rejuanul Islam (@smrejuanul_islam_e2e79a).</description>
    <link>https://dev.to/smrejuanul_islam_e2e79a</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%2F3504542%2Fc8877a32-adf4-4e42-82c1-f01bb47e12ff.jpg</url>
      <title>DEV Community: S.M.Rejuanul Islam</title>
      <link>https://dev.to/smrejuanul_islam_e2e79a</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/smrejuanul_islam_e2e79a"/>
    <language>en</language>
    <item>
      <title>I wasn't chasing a perfect Lighthouse score when I started this project.</title>
      <dc:creator>S.M.Rejuanul Islam</dc:creator>
      <pubDate>Mon, 27 Oct 2025 17:28:35 +0000</pubDate>
      <link>https://dev.to/smrejuanul_islam_e2e79a/i-wasnt-chasing-a-perfect-lighthouse-score-when-i-started-this-project-47lg</link>
      <guid>https://dev.to/smrejuanul_islam_e2e79a/i-wasnt-chasing-a-perfect-lighthouse-score-when-i-started-this-project-47lg</guid>
      <description>&lt;p&gt;My focus was simple: build something fast, clean, &lt;br&gt;
and accessible for the client. &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.amazonaws.com%2Fuploads%2Farticles%2Ftxz3650nkndovkqdzc9w.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.amazonaws.com%2Fuploads%2Farticles%2Ftxz3650nkndovkqdzc9w.png" alt=" " width="800" height="475"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;But here's what I learned: &lt;/p&gt;

&lt;p&gt;when you make thoughtful decisions from the start, &lt;br&gt;
the results follow naturally.&lt;/p&gt;

&lt;p&gt;Things like structuring content with performance in mind, &lt;br&gt;
optimizing images properly, eliminating layout shifts, &lt;br&gt;
and writing semantic, accessible HTML.&lt;/p&gt;

&lt;p&gt;The outcome? 100/100 across all four Lighthouse metrics.&lt;/p&gt;

&lt;p&gt;But here's the thing. The score isn't what matters most. &lt;/p&gt;

&lt;p&gt;It's that the site loads fast on slow networks.&lt;/p&gt;

&lt;p&gt;It works beautifully across devices. Users get what they need, quickly.&lt;/p&gt;

&lt;p&gt;The perfect score? That's just a side effect of building with care.&lt;/p&gt;

&lt;p&gt;And yes, Google appreciates it too 😊&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>design</category>
      <category>performance</category>
    </item>
    <item>
      <title>How I Built Mentorak in Days Using Kiro: A Dev Journey With Specs, Hooks, and AI</title>
      <dc:creator>S.M.Rejuanul Islam</dc:creator>
      <pubDate>Mon, 15 Sep 2025 18:15:03 +0000</pubDate>
      <link>https://dev.to/smrejuanul_islam_e2e79a/how-i-built-mentorak-in-days-using-kiro-a-dev-journey-with-specs-hooks-and-ai-34jo</link>
      <guid>https://dev.to/smrejuanul_islam_e2e79a/how-i-built-mentorak-in-days-using-kiro-a-dev-journey-with-specs-hooks-and-ai-34jo</guid>
      <description>&lt;p&gt;As a solo developer and hackathon enthusiast, I'm constantly searching for ways to build smarter, not harder. That’s why I turned to Kiro for my latest project Mentorak, an AI-powered quiz generator designed to help students, educators, and lifelong learners generate custom quizzes in seconds.&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.amazonaws.com%2Fuploads%2Farticles%2Fi2vyd031x716mxo08u8q.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.amazonaws.com%2Fuploads%2Farticles%2Fi2vyd031x716mxo08u8q.png" alt=" " width="800" height="436"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Users type in any topic from Photosynthesis to World War II  and Mentorak instantly returns 10 multiple-choice questions with answer options, scoring feedback, and a saved history for future review.&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.amazonaws.com%2Fuploads%2Farticles%2F3106zbml8gxjogqd36wk.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.amazonaws.com%2Fuploads%2Farticles%2F3106zbml8gxjogqd36wk.png" alt=" " width="800" height="460"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Instead of writing boilerplate code, I started with structured natural language specs, which Kiro translated into routes, components, and logic. It completely shifted how I approached building products.&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.amazonaws.com%2Fuploads%2Farticles%2F0s28uva6mpohnallcn70.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.amazonaws.com%2Fuploads%2Farticles%2F0s28uva6mpohnallcn70.png" alt=" " width="800" height="448"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;📐 How Kiro Changed My Development Process&lt;br&gt;
With traditional development, I’d usually:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Create the folder structure manually&lt;/li&gt;
&lt;li&gt;Write repetitive components, APIs, types, and error handling&lt;/li&gt;
&lt;li&gt;Then wire everything together&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What Surprised Me&lt;br&gt;
A few moments stood out where Kiro exceeded my expectations:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Edge Case Handling: Kiro auto-added error boundaries and loading states I hadn’t thought of&lt;/li&gt;
&lt;li&gt;Agent Hooks: Though I didn’t use many in this build, experimenting with them showed me how async logic and state transitions could be modular and powerful&lt;/li&gt;
&lt;li&gt;Speed of Iteration: I built, broke, and rebuilt faster than ever before — because I wasn’t afraid to try new things. Specs made rollback and rethinking feel safe.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;🏁 Final Thoughts&lt;br&gt;
Mentorak is just getting started — but I already have some exciting future plans:&lt;/p&gt;

&lt;p&gt;🎤 Voice input + feedback: Turn the quiz into an interactive conversation&lt;br&gt;
🎮 Multiplayer quiz battles: Challenge friends on shared topics&lt;br&gt;
📊 Analytics and skill tracking: Visualize learning over time&lt;/p&gt;

&lt;p&gt;Try it out &lt;a href="https://mentorak.com/" rel="noopener noreferrer"&gt;https://mentorak.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;But most importantly this project has permanently changed how I code.&lt;/p&gt;

&lt;p&gt;I no longer want to write everything from scratch.&lt;br&gt;
With Kiro, I can stay in flow, stay creative, and ship more in less time.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>showdev</category>
      <category>tooling</category>
      <category>kiro</category>
    </item>
  </channel>
</rss>
