<?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: Gentian Elmazi</title>
    <description>The latest articles on DEV Community by Gentian Elmazi (@gentos).</description>
    <link>https://dev.to/gentos</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%2F3168177%2F45acddec-486c-4c9e-b981-eddb9754c0e4.jpg</url>
      <title>DEV Community: Gentian Elmazi</title>
      <link>https://dev.to/gentos</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/gentos"/>
    <language>en</language>
    <item>
      <title>How to onboard engineers 10x faster</title>
      <dc:creator>Gentian Elmazi</dc:creator>
      <pubDate>Tue, 28 Oct 2025 22:44:16 +0000</pubDate>
      <link>https://dev.to/gentos/how-to-onboard-engineers-faster-306g</link>
      <guid>https://dev.to/gentos/how-to-onboard-engineers-faster-306g</guid>
      <description>&lt;p&gt;Finding time to &lt;strong&gt;#buildinpublic&lt;/strong&gt; is never easy — but it’s always worth it.&lt;/p&gt;

&lt;p&gt;Today, I’m excited to share one of the newest features we’ve launched at &lt;a href="https://infinitcode.ai/" rel="noopener noreferrer"&gt;Infinitcode.ai&lt;/a&gt;: 👉 Code Explorer&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is Code Explorer?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Code Explorer transforms your repositories into an interactive visual map, allowing you to understand project structure at a glance. Whether you're diving into a new codebase or managing a large enterprise repository, it helps you navigate, explore, and comprehend code faster.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why it matters&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If you’ve ever switched projects or joined a new team, you know the struggle: it can take 1–3 months to truly get up to speed.&lt;/p&gt;

&lt;p&gt;Even with onboarding processes in place, most of that context disappears once the onboarding engineer moves on — leaving new developers to start from scratch.&lt;/p&gt;

&lt;p&gt;With Code Explorer, we’re making that transition seamless.&lt;/p&gt;

&lt;p&gt;It’s designed for fast onboarding, knowledge sharing, and cross-team collaboration — so switching projects no longer means weeks of catching up.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What you can do with Code Explorer&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Beyond visualization, Infinitcode AI extends Code Explorer with powerful AI actions:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;🧠 Explain a file or function&lt;/li&gt;
&lt;li&gt;📘 Generate documentation automatically&lt;/li&gt;
&lt;li&gt;🧪 Write unit tests with full coverage suggestions&lt;/li&gt;
&lt;li&gt;🔍 Review files and detect potential issues&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;strong&gt;Why teams love it&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Open Source teams: Maintain high-quality documentation for easier adoption and contributions.&lt;/li&gt;
&lt;li&gt;QA and Dev teams: Automatically generate meaningful test coverage across all branches.&lt;/li&gt;
&lt;li&gt;Enterprises: Cut onboarding time from months to weeks.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We tested it ourselves — onboarding that used to take up to 3 months now takes just 1–2 weeks. Documentation gaps are gone, and code reviews are faster and more reliable.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Try it yourself&lt;/strong&gt;&lt;br&gt;
You can explore it right now at &lt;a href="https://infinitcode.ai/" rel="noopener noreferrer"&gt;infinitcode.ai&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;💡 Free forever for:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Startups with up to 3 team members&lt;/li&gt;
&lt;li&gt;Open Source projects&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Curious to hear what you think — how would Code Explorer fit into your workflow?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>ai</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Integrations, Integrations, Integrations… and why they matter</title>
      <dc:creator>Gentian Elmazi</dc:creator>
      <pubDate>Tue, 10 Jun 2025 14:59:52 +0000</pubDate>
      <link>https://dev.to/gentos/integrations-integrations-integrations-and-why-they-matter-24ng</link>
      <guid>https://dev.to/gentos/integrations-integrations-integrations-and-why-they-matter-24ng</guid>
      <description>&lt;h2&gt;
  
  
  Integrations, Integrations, Integrations… and why they matter
&lt;/h2&gt;

&lt;p&gt;As the second post in #buildinpublic, I'm sharing insights from our team at &lt;a href="https://infinitcode.ai/" rel="noopener noreferrer"&gt;Infinitcode.ai&lt;/a&gt; about why integrations matter.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why integrations matter
&lt;/h3&gt;

&lt;p&gt;Software teams typically use multiple tools in their day-to-day work. This can get messy quickly because developers need to focus on productivity rather than getting distracted by constantly switching between tools.&lt;/p&gt;

&lt;p&gt;Developers are simple creatures: they hate bureaucracy and love simplicity. &lt;/p&gt;

