<?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: Manoj Kumar</title>
    <description>The latest articles on DEV Community by Manoj Kumar (@manoj-kumar).</description>
    <link>https://dev.to/manoj-kumar</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%2F2675913%2Fd95e96bf-6635-4ad3-a17b-af9a6480a71a.jpg</url>
      <title>DEV Community: Manoj Kumar</title>
      <link>https://dev.to/manoj-kumar</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/manoj-kumar"/>
    <language>en</language>
    <item>
      <title>The Two Failure Paths of a Software Developer</title>
      <dc:creator>Manoj Kumar</dc:creator>
      <pubDate>Sat, 10 Jan 2026 15:56:28 +0000</pubDate>
      <link>https://dev.to/manoj-kumar/the-two-failure-paths-of-a-software-developer-1fg7</link>
      <guid>https://dev.to/manoj-kumar/the-two-failure-paths-of-a-software-developer-1fg7</guid>
      <description>&lt;p&gt;Beyond building the wrong thing or building it wrong, are there other ways software developers fail?&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.linkedin.com/pulse/two-failure-paths-manoj-kumar-9umsc/" rel="noopener noreferrer"&gt;My LinkedIn Article&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
    </item>
    <item>
      <title>Sample Project for Quartz.NET Tutorials</title>
      <dc:creator>Manoj Kumar</dc:creator>
      <pubDate>Sun, 22 Jun 2025 05:32:17 +0000</pubDate>
      <link>https://dev.to/manoj-kumar/sample-project-for-quartznet-tutorials-4oij</link>
      <guid>https://dev.to/manoj-kumar/sample-project-for-quartznet-tutorials-4oij</guid>
      <description>&lt;p&gt;A demonstration project showcasing how to schedule jobs (tasks or pieces of work) to run at specified times or intervals, similar to how Windows Task Scheduler or cron jobs work using Quartz.NET an open-source, full-featured job scheduling library for .NET applications.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/manojkumar-jmp/explore-quartz" rel="noopener noreferrer"&gt;https://github.com/manojkumar-jmp/explore-quartz&lt;/a&gt;&lt;/p&gt;

</description>
      <category>dotnet</category>
      <category>aspdotnet</category>
      <category>howto</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Indicator to do better software design</title>
      <dc:creator>Manoj Kumar</dc:creator>
      <pubDate>Thu, 09 Jan 2025 16:43:20 +0000</pubDate>
      <link>https://dev.to/manoj-kumar/indicator-to-do-better-software-design-4pad</link>
      <guid>https://dev.to/manoj-kumar/indicator-to-do-better-software-design-4pad</guid>
      <description>&lt;p&gt;If your answered yes to any of below questions, it's time to do better software design.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Is your code difficult to make changes?&lt;/li&gt;
&lt;li&gt;Did a small code change produce a ripple-effect for changes elsewhere in the code? &lt;/li&gt;
&lt;li&gt;Is your code hard to reuse? &lt;/li&gt;
&lt;li&gt;Is the software difficult to maintain after a release? &lt;/li&gt;
&lt;li&gt;Is difficult to express ideas for your software with other developers, other teams, and your clients.&lt;/li&gt;
&lt;li&gt;Is it difficult to write Unit test.&lt;/li&gt;
&lt;/ol&gt;

</description>
      <category>softwaredevelopment</category>
    </item>
    <item>
      <title>The goal of software architecture</title>
      <dc:creator>Manoj Kumar</dc:creator>
      <pubDate>Wed, 08 Jan 2025 14:51:35 +0000</pubDate>
      <link>https://dev.to/manoj-kumar/the-goal-of-software-architecture-470</link>
      <guid>https://dev.to/manoj-kumar/the-goal-of-software-architecture-470</guid>
      <description>&lt;p&gt;The goal of software architecture is to minimize the human resources required to build and maintain the required system.&lt;/p&gt;

&lt;p&gt;The measure of design quality is simply the measure of the effort required to meet the needs of the customer. If that effort is low, and stays low throughout the lifetime of the system, the design is good. If that effort grows with each new release, the design is bad. It’s as simple as that.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