&lt;p&gt;A few tools they use daily (from my personal experience) include:  &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Email
&lt;/li&gt;
&lt;li&gt;Git (GitHub, GitLab...)
&lt;/li&gt;
&lt;li&gt;Communication tools (Slack, Discord ❤️)
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;To keep everyone aligned, you need to communicate through these channels.  &lt;/p&gt;

&lt;p&gt;Here's why you should integrate them:  &lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Interconnect tools&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sync communications in one place&lt;/strong&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Interconnect tools
&lt;/h3&gt;

&lt;p&gt;Connecting tools takes effort initially, but once you establish a solid pipeline, everything falls into place.  &lt;/p&gt;

&lt;h3&gt;
  
  
  Sync communications in one place
&lt;/h3&gt;

&lt;h3&gt;
  
  
  A bug in production?
&lt;/h3&gt;

&lt;h3&gt;
  
  
  A new release?
&lt;/h3&gt;

&lt;h3&gt;
  
  
  A successful code review?
&lt;/h3&gt;

&lt;p&gt;These questions demand immediate answers. What if there's a breaking change in production? Your team must be aligned to act ASAP.  &lt;/p&gt;

&lt;p&gt;A new release? Alignment on company goals and achievements becomes critical.  &lt;/p&gt;

&lt;p&gt;A passed review? Developers need real-time visibility into their code's progression: dev → staging → production.  &lt;/p&gt;

&lt;h3&gt;
  
  
  How we did it
&lt;/h3&gt;

&lt;p&gt;At InfinitCode.ai, we've launched a feature that lets you connect communication tools like Discord and Slack to receive PR reviews and code change notifications in one place.  &lt;/p&gt;

&lt;p&gt;While our AI agent handles initial reviews (followed by senior developers), you can focus on other tasks and simply monitor your communication tools.  &lt;/p&gt;

&lt;p&gt;For example, connecting Discord is straightforward:  &lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Edit your channel
&lt;/li&gt;
&lt;li&gt;Navigate to Integrations
&lt;/li&gt;
&lt;li&gt;Create a new webhook
&lt;/li&gt;
&lt;li&gt;Copy the Webhook URL
&lt;/li&gt;
&lt;li&gt;Paste it into &lt;a href="https://infinitcode.ai/" rel="noopener noreferrer"&gt;Infinitcode.ai&lt;/a&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Then create your new integration and you're set!&lt;/p&gt;

&lt;p&gt;While maintaining productivity you synchronise your team and you set your goals straight&lt;/p&gt;

&lt;p&gt;I would ❤️ to hear how you do it in your team?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>productivity</category>
      <category>vibecoding</category>
      <category>programming</category>
    </item>
    <item>
      <title>How We Launched 10x Faster in Production</title>
      <dc:creator>Gentian Elmazi</dc:creator>
      <pubDate>Thu, 15 May 2025 22:03:43 +0000</pubDate>
      <link>https://dev.to/gentos/how-we-launched-10x-faster-in-production-4fed</link>
      <guid>https://dev.to/gentos/how-we-launched-10x-faster-in-production-4fed</guid>
      <description>&lt;p&gt;Hi everyone! I’m &lt;strong&gt;Gentian Elmazi&lt;/strong&gt;, a software engineer with over ten years of experience and co-founder of &lt;a href="http://infinitcode.com/" rel="noopener noreferrer"&gt;Infinitcode.com&lt;/a&gt; and I am starting the first #buildinpublic series. At our company, we partner with businesses across industries—outsourcing the development of web applications powered by deep tech like AI, NLP, blockchain and so on.&lt;/p&gt;




&lt;h2&gt;
  
  
  Our Established Standards
&lt;/h2&gt;

&lt;p&gt;From day one, we’ve enforced &lt;strong&gt;maintainable&lt;/strong&gt;, &lt;strong&gt;readable&lt;/strong&gt;, and &lt;strong&gt;scalable&lt;/strong&gt; code. We adopt layered architectural patterns with dependency injection for modularity and testability. For source control, we follow &lt;strong&gt;GitHub Flow&lt;/strong&gt;:  &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;feature/*&lt;/code&gt; branch
&lt;/li&gt;
&lt;li&gt;→ Pull request
&lt;/li&gt;
&lt;li&gt;→ Peer review
&lt;/li&gt;
&lt;li&gt;→ Merge into &lt;code&gt;dev&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;→ Production release
&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  The Bottleneck We Hit
&lt;/h2&gt;

&lt;p&gt;As our client base and project scope grew, our senior engineers spent roughly &lt;strong&gt;40%&lt;/strong&gt; of their time on code reviews. Constantly context-switching across multiple repositories began to erode our strict standards—and that led to production issues we simply couldn’t ignore.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Promise (and Pitfalls) of AI
&lt;/h2&gt;

&lt;p&gt;When AI assistants promised &lt;strong&gt;30–40%&lt;/strong&gt; productivity boosts, we were eager to adopt them. Yet out-of-the-box AI snippets often:  &lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Violated our company rules
&lt;/li&gt;
&lt;li&gt;Introduced inconsistent patterns
&lt;/li&gt;
&lt;li&gt;Missed critical edge cases
&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  Piloting &lt;a href="http://infinitcode.ai/" rel="noopener noreferrer"&gt;Infinitcode.ai&lt;/a&gt;’s Code Reviewer
&lt;/h2&gt;

&lt;p&gt;We decided to take a leap of faith and built an internal AI code-reviewer—now in public alpha as &lt;strong&gt;Infinitcode.ai&lt;/strong&gt;—to help streamline our workflow. Within days, we saw:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;35% Productivity Gain&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Automated PR summaries and inline suggestions let senior engineers focus on high-value reviews, shrinking review cycles from days to hours.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;30% Performance Improvement&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
The AI flagged inefficient loops and unnecessary computations that we’d normally catch only after profiling in production.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;15+ Security Bugs Caught&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Critical vulnerabilities surfaced early in pull requests, not weeks after deployment.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;120+ Typos &amp;amp; Style Violations Fixed&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Consistent code formatting and improved documentation boosted overall readability.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Example Security Fix
&lt;/h3&gt;

&lt;blockquote&gt;
&lt;p&gt;⚠️ &lt;strong&gt;Risk&lt;/strong&gt;: Non-cryptographic &lt;code&gt;UUIDv4&lt;/code&gt; generation in bulk operations risked collisions under high-concurrency loads.&lt;br&gt;&lt;br&gt;
🔧 &lt;strong&gt;Fix&lt;/strong&gt;: Implemented &lt;code&gt;crypto.randomUUID()&lt;/code&gt; with batch-safe collision checks, ensuring unique identifiers even when processing thousands of records per second.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Even with a decade of hands-on coding, I likely would’ve missed this subtle bug until it hit production—so having AI catch it early was truly a game-changer.&lt;/p&gt;

&lt;p&gt;The charts below illustrate the 35% productivity and 30% performance improvements we achieved—plus the dozens of security bugs and 120+ typos our AI reviewer caught—demonstrating its measurable impact on our workflow&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%2Fhbsbluum4hyzx02fs9xw.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%2Fhbsbluum4hyzx02fs9xw.png" alt="AI Code Reviewer impact in Productivity and Performance" width="554" height="325"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&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%2Fj8ac21s85e4p5d69zekt.png" alt="Issues detected by AI code reviewer" width="573" height="330"&gt;
&lt;/h2&gt;

&lt;h2&gt;
  
  
  Key Features That Helped Us
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Multi-Model Integration&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
DeepSeek’s backbone matched our use cases, letting us switch models as needed.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Custom Rulesets&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Uploading our linting and security policies ensured AI suggestions aligned perfectly with our coding standards.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Rapid Support &amp;amp; Iteration&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Working directly with the team allowed us to fine-tune the tool within hours, not weeks.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Lessons Learned &amp;amp; Next Steps
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;AI Empowers, Doesn’t Replace&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Developers remain central—AI handles routine checks so humans tackle design and architecture.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Iterate on Your Rules&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Continuously refine your AI’s rulesets and model settings as your codebase evolves.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Measure &amp;amp; Visualize&lt;/strong&gt;&lt;br&gt;&lt;br&gt;
Track metrics (productivity gains, bug catch rate, review times) to demonstrate ROI and keep stakeholders aligned.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;




&lt;p&gt;I’d love to hear how AI is reshaping your code reviews—share your experiences or questions in the comments below!&lt;/p&gt;

&lt;p&gt;As well feel free to try &lt;a href="http://infinitcode.ai/" rel="noopener noreferrer"&gt;Infinitcode.ai&lt;/a&gt; in alpha stage. Your feedback is greatly appreciated &lt;/p&gt;

</description>
      <category>webdev</category>
      <category>productivity</category>
      <category>ai</category>
      <category>vibecoding</category>
    </item>
  </channel>
</rss>
