<?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 Hamed Shirbandi on Medium]]></title>
        <description><![CDATA[Stories by Hamed Shirbandi on Medium]]></description>
        <link>https://medium.com/@hamed.shirbandi?source=rss-2a06b8c537a3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YddRUk-szEQzMdoX32-M3Q@2x.jpeg</url>
            <title>Stories by Hamed Shirbandi on Medium</title>
            <link>https://medium.com/@hamed.shirbandi?source=rss-2a06b8c537a3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:50:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hamed.shirbandi/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[How to Find a Good SaaS Idea (and Actually Validate It)]]></title>
            <link>https://medium.com/@hamed.shirbandi/how-to-find-a-good-saas-idea-and-actually-validate-it-30ca7f6d6740?source=rss-2a06b8c537a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/30ca7f6d6740</guid>
            <category><![CDATA[solopreneur]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Hamed Shirbandi]]></dc:creator>
            <pubDate>Thu, 07 May 2026 19:29:05 GMT</pubDate>
            <atom:updated>2026-05-10T10:51:33.259Z</atom:updated>
            <content:encoded><![CDATA[<p>Most advice about starting a SaaS says you should “validate your idea” before writing any code. That sounds easy in theory, but anyone who has tried it knows it is often much harder than it sounds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*R50Sp0P4cMveiQzW.jpg" /></figure><h3>What People Usually Say About Validation</h3><p>The usual advice looks something like this:</p><ul><li>Create a waiting list and see who signs up</li><li>Launch a simple landing page</li><li>Run surveys and collect feedback</li><li>Ask friends, online communities, or strangers what they think</li></ul><p>These methods are not useless, but they often do not give clear answers when you are working on a brand-new idea.</p><p>Another problem people rarely talk about is how difficult it actually is to get feedback in the first place.</p><p>Most new founders do not already have an audience, a community, or hundreds of followers waiting to test their ideas. In reality, when you post a survey or launch a waiting list, you often get very little response. Sometimes almost none at all. That can feel discouraging and make you think your idea is bad, even when it might not be.</p><p>Today, people also sign up for many different reasons. Some are curious. Some want to support you. Some just enjoy trying new things. That does not always mean they would actually pay for your product later.</p><p>The same thing happens with feedback. People are often polite, vague, or simply not your target audience.</p><p>The biggest issue is this: if the feedback is not coming from the kind of person who would truly become a paying customer, it usually does not help you make better decisions.</p><p>The good news is that there are ways to overcome this problem, even if you are starting with no audience at all. I will cover some practical strategies for that in future articles.</p><h3>The Problem With Brand-New Ideas</h3><p>If you are building something completely new, getting honest feedback before launch can be very difficult.</p><p>You can easily spend months building prototypes, collecting sign-ups, and chasing validation without ever knowing if the idea has real demand. For solo founders, that is a big risk and often a huge waste of time.</p><h3>A Safer Approach: Follow What Is Already Working</h3><p>Instead of trying to invent something completely new from scratch, a safer approach is to learn from products that are already succeeding.</p><p>Here is a simple way to do it:</p><ol><li><strong>Study products that already work.</strong> Look for SaaS apps with active users and clear signs of revenue.</li><li><strong>Find the gaps and frustrations.</strong> Use these products yourself. Read reviews, feature requests, and customer complaints. What are users still unhappy about?</li><li><strong>Build a smaller and more focused version.</strong> Solve one specific problem better, simpler, or for a more specific group of people.</li></ol><p>When similar businesses are already making money, you know there is demand. You are entering a proven market instead of guessing.</p><h3>Where to Find Successful SaaS Ideas</h3><p>If you are not sure where to look, here are a few practical places to start:</p><ul><li><strong>Browse SaaS marketplaces and directories.</strong> Websites like Product Hunt, Indie Hackers, and AppSumo are full of real SaaS products with user feedback.</li><li><strong>Follow founders building in public.</strong> Many solo founders openly share their revenue, growth, and lessons on X (formerly Twitter), LinkedIn, or personal blogs.</li><li><strong>Read founder interviews and startup stories.</strong> Communities like Indie Hackers and websites like Starter Story publish detailed stories from SaaS creators.</li><li><strong>Join niche communities.</strong> Reddit groups, Discord servers, LinkedIn communities, and industry forums are great places to see what people complain about or recommend.</li><li><strong>Watch for “What tools do you pay for?” discussions.</strong> These conversations often reveal which products people truly value.</li></ul><p>The key is to look for patterns. Are people repeating the same complaints? Is a certain group being ignored? Are users asking for features that nobody has built yet?</p><p>Those are often the best opportunities.</p><h3>Keep the Idea Small</h3><p>One of the biggest mistakes founders make is building too much too early.</p><p>You do not need a huge vision on day one. Start with something small enough that you can design, build, launch, and market it by yourself within a month or two.</p><p>Keeping the scope small helps you avoid endless planning and gets you in front of real users faster.</p><p>This approach works especially well for solopreneurs and indie SaaS builders. If you want to learn more about why building solo can be such a strong advantage, check out <a href="https://codeblock.dev/blog/post/who-is-a-solopreneur">Who Is a Solopreneur? (And Why They Fit the SaaS Revolution)</a> and <a href="https://codeblock.dev/blog/post/who-is-a-saas-builder">Who Is a SaaS Builder? (And Why You Could Be One)</a>.</p><h3>Why Building Solo Works So Well</h3><ul><li>You can start immediately without convincing investors or cofounders</li><li>You can change direction quickly if needed</li><li>Smaller projects are easier to finish and launch</li><li>Every hour you spend building helps you learn what real users actually want</li></ul><h3>Real Example: How I Built “Hey It’s Me” by Combining Proven Ideas</h3><p>Here is how I personally used this approach to launch my SaaS app, <a href="https://hey-it-is.me/">Hey It’s Me</a>.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FeaXKPKcNw7I%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DeaXKPKcNw7I&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FeaXKPKcNw7I%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/14c5bbed503345be58e4b8b091e02ae7/href">https://medium.com/media/14c5bbed503345be58e4b8b091e02ae7/href</a></iframe><p>While exploring SaaS opportunities, I noticed that AI image generator apps were growing very quickly. Many founders were openly sharing impressive revenue numbers from simple tools that allowed users to create AI-generated images.</p><p>I did not discover this through news articles or trend reports. I found it by following SaaS founders on X (formerly Twitter), where many people share their projects, revenue screenshots, and growth updates publicly. This gave me real proof that users were willing to pay for these kinds of products.</p><p>At the same time, I noticed that “link in bio” tools like <a href="https://linktr.ee/">Linktree</a> had become extremely popular among creators and online professionals. These tools were already widely used, and the demand was clearly proven.</p><p>That gave me an idea.</p><p>What if users could create a personal page, but instead of manually writing everything themselves, they could chat with an AI that asks questions, generates interesting facts about them, and even creates unique AI-generated images for each fact?</p><p>The result became a shareable personal mini-site filled with AI-generated visuals, analytics, privacy controls, and a modern design. You can see it at <a href="https://hey-it-is.me/">hey-it-is.me</a> or explore the sample pages.</p><p>This was not a random guess. I combined two ideas that were already working well:</p><ul><li>AI image generation apps with proven demand</li><li>Link-in-bio tools with strong user adoption</li></ul><p>Instead of inventing a completely new market, I added a fresh twist to two proven ideas.</p><p>And because I built it solo using the <a href="https://codeblock.dev/">CodeBlock SaaS DevKit</a>, I was able to launch much faster while keeping full control over the product and development process.</p><p>If you want to learn how DevKit can help you launch your own SaaS faster, visit <a href="https://codeblock.dev/">codeblock.dev</a>.</p><h3>Final Checklist for Your Next SaaS Idea</h3><ol><li><strong>Start with a proven market.</strong> Look for products that already have paying users.</li><li><strong>Choose a smaller niche.</strong> Focus on a specific audience or a more specific problem.</li><li><strong>Keep the scope simple.</strong> Focus on solving one important problem well.</li><li><strong>Build something you can launch alone.</strong> Aim for a product you can finish within 4–8 weeks.</li><li><strong>Learn from real users after launch.</strong> Pay attention to how people actually use the product.</li></ol><p>If you follow this approach, you will have a much better chance of building something people truly want-and are willing to pay for.</p><p><em>Originally published at </em><a href="https://codeblock.dev/blog/post/how-to-find-a-good-saas-idea-and-actually-validate-it"><em>https://codeblock.dev</em></a><em> on May 7, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30ca7f6d6740" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who Is a Solopreneur? (And Why They Fit the SaaS Revolution)]]></title>
            <link>https://medium.com/@hamed.shirbandi/who-is-a-solopreneur-and-why-they-fit-the-saas-revolution-493171d48bcd?source=rss-2a06b8c537a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/493171d48bcd</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[solopreneur]]></category>
            <category><![CDATA[solopreneurship]]></category>
            <dc:creator><![CDATA[Hamed Shirbandi]]></dc:creator>
            <pubDate>Sun, 03 May 2026 16:21:58 GMT</pubDate>
            <atom:updated>2026-05-07T11:17:19.416Z</atom:updated>
            <content:encoded><![CDATA[<p>Ever wonder who is behind so many of the creative tools, apps, and businesses popping up online? Often, it is not a team of executives with big funding. It is a solopreneur. But what exactly does that mean, and why are solopreneurs driving so much of today’s SaaS boom?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rOgBuNDxGJ5gPiiI.jpg" /></figure><h3>What Is a Solopreneur?</h3><p>A <strong>solopreneur</strong> is someone who starts and runs a business single-handedly. That means no cofounders, no staff, and no board meetings. Just you, your ideas, and your willingness to learn and build.</p><p>Solopreneurs:</p><ul><li>Wear every hat: builder, marketer, support agent, tester, and CEO.</li><li>Value freedom, flexibility, and full control over their schedule.</li><li>Launch businesses that scale online, often using technology and automation to do the work of a whole team.</li></ul><p>If you want to see how solopreneurship can look in practice, check out <a href="https://codeblock.dev/blog/post/who-is-a-saas-builder">Who Is a SaaS Builder? (And Why You Could Be One)</a>. Many SaaS builders are actually solopreneurs, launching their first product solo.</p><h3>The Modern Solopreneur’s Toolkit: SaaS and No-Code</h3><p>What makes this path possible today? Mostly, the rise of powerful tools you can use without a huge team-including SaaS platforms you can plug into your business, as well as ready-made SaaS templates.</p><p>In fact, countless solopreneurs have built amazing apps just by assembling the right tools, connecting online services, or leveraging templates like <a href="https://codeblock.dev/">CodeBlock DevKit</a> to speed up jump from idea to launch.</p><h3>Why SaaS is Perfect for Solopreneurs</h3><p>SaaS (Software as a Service) is an ideal business model for people going solo:</p><ul><li>Build once, sell to many.</li><li>Recurring revenue, not just one-off sales.</li><li>Scale globally, with automated signups and support.</li><li>Focus more on value delivered, less on physical inventory.</li></ul><p>If you can spot a problem and package up the solution as a SaaS, you have the makings of a solopreneur success story.</p><h3>Rules and Mindsets for Solopreneurs</h3><p>Thriving as a solopreneur takes a clear mindset and a few simple rules:</p><p><strong>1. Ruthlessly prioritize your time.</strong></p><ul><li>Ask whether each task moves your business closer to launch or profit.</li><li>Automate or drop everything you do not need to do yourself.</li></ul><p><strong>2. Ship before you feel ready.</strong></p><ul><li>Aim to launch a “minimum sellable version.” Get feedback fast.</li><li>Perfectionism is the enemy of progress for solo founders.</li></ul><p><strong>3. Learn by doing, not by waiting.</strong></p><ul><li>Everything you need to know is learnable. The best lessons come once you have users.</li></ul><p><strong>4. Stay resourceful.</strong></p><ul><li>Use SaaS products and ready-made templates as leverage. <a href="https://codeblock.dev/">CodeBlock DevKit</a> can save you months of groundwork if you are building a SaaS in .NET.</li></ul><p><strong>5. Build habits, not just products.</strong></p><ul><li>Consistency, working a bit every day or week, almost always beats “motivation”.</li></ul><p><strong>6. Remember, you are in charge.</strong></p><ul><li>You set your own rules, pace, and priorities.</li></ul><h3>Connected: Solopreneurs, SaaS, and the Builder’s Journey</h3><p>Solopreneurs and SaaS are deeply linked. Many of the world’s best-known solo founders got their start by building a simple SaaS product. If you are curious about building and launching your own SaaS, or just want to see what the journey is like, dive into our guide to <a href="https://codeblock.dev/blog/post/who-is-a-saas-builder">Who Is a SaaS Builder? (And Why You Could Be One)</a>.</p><h3>Final Takeaway</h3><p>Solopreneurs show that big impact does not require a big team. With modern SaaS tools, the right mindset, and a willingness to ship small and learn fast, you can launch a product and grow a business entirely on your own.</p><p><em>Originally published at </em><a href="https://codeblock.dev/blog/post/who-is-a-solopreneur-and-why-they-fit-the-saas-revolution"><em>https://codeblock.dev</em></a><em> on May 3, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=493171d48bcd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who Is a SaaS Builder? (And Why You Could Be One)]]></title>
            <link>https://medium.com/@hamed.shirbandi/who-is-a-saas-builder-and-why-you-could-be-one-9f97c48a5505?source=rss-2a06b8c537a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f97c48a5505</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[devkit]]></category>
            <category><![CDATA[solopreneur]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Hamed Shirbandi]]></dc:creator>
            <pubDate>Sun, 03 May 2026 15:53:24 GMT</pubDate>
            <atom:updated>2026-05-06T09:25:05.606Z</atom:updated>
            <content:encoded><![CDATA[<p>What if you could build a software product, launch it online, and get paid by people all over the world, sometimes even while you sleep? This is the promise of SaaS. The people making it happen are known as SaaS builders. But who are they, really? And could you be one?</p><p>Let’s break it down, step by step. No jargon, no gatekeeping.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qAn8brwLo-DBTYPd.jpg" /></figure><h3>What Does “SaaS Builder” Mean?</h3><p>If you’re not familiar with SaaS yet, start by reading <a href="https://codeblock.dev/blog/post/what-is-saas-a-simple-guide-with-a-real-example">What Is SaaS? A Simple Guide (With a Real Example)</a> for a friendly introduction.</p><p><strong>SaaS</strong> stands for <strong>Software as a Service</strong>: digital products you use online, directly in your web browser, instead of as something you download and install.</p><p>A <strong>SaaS builder</strong> is anyone who creates one of these products. They’re the people behind your favorite online productivity tools, note apps, website builders, and even AI-powered platforms. For example, <a href="https://hey-it-is.me/">Hey It Is Me</a> is a SaaS app that I vibe coded in about a month, using AI and building on top of <a href="https://codeblock.dev/">CodeBlock DevKit</a>.</p><p>But a SaaS builder is not just a coder. They are problem-solvers, creators, and sometimes full-blown entrepreneurs.</p><h3>Who Are SaaS Builders? (Hint: Not Just Programmers)</h3><ul><li><strong>Solo developers</strong> who want to escape freelancer “hourly rates” and earn from something they control.</li><li><strong>Small teams</strong> of friends or ex-coworkers who spot a problem and decide to build a solution.</li><li><strong>Designers</strong> who learn enough tech to launch their own product.</li><li><strong>Domain experts</strong>-teachers, marketers, accountants-who team up with developers to build tools for their industry.</li><li><strong>Anyone</strong> curious enough to learn, experiment, and turn an idea into reality.</li></ul><p>All you really need to get started is:</p><ul><li>A real-life problem worth solving.</li><li>Willingness to learn (even if you’re not a “tech person” yet).</li><li>A drive to see something through.</li></ul><h3>What Makes SaaS Building Different?</h3><p>Launching a SaaS isn’t just about coding. The real work is making something <strong>people want to use</strong> -and that they’ll pay for.</p><p>Here’s what SaaS builders do:</p><ul><li><strong>Find real problems:</strong> Listen for pain points, bottlenecks, or time-wasters in everyday life or work.</li><li><strong>Design simple solutions:</strong> Create an app that solves it with as little friction as possible.</li><li><strong>Ship early:</strong> Put the product in real users’ hands, even if it’s not “perfect.”</li><li><strong>Learn and improve:</strong> Watch how users behave, listen to feedback, and rapidly improve the app.</li><li><strong>Handle the foundations:</strong> Authentication, payments, user management, and keeping the site running reliably (using kits like <a href="https://codeblock.dev/">CodeBlock DevKit</a> massively speeds up this part).</li></ul><h3>You Don’t Need to Be a Genius (Or Have a Big Team)</h3><p>Most SaaS products start small and simple. Many are built by just one person or a tiny group with part-time hours. There are stories everywhere of teachers, designers, and indie hackers launching SaaS products, some as side projects that grow into full businesses.</p><p>What matters most?</p><ul><li>Willingness to learn as you go. Most SaaS builders figure things out one step at a time.</li><li>Curiosity about users: understanding what <em>really</em> helps people.</li><li>Patience and persistence: successful builders often fail (a few times) before landing on the right idea.</li></ul><h3>Why Become a SaaS Builder?</h3><ul><li><strong>Freedom:</strong> You decide what to build, when to work, and what to try next.</li><li><strong>Scalability:</strong> Launch once; serve dozens, hundreds, or thousands of users, without working more hours.</li><li><strong>Learning:</strong> It’s the fastest way to learn modern product skills (tech, design, customer discovery-all at once).</li><li><strong>Earning potential:</strong> While it’s not “get rich overnight,” a single SaaS can provide side income-or grow into your main job.</li></ul><h3>How Can You Start?</h3><ol><li><strong>Explore problems:</strong> What do you wish worked better? What do others complain about?</li><li><strong>Learn the basics:</strong> You don’t need to be a pro-a foundation or template can cover most of the “hard,” repetitive parts (see <a href="https://codeblock.dev/blog/post/how-to-build-a-production-ready-saas-in-net">How to Build a Production-Ready SaaS in .NET</a>).</li><li><strong>Build a tiny version:</strong> Just enough to test if people care.</li><li><strong>Share it:</strong> With friends, online communities, or people with that problem.</li><li><strong>Iterate:</strong> Tweak, fix, and grow-based on how people actually use your product.</li></ol><h3>Final Thought</h3><p>A SaaS builder is a <strong>doer</strong>, someone who turns problems into products, often starting from little more than curiosity and persistence. If you’ve ever thought, <em>“I wish someone made an app for that…”</em>, maybe the next SaaS builder could be you.</p><p><em>Originally published at </em><a href="https://codeblock.dev/blog/post/who-is-a-saas-builder-and-why-you-could-be-one"><em>https://codeblock.dev</em></a><em> on May 3, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f97c48a5505" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Is SaaS? A Simple Guide (With a Real Example)]]></title>
            <link>https://medium.com/@hamed.shirbandi/what-is-saas-a-simple-guide-with-a-real-example-f8f066619fb3?source=rss-2a06b8c537a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8f066619fb3</guid>
            <category><![CDATA[devkit]]></category>
            <category><![CDATA[solopreneur]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Hamed Shirbandi]]></dc:creator>
            <pubDate>Sun, 03 May 2026 08:34:21 GMT</pubDate>
            <atom:updated>2026-05-03T10:14:14.404Z</atom:updated>
            <content:encoded><![CDATA[<p>You’ve probably used a SaaS today without realizing it.</p><p>No technical background required. No complicated terms. Just a simple explanation of what SaaS is, how it works, and why so many people are building them.</p><p>By the end, you might even start thinking:</p><blockquote><em>“Wait… could I build one too?”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*D5h1eIQNts9zREHb.jpg" /></figure><h3>Start With Something Simple</h3><p>Before we explain SaaS, let’s start even simpler.</p><p>A <strong>website</strong> is something you visit. You open a link, and you read or watch something.</p><p>A <strong>web application</strong> is different. It <em>does something for you</em>.</p><ul><li>You sign in</li><li>You create or save something</li><li>You interact with it</li></ul><p>Think of dashboards, tools, or platforms you log into.</p><p>Now we’re ready for SaaS.</p><h3>So What Is SaaS?</h3><p><strong>SaaS</strong> stands for <strong><em>Software as a Service</em></strong>.</p><p>That sounds technical, but it’s actually very simple:</p><blockquote><em>SaaS is software you use online, instead of installing on your computer.</em></blockquote><p>You don’t download it.<br> You don’t manage it.<br> You just open it in your browser and use it.</p><p>Usually, you:</p><ul><li>create an account</li><li>use the product online</li><li>and sometimes pay monthly or yearly</li></ul><p>That’s it.</p><h3>A Simple Way to Think About It</h3><p>Instead of selling software once, SaaS is about:</p><blockquote><em>Building one product and letting many people use it online.</em></blockquote><p><strong>The creator</strong>:</p><ul><li>runs the servers</li><li>updates the product</li><li>improves it over time</li></ul><p><strong>The user</strong>:</p><ul><li>just logs in and uses it</li></ul><h3>A Real Example: Hey It Is Me</h3><p>Let’s make this real.</p><p><a href="https://hey-it-is.me/"><strong>Hey It Is Me</strong></a> is a SaaS product.</p><p>It lets you create your own personal page where you share facts about yourself, along with AI-generated images.</p><p>Here’s how it works:</p><ol><li>You sign up</li><li>You create your page</li><li>The system helps generate content using AI</li><li>You get a unique link to share with others</li></ol><p>Now you have your own online identity page.</p><p><strong>Why this is SaaS:</strong></p><ul><li>You don’t install anything</li><li>Everything runs online</li><li>Your data is saved in your account</li><li>The product works for many users at the same time</li><li>There are free and paid plans-upgrade to unlock more features</li></ul><p>This is exactly what SaaS looks like in real life.</p><h3>Why People Are Excited About SaaS</h3><p>Now here’s where it gets interesting.</p><p>From the outside, SaaS might look like just another app.</p><p>But for builders, it’s different.</p><h3>1. Build Once, Many People Use It</h3><p>You don’t create a new product for every customer.</p><p>You build it once, and users sign up.</p><h3>2. You Can Start Small</h3><p>You don’t need a big team.</p><p>Many SaaS products are started by:</p><h3>3. It Doesn’t Take Years</h3><p>If you focus, reuse the right tools, and avoid overbuilding:</p><blockquote><em>You can launch a real SaaS in weeks, not years.</em></blockquote><p>Sometimes, even in about a month.</p><h3>4. Low Initial Cost</h3><p>You don’t need:</p><p>You just need a little time, consistency, and one good idea.</p><p>That’s why so many developers and creators are exploring SaaS.</p><h3>So… Can You Build One?</h3><p>This is the real question.</p><p>And the honest answer is:</p><blockquote><em>Yes. But not by starting from zero every time.</em></blockquote><p>Because a SaaS is not just your idea.</p><p>It also needs:</p><ul><li>authentication (login, signup)</li><li>payments and subscriptions</li><li>admin tools</li><li>user management</li><li>and more</li></ul><p>That’s where most time goes.</p><h3>A Smarter Way to Build</h3><p>Instead of building everything from scratch, many developers use a foundation.</p><p>That’s exactly what <a href="https://codeblock.dev/"><strong>CodeBlock DevKit</strong></a> is for.</p><p>It gives you the core parts of a SaaS:</p><ul><li>authentication</li><li>admin panel</li><li>pricing and subscriptions</li><li>and other essential modules</li></ul><p>So instead of spending weeks on setup, you focus on:</p><blockquote><em>your idea, your product, your users</em></blockquote><h3>What Comes Next?</h3><p>This article is just the starting point.</p><p>In future articles, we’ll go deeper into things like:</p><ul><li>Who builds SaaS products?</li><li>How do you find a good SaaS idea?</li><li>How do you get users after launch?</li><li>How do you price your SaaS?</li><li>How do you make money from it?</li></ul><h3>Final Takeaway</h3><p>SaaS is simply:</p><blockquote><em>Software you use online, built once, and used by many people.</em></blockquote><p>You’ve already used it.</p><p>Now you understand it.</p><p>The next step?</p><p>Maybe… you build one.</p><p><em>Originally published at </em><a href="https://codeblock.dev/blog/post/what-is-saas-a-simple-guide-with-a-real-example"><em>https://codeblock.dev</em></a><em> on May 3, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8f066619fb3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SaaS Foundations: The Hidden Work Behind a Real Product]]></title>
            <link>https://medium.com/@hamed.shirbandi/saas-foundations-the-hidden-work-behind-a-real-product-d670432adc1c?source=rss-2a06b8c537a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/d670432adc1c</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[solopreneur]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Hamed Shirbandi]]></dc:creator>
            <pubDate>Thu, 23 Apr 2026 19:39:53 GMT</pubDate>
            <atom:updated>2026-05-03T10:18:22.245Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s not your idea that slows SaaS projects down, it’s everything you have to build around it before real users can use, trust, and pay for your product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BPsFJp1JTIk2Nje8.jpg" /></figure><blockquote><em>If you’re new to the concept of SaaS, start with </em><a href="https://codeblock.dev/blog/post/what-is-saas-a-simple-guide-with-a-real-example"><em>What is SaaS? A simple guide (with a real example)</em></a><em>.</em></blockquote><h3>What “Foundation” Really Means</h3><p>Your <strong>SaaS foundation</strong> is the minimum you absolutely need:</p><ul><li>User accounts, signup, and login</li><li>Role-based permissions and admin controls</li><li>Handling payments, plans, and subscriptions</li><li>Keeping the system running when (not if!) things break</li></ul><p>Most developers <em>dramatically</em> underestimate this work, until they try to launch.</p><h3>Four Critical Layers (Before Features)</h3><h4>1. User Access and Authentication</h4><p>Before building features, you need a rock-solid way for users to get into (and stay in) your product.<br> This means:</p><ul><li>Signup and login flows (email, password, social login, or magic links)</li><li>Email verification and password reset</li><li>Consistent session management</li></ul><p>If you get these wrong, you create endless support headaches.</p><h4>2. Admin Controls and Permissions</h4><p>As soon as you have users, you need to control who can do what.<br> You’ll need:</p><ul><li>Admin, staff, and customer roles</li><li>Permissions for sensitive actions (like billing or user management)</li><li>Internal tools for supporting users (changing their plans, applying discounts, seeing issues)</li></ul><p>Every feature you ever add, billing, content, integrations, depends on this working.</p><h4>3. Payments, Pricing, and Plans</h4><p>This is where your project turns into a business.<br> You need:</p><ul><li>Flexible plan and pricing tiers</li><li>Flows for users to subscribe, upgrade, downgrade, or cancel</li><li>Logic for real cases (failed payments, retries)</li><li>Instantly updating access when plans change</li></ul><p>Edge cases? Invoicing, refunds, double charges, changing discounts, these are not rare. They are <em>normal</em>.</p><h4>4. Monitoring and Reliability</h4><p>Once people depend on your product, <em>you</em> have to know what’s happening at all times.</p><p>Minimum baseline:</p><ul><li>Logs for debugging what went wrong</li><li>Health checks for your core systems</li><li>Visibility into background jobs (renewals, emails, billing runs)</li></ul><p>Without this, small issues snowball into disasters you cannot trace.</p><h3>What You Can (Usually) Delay</h3><p>Not everything has to be built on Day One. You can often postpone:</p><ul><li>Advanced analytics</li><li>Full localization</li><li>Rare payment methods</li><li>Deep product customization</li></ul><p>But anything to do with users, money, or reliability is mandatory from the start.</p><h3>The Hidden Realization</h3><p>Eventually, every SaaS builder realizes:<br> Building a SaaS is not just about your idea, it’s about <em>everything required to support that idea in real life</em>.</p><p>Authentication, permissions, billing logic, admin tools, monitoring. These aren’t “nice extras”, they’re essential before you can call your product usable.</p><h3>The Shortcut: Stand on Solid Foundations</h3><p>At this point you have two choices:</p><ol><li>Build all these foundations yourself</li><li>Use something that gives them to you</li></ol><p>A <strong>SaaS development kit</strong> is the shortcut every founder wishes they’d taken sooner.</p><p>For .NET SaaS, <a href="https://codeblock.dev/">CodeBlock DevKit</a> provides modules for:</p><ul><li>Authentication &amp; user management</li><li>Admin panel &amp; permissions</li><li>Pricing, payments, and subscriptions</li><li>Monitoring and health checks</li><li>Settings, licensing, and more</li></ul><p><strong>The key</strong>: these pieces work together as an actual application, not scattered code samples.</p><p>You start by focusing on your idea…<br> But you win by delivering everything else users expect.</p><h3>Closing: Why Foundations Matter</h3><p>Shipping a SaaS is not just about your core logic.<br> It’s about making that logic usable, manageable, and reliable for real users.</p><p>Once you see the full picture, you realize why so many products grind to a halt before they launch,<br> and why building on a solid foundation <em>changes everything</em>.</p><p><em>Originally published at </em><a href="https://codeblock.dev/blog/post/saas-foundations-the-hidden-work-behind-a-real-product"><em>https://codeblock.dev</em></a><em> on April 23, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d670432adc1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stripe Subscriptions in .NET SaaS: What You Actually Have to Build]]></title>
            <link>https://medium.com/@hamed.shirbandi/stripe-subscriptions-in-net-saas-what-you-actually-have-to-build-946ccd39a7ed?source=rss-2a06b8c537a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/946ccd39a7ed</guid>
            <category><![CDATA[solopreneur]]></category>
            <category><![CDATA[stripe]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Hamed Shirbandi]]></dc:creator>
            <pubDate>Tue, 14 Apr 2026 22:06:33 GMT</pubDate>
            <atom:updated>2026-05-03T10:21:30.007Z</atom:updated>
            <content:encoded><![CDATA[<p>Stripe can charge a card in a demo in one afternoon.<br> But building a <strong>real SaaS subscription system</strong> is something else entirely.</p><p>The real work is handling renewals, failed payments, refunds, edge cases, and support-keeping billing healthy in real life, not just in test mode.</p><p>This article zooms in on one part of SaaS almost everyone underestimates: <strong>subscriptions and billing with Stripe</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*34P7iaVJxmPPJZjM.jpg" /></figure><blockquote><em>If you’re new to SaaS, start with </em><a href="https://codeblock.dev/blog/post/what-is-saas-a-simple-guide-with-a-real-example"><em>What is SaaS? A simple guide (with a real example)</em></a></blockquote><h3>Why Stripe Integration Is Never “Just One Feature”</h3><p>At first, it feels simple:</p><blockquote><em>User picks a plan, pays, and gets access.</em></blockquote><p>But <strong>subscriptions are ongoing</strong>. After launch, you’ll need to handle:</p><ul><li>Successful and failed payments</li><li>Billing renewals</li><li>Upgrades/downgrades</li><li>Cancellations/reactivations</li><li>Refunds and disputes</li><li>Customer emails and notifications</li><li>Internal tools for support</li></ul><p>Stripe takes care of payments, but your application is responsible for everything that happens before, during, and after.</p><h3>What You Actually Need to Build</h3><p>Launching a real subscription SaaS means building more than simple API calls. Here’s what most real-world teams wind up implementing:</p><h4>1. Your Own Pricing and Subscription Model</h4><p>Stripe has products and prices, but your app defines what each plan means, what “active” means, what’s included, what’s limited, and what free trials (if any) look like.</p><h4>2. Mapping Users to Stripe Data</h4><p>Your system needs to reliably connect:</p><ul><li>Your user accounts</li><li>The Stripe customer</li><li>The subscription record</li></ul><p>If this mapping breaks-for example, if users pay before an account is made or switch email addresses-trust falls apart.</p><h4>3. Webhooks: The Source of Truth</h4><p>Never trust only the browser or post-payment redirect.<br><strong>Stripe webhooks</strong> are what actually matter.</p><p>To get this right, you’ll need to:</p><ul><li>Verify webhook signatures</li><li>Handle duplicate events and retries</li><li>Update your database in a consistent way</li><li>Trigger follow-up (emails, upgrades)</li></ul><p>If webhooks are unstable, your data will eventually get out of sync.<br> Users might see “active” while Stripe says “unpaid.”</p><h4>4. Admin and Support Tools</h4><p>Growth (and frustration) comes down to how quickly you can:</p><ul><li>Search users and subscriptions</li><li>Issue refunds safely</li><li>See full billing and support history</li><li>Investigate “what went wrong” errors</li></ul><p>If you skip these, every billing issue becomes a personal headache.</p><h3>Practical Checklist for Your First Version</h3><p>Use this checklist to scope your first launch:</p><p><strong>Customer Experience</strong> <strong>System Reliability</strong> <strong>Business Operations</strong></p><p>If this seems long, that’s why billing is the top reason for delays in SaaS launches.</p><h3>Should You Build All of This Yourself?</h3><p>The easy test:</p><blockquote><em>Is billing a true differentiator for your product, or just something users expect to work every time?</em></blockquote><p><strong>Build it yourself if:</strong></p><ul><li>You need complex, usage-based pricing</li><li>Advanced team/seat logic</li><li>Contracts with detailed, custom billing</li></ul><p><strong>But for most SaaS products?</strong><br> What you need is reliability and clarity for users.<br> Building everything from scratch is rarely worth it.</p><h3>A Faster Path With a Ready Foundation</h3><p>This is where <a href="https://codeblock.dev/"><strong>CodeBlock DevKit</strong></a> comes in.</p><p>Instead of reinventing billing, subscriptions, and admin tools, you get:</p><ul><li>Pricing and plan management</li><li>Stripe payment integration</li><li>Subscription lifecycle handling</li><li>Admin and user panels</li><li>Monitoring and tracking</li></ul><p>So you can focus on what actually makes your product valuable.</p><p>For technical details, visit the <a href="https://docs.codeblock.dev/">CodeBlock DevKit docs</a>.</p><h3>Mistakes to Avoid</h3><p>Save yourself hassle by avoiding these:</p><ul><li>Treating the success page as proof of payment</li><li>Skipping webhook retries and idempotency</li><li>Postponing admin tool development</li><li>Not tracking billing changes</li></ul><p>Avoiding these doesn’t guarantee overnight growth, but it does mean far fewer fires and angry users.</p><h3>What to Do Next</h3><p>Before you write code, nail down:</p><ol><li>Your subscription logic-plain English</li><li>Webhook events you’ll handle from day one</li><li>What actually happens when a payment fails</li><li>Admin panel must-haves (day one!)</li></ol><p>Just doing these can save you weeks later.</p><h3>Final Takeaway</h3><p>Stripe makes payments simple.<br> A real, healthy subscription system is the hard part.</p><p>If you want to launch a true SaaS, focus on your product, your users, your value-<br> and stand on a solid foundation for everything else.</p><p>That’s how you move from demo… to a real business.</p><p><em>Originally published at </em><a href="https://codeblock.dev/blog/post/stripe-subscriptions-in-net-saas-what-you-actually-have-to-build"><em>https://codeblock.dev</em></a><em> on April 14, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=946ccd39a7ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Build a Production-Ready SaaS in .NET]]></title>
            <link>https://medium.com/@hamed.shirbandi/how-to-build-a-production-ready-saas-in-net-561d8d55ae4a?source=rss-2a06b8c537a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/561d8d55ae4a</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[solopreneur]]></category>
            <category><![CDATA[devkit]]></category>
            <dc:creator><![CDATA[Hamed Shirbandi]]></dc:creator>
            <pubDate>Tue, 14 Apr 2026 21:50:06 GMT</pubDate>
            <atom:updated>2026-05-03T10:24:25.909Z</atom:updated>
            <content:encoded><![CDATA[<p>Building your SaaS isn’t hard because your idea is complicated.<br> It’s hard because of everything around your idea: authentication, payments, subscriptions, admin tools, monitoring, localization, deployment and more than you expect.</p><p>If you’ve got your core idea, this is your practical shortcut to launching a <strong>real</strong> SaaS, one that’s production-ready, not just a demo.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1W8UxyhA71UpYcrB.jpg" /></figure><blockquote><em>If you want a clear, non-technical intro to SaaS, start with </em><a href="https://codeblock.dev/blog/post/what-is-saas-a-simple-guide-with-a-real-example"><em>What is SaaS? A simple guide (with a real example)</em></a><em>.</em></blockquote><h3>Why Most SaaS Projects Get Delayed</h3><p>Almost every SaaS, regardless of what it does, needs:</p><ul><li>Secure authentication and authorization</li><li>Payment and pricing (plans, renewals, upgrades)</li><li>Admin and user panels</li><li>Monitoring, logging, and audit trails</li><li>Efficient deployment and maintenance</li></ul><p>Rebuilding all of this from scratch burns months of your time, budget, and energy.<br> Skip “minimum viable product” dreams. If you launch with half of these missing, you’ll grind to a halt as soon as real users arrive.</p><h3>What “Production-Ready” Actually Means</h3><p>A true, production-ready SaaS (even for solo founders) needs <strong>much more</strong> than a working demo:</p><ol><li><strong>Clean architecture</strong> that grows with your business logic</li><li><strong>Robust identity, roles, &amp; permissions</strong> for secure access</li><li><strong>Pricing and subscriptions</strong> (upgrade, cancel, pro-rate support)</li><li><strong>Integrated payments</strong> (Stripe, etc.)</li><li><strong>Admin and user panels</strong>, because support matters</li><li><strong>Monitoring and change tracking</strong> for reliability</li><li><strong>Localization/globalization</strong> for multi-market growth</li></ol><p>If any of these are missing, you’re not ready for production.</p><h3>Should You Build or Buy Your Foundation?</h3><p>Ask yourself:</p><ul><li><strong>Is this feature (auth, billing, admin, etc.) my competitive edge, or do my users expect it “just to work”?</strong></li><li><strong>Will people buy or stay because of custom infrastructure, or for what’s unique in my product?</strong></li><li><strong>Do I want to maintain this code for years, or would I rather focus all energy on my real idea?</strong></li></ul><p>If these questions make you doubt, don’t reinvent the wheel.<br><strong>Adopt a foundation you trust and invest your time in what only you can build.</strong></p><h3>Your Fastest .NET SaaS Launch Path (Step-by-Step)</h3><h4>1. Start With a Complete SaaS Template</h4><p>Skip the barebones starter kits. Use a template that already contains real architecture, with identity, payments, admin UI, and more already wired up.</p><h4>2. Configure Your Product (Not Just the Style)</h4><p>Set up plans, subscription logic, branding, permissions, and any tenant rules <strong>before</strong> you write new features.</p><h4>3. Code Only the Unique Value</h4><p>Treat the template as your platform layer.<br> All the things every SaaS needs are handled, now add only the features that make yours special.</p><h4>4. Deploy Fast &amp; Learn in Production</h4><p>Launch quickly, collect feedback from real users, and iterate.<br> Spending months on unseen foundation leads to “perfect code, no customers.”</p><h3>CodeBlock DevKit: The Full SaaS Foundation for .NET</h3><p><a href="https://codeblock.dev/"><strong>CodeBlock DevKit</strong></a> is a production-grade SaaS development kit for .NET teams and solo builders:</p><ul><li>Full SaaS application template</li><li>Website, admin panel, and user panel, all integrated</li><li>Core modules (Identity, Admin, Pricing, Payment, Subscription)</li><li>AI Chatbot module for those training models</li><li>Monitoring &amp; change tracking</li><li>Comprehensive documentation &amp; REST API client</li></ul><p>Get the up-to-date feature scope at <a href="https://codeblock.dev/">codeblock.dev</a> or check the docs at <a href="https://docs.codeblock.dev/">docs.codeblock.dev</a>.</p><h3>Who Wins With This Approach?</h3><p>This shortcut is a game changer if you are:</p><ul><li>A solo founder with limited time (and patience for boilerplate)</li><li>A backend developer who wants to ship faster (and avoid endless “setup”)</li><li>A frontend dev who’d rather build UI than learn yet another backend</li><li>A team focused on validating an idea before scaling</li></ul><h3>Mistakes to Avoid</h3><p>The most expensive early SaaS mistake?<br><strong>Optimizing for “developer comfort” instead of your users’ reality.</strong></p><p>A hand-crafted backend may be satisfying, but your real edge is launching and learning fast, not admiring your code.</p><h3>Your Real Advantage: Speed to Value</h3><p>Real SaaS growth comes from putting your unique idea in users’ hands fast, then improving it week by week.</p><p>A dev kit like CodeBlock DevKit lets you skip the repetitive 80% so you can focus on the 20% nobody else can copy.</p><h3>Final Test Before You Commit</h3><p>Before you take a path, ask yourself:</p><blockquote><strong><em>How quickly can I get from “idea” to a real, production-ready SaaS with paying users?</em></strong></blockquote><p>If your answer isn’t “weeks, not months”, it’s time to use a better foundation.</p><p><em>Originally published at </em><a href="https://codeblock.dev/blog/post/how-to-build-a-production-ready-saas-in-net"><em>https://codeblock.dev</em></a><em> on April 14, 2026.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=561d8d55ae4a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing CodeBlock SaaS DevKit]]></title>
            <link>https://medium.com/@hamed.shirbandi/introducing-codeblock-saas-devkit-e8fd1a106aab?source=rss-2a06b8c537a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8fd1a106aab</guid>
            <category><![CDATA[solopreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[devkit]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[solopreneur]]></category>
            <dc:creator><![CDATA[Hamed Shirbandi]]></dc:creator>
            <pubDate>Tue, 26 Aug 2025 12:31:34 GMT</pubDate>
            <atom:updated>2025-08-26T12:31:34.281Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fs5PO1JIE38w&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Ds5PO1JIE38w&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2Fs5PO1JIE38w%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b759ab43f675b6c78fbf13323450823c/href">https://medium.com/media/b759ab43f675b6c78fbf13323450823c/href</a></iframe><p>Building a SaaS product is exciting — until you realize just how much groundwork needs to be done before you can even test your idea. Authentication, payments, pricing, subscriptions, admin panels, monitoring… the list feels endless.</p><p>For many solo founders, entrepreneurs, and developers, this means <strong>months of repetitive work</strong> before they can even start building the unique part of their product. And in the fast-moving startup world, that delay can be fatal.</p><p>That’s why I created <a href="https://codeblock.dev/"><strong>CodeBlock DevKit</strong></a>.</p><h3>What is CodeBlock DevKit?</h3><p>CodeBlock DevKit is a <strong>SaaS Development Kit for entrepreneurs and developers</strong>. Instead of spending months building the foundation of your application, you can get a <a href="https://github.com/CodeBlock-Dev/CodeBlock.DevKit.SaaS.Template"><strong>production-ready SaaS template</strong></a> in minutes — complete with all the essential modules already integrated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0BVJVAJnOcKc1p1FaPcFXA.png" /></figure><h3>How It Works</h3><ol><li><strong>Purchase your license</strong> — one simple plan, unlimited SaaS apps.</li><li><strong>Download the </strong><a href="https://github.com/CodeBlock-Dev/CodeBlock.DevKit.SaaS.Template"><strong>template</strong> </a>— a full, production-ready application with architecture in place.</li><li><strong>Customize &amp; build</strong> — add your business logic in your preferred IDE.</li><li><strong>Deploy anywhere</strong> — cloud, Windows, Linux — your choice.</li></ol><p>From purchase to production in minutes, not months.</p><h3>What You Get</h3><p>When you get CodeBlock DevKit, you’re not just getting a starter project — you’re getting a <strong>complete SaaS application</strong> with:</p><ul><li>Website, user panel, and admin panel.</li><li>REST API and AI chatbot client.</li><li>Pre-built modules for <strong>identity, pricing, payments, subscriptions, monitoring, AI chatbots, settings, change tracking, analytics, blogging, licensing, and more</strong>.</li><li>Supporting services like email, SMS, caching, security, localization, globalization, job scheduling, and more.</li></ul><p>Everything works out of the box, so you can <strong>focus on your idea instead of infrastructure</strong>.</p><h3>Why CodeBlock DevKit?</h3><ul><li><strong>Save months of development</strong> — focus on innovation, not boilerplate.</li><li><strong>Production-ready quality</strong> — secure, tested, and reliable modules.</li><li><strong>Incredible value</strong> — equals about 8 hours of a developer’s salary.</li><li><strong>Future-proof</strong> — all updates and new modules included.</li><li><strong>AI Agent </strong>— describe your SaaS in plain English and let AI build it for you.</li></ul><h3>Who Can Benefit?</h3><ul><li><strong>Entrepreneurs</strong> — Have an idea but no technical co-founder? Launch affordably.</li><li><strong>Backend Developers</strong> — Skip foundation work and ship faster.</li><li><strong>Frontend Developers</strong> — Use our REST APIs and panels without worrying about backend.</li><li><strong>AI Model Trainers</strong> — <a href="https://docs.codeblock.dev/docs/tutorials-examples/train-and-monetize-ai-model.html">Monetize your models</a> instantly with our AI chatbot module.</li></ul><p>If you’re building a SaaS, CodeBlock DevKit can cut your launch time from <strong>months to days</strong>.</p><h3>Ready to Build?</h3><p>I built CodeBlock DevKit so other developers and founders don’t have to go through the painful slow grind I faced when launching my own SaaS products.</p><p>💡 Whether you’re a <strong>solo founder</strong> or a <strong>developer with a SaaS idea</strong>, CodeBlock DevKit is here to help you launch faster, smarter, and with confidence.</p><p>👉 Start today: <a href="https://codeblock.dev/">codeblock.dev</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8fd1a106aab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linting and Code Formatting in .NET Projects]]></title>
            <link>https://medium.com/@hamed.shirbandi/linting-and-code-formatting-in-net-projects-0bcea841d4c5?source=rss-2a06b8c537a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/0bcea841d4c5</guid>
            <category><![CDATA[linting]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[ci]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Hamed Shirbandi]]></dc:creator>
            <pubDate>Sun, 05 Nov 2023 19:08:01 GMT</pubDate>
            <atom:updated>2023-12-08T13:14:28.704Z</atom:updated>
            <content:encoded><![CDATA[<h3>Linting and Code Formatting in .NET Projects</h3><p>In a team working on a software product, each developer may bring their own coding style. This variability leads to bug-prone, design-violating, and code-smell-ridden code, making code reviews challenging and decreasing code quality. To address this, we need to automate the enforcement of a set of rules and best practices. But how?</p><h3>Automated Linting and Code Formatting</h3><p>Documenting coding rules and asking developers to adhere to them is not sufficient; there is no guarantee, and reminding them repeatedly will make the environment psychologically unsafe. Instead, we can use linting and formatting tools to enforce coding rules and integrate them into our build automation and CI pipelines.</p><p>Before we dive in, be sure to check out my articles on CI and Build Automation:</p><p><a href="https://medium.com/@hamed.shirbandi/integrate-ci-with-nuke-and-stryker-0750ce8c8829">Integrate CI with Nuke and Stryker</a></p><h3>Using CSharpier tool for Code Formatting</h3><blockquote>Code formatting tools focus on the visual appearance and style of the code, including aspects like indentation, line breaks, spacing, etc. They automatically adjust the code to adhere to a predefined coding style or a specific set of formatting rules.</blockquote><p><a href="https://csharpier.com/">CSharpier</a> is a good code formatting tool for C# which you can use both in local and CI pipelines. It is very simple to use by installing it, adding a config file and then run its commands on your build automation.</p><p>You can install it globally on your machine by running the following command:</p><pre>dotnet tool install csharpier -g</pre><p>To be able to use it in the CI pipelines, you need to also add it to the <strong>dotnet-tools.json</strong>, you will find it in the <strong>.config</strong> folder from the root folder of your project’s repository.</p><pre>{<br>  &quot;version&quot;: 1,<br>  &quot;isRoot&quot;: true,<br>  &quot;tools&quot;: {<br>    &quot;csharpier&quot;: {<br>      &quot;version&quot;: &quot;0.24.2&quot;,<br>      &quot;commands&quot;: [<br>        &quot;dotnet-csharpier&quot;<br>      ]<br>    }<br>  }<br>}</pre><p>Then you should add the config file for CSharpier (<strong>.csharpierrc.yaml) </strong>to the root folder of your project:</p><pre>printWidth: 100 # Specify at what point the printer will wrap content<br>useTabs: false # Indent lines with tabs instead of spaces.<br>tabWidth: 4 #Specify the number of spaces used per indentation level<br>preprocessorSymbolSets: # Preprocessor Symbol Sets like #if FIRST #elif SECOND<br>    - &quot;&quot;<br>    - &quot;DEBUG&quot;<br>    - &quot;DEBUG,CODE_STYLE&quot;</pre><p>Now everything is ready for formatting your codes. But, let’s do it through an example. We have the following code in a class:</p><pre>public class ClassName {<br>    public void CallMethod() { <br>        this.LongUglyMethod(&quot;1234567890&quot;, &quot;abcdefghijklmnopqrstuvwxyz&quot;, &quot;ABCDEFGHIJKLMNOPQRSTUVWXYZ&quot;);<br>    }<br>}</pre><p>Now, to enforce code formatting rules using CSharpier, we need to run the following command on the root folder of the project:</p><pre>dotnet csharpier .</pre><p>After running the above command, the code will be changed like the following:</p><pre>public class ClassName<br>{<br>    public void CallMethod()<br>    {<br>        this.LongUglyMethod(<br>            &quot;1234567890&quot;,<br>            &quot;abcdefghijklmnopqrstuvwxyz&quot;,<br>            &quot;ABCDEFGHIJKLMNOPQRSTUVWXYZ&quot;<br>        );<br>    }<br>}</pre><p>Note that the above command is useful only in local environment, not in CI pipeline. Developers can use this command to apply the formatting rules automatically. But, in CI, we just need to check if the formatting rules are obeyed or not, and we don’t want to change the coming codes. If the formatting rules are not followed, then the CI will break the build and the respective developer should resolve it. To achieve that, in CI pipeline, we need to run the following command instead:</p><pre>dotnet csharpier --check .</pre><p>If you are not using a modern build tool like <a href="https://medium.com/@hamed.shirbandi/build-automation-with-nuke-in-net-projects-9fc6cfddb23b">Nuke</a>, CSharpier will return a none zero exit code that you can use in your build script to break the build.</p><p>Also, CSharpier has an <a href="https://csharpier.com/docs/Editors">extension</a> for different IDEs that you can use to format the code on file save.</p><h3>Using dotnet-format tool for Linting</h3><blockquote>Linting is concerned with code quality, potential issues, and adherence to coding standards and best practices. Linters use predefined rules or configurations to identify and report code issues, such as unused variables, potential bugs, non-standard coding practices, etc.</blockquote><p><a href="https://github.com/dotnet/format">dotnet-format</a> is a built-in tool provided by .NET you can use to define and force your coding rules and best practices. It reads the rules from <strong>.editorconfig</strong> file, which you should add it to the root folder of your project’s repository.</p><p>Let’s start using it through an example. We need to force namespaces to match folder structure. So, we add that rule to the .editorconfig:</p><pre><br>root = true<br><br># C# files<br>[*.cs]<br><br>dotnet_diagnostic.IDE0130.severity=error # IDE0130 means namespace does not match folder structure </pre><p>You can find a list of Microsoft rules like <strong>IDE0130 </strong>in <a href="https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/style-rules/">this link</a>. Also, I have prepared a real-world rule set for <a href="https://github.com/hamed-shirbandi/TaskoMask/blob/master/.editorconfig">my open source project</a> that you may like to use and customize for your project.</p><p>In our sample project, we have a class which is placed in a folder named <strong>Models</strong>, but the namespace doesn’t match the folder structure. So, as we set the severity to error, Visual Studio will mark that namespace with a red underline just like other compile errors:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/782/1*60J-VfoprG9HwsUN7aDDoA.png" /></figure><p>In the above image, you see we have a compile error, but it doesn’t show up when we build the project. To solve this issue, we need to add <strong>EnforceCodeStyleInBuild </strong>property to the <strong>.csproj </strong>file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/694/1*4ocsFv_ky81EuNJUHhVaHw.png" /></figure><p>Also, if you want to apply it to all projects in the solution, you can add a file named <strong>Directory.Build.props </strong>to the root of your solution folder with the below content:</p><pre>&lt;Project&gt;<br>    &lt;PropertyGroup&gt;<br>        &lt;EnforceCodeStyleInBuild&gt;true&lt;/EnforceCodeStyleInBuild&gt;<br>    &lt;/PropertyGroup&gt;<br>&lt;/Project&gt;</pre><p>Now, if you build again, you will see the error and the build will be failed:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/699/1*gz-EGrLcP5Pim_RR5ZiTyw.png" /></figure><p>Now, we need to verify our rules through commands because we like to use them in our build automation and CI pipeline. If you run the following command, it will fix the rule violations automatically if it is possible. Because some changes can not be applied by tool and a developer needs to make a decision. But it will fix some others like forcing file-scoped namespaces, etc.</p><pre>dotnet format style </pre><p>As said before, we don’t want to change anything during CI, so the above command is good to be used only on local environment. To verify our rules on CI, we can run the following command:</p><pre>format style --verify-no-changes --verbosity diagnostic</pre><p>If you are not using a modern build tool like <a href="https://medium.com/@hamed.shirbandi/build-automation-with-nuke-in-net-projects-9fc6cfddb23b">Nuke</a>, dotnet-format will return a none zero exit code that you can use in your build script to break the build.</p><p>.editorconfig allows you to add almost every rule you want. If you have some naming conventions, preferred code styles and anything else, you can simply add it to your rules. Think of your rules and best practices, then search to find them on Microsoft docs.</p><h3>Explore linting in a real-world example</h3><p>If you read <a href="https://medium.com/@hamed.shirbandi/integrate-ci-with-nuke-and-stryker-0750ce8c8829">my other article</a> mentioned at the beginning, you will find out how to add CSharpier to your build automation and CI. Also, you can explore my open-source project to see how lint and formatting tools area integrated with the build automation and CI:</p><p><a href="https://github.com/hamed-shirbandi/TaskoMask">GitHub - hamed-shirbandi/TaskoMask: Task management system based on .NET 6 with Microservices, DDD, CQRS, Event Sourcing and Testing Concepts</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0bcea841d4c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Integrate CI with Nuke and Stryker]]></title>
            <link>https://medium.com/@hamed.shirbandi/integrate-ci-with-nuke-and-stryker-0750ce8c8829?source=rss-2a06b8c537a3------2</link>
            <guid isPermaLink="false">https://medium.com/p/0750ce8c8829</guid>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[github-actions]]></category>
            <category><![CDATA[build-automation]]></category>
            <category><![CDATA[stryker]]></category>
            <dc:creator><![CDATA[Hamed Shirbandi]]></dc:creator>
            <pubDate>Wed, 25 Oct 2023 18:32:58 GMT</pubDate>
            <atom:updated>2023-10-25T18:32:58.921Z</atom:updated>
            <content:encoded><![CDATA[<p>Struggling to improve code quality and test coverage in your development process? In this article, we’ll reveal how integrating CI with Nuke and Stryker can be your solution!</p><p>Before we dive in, be sure to check out my two other articles on Nuke and Stryker for a more in-depth understanding. These resources can complement what we’ll cover here.</p><ul><li><a href="https://medium.com/@hamed.shirbandi/build-automation-with-nuke-in-net-projects-9fc6cfddb23b">Build Automation with Nuke in .NET projects</a></li><li><a href="https://medium.com/@hamed.shirbandi/mutation-testing-with-stryker-in-net-projects-ff1f05ddce8f">Mutation Testing with Stryker in .NET Projects</a></li></ul><h3>Building a real-world example</h3><p>In this hands-on journey, we’ll apply the principles of CI with Nuke and Stryker to a real-world project on GitHub named <a href="https://github.com/hamed-shirbandi/TaskoMask"><strong><em>TaskoMask</em></strong></a>. For an in-depth understanding, feel free to explore the project itself. And if you find it valuable, a star would be much appreciated :)</p><p><a href="https://github.com/hamed-shirbandi/TaskoMask">GitHub - hamed-shirbandi/TaskoMask: Task management system based on .NET 6 with Microservices, DDD, CQRS, Event Sourcing and Testing Concepts</a></p><h3>Preparing the Build Plan</h3><p>To start, let’s create a build plan. For TaskoMask, I’ve made a plan to make sure the code always gets compiled, check for any bugs with unit tests, and ensure the quality of these tests with mutation testing. Here’s the plan:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rTPhhGrEogTobAfwZP7LEg.png" /><figcaption>Nuke-build-plan</figcaption></figure><h3>Implementing the Build Plan with Nuke</h3><p>Here is the build implementation using Nuke. You can also find the latest version on <a href="https://github.com/hamed-shirbandi/TaskoMask/blob/master/src/6-Build/Build.cs">GitHub</a>.</p><pre>class Build : NukeBuild<br>{<br>    public static int Main() =&gt; Execute&lt;Build&gt;(x =&gt; x.RunMutationTests);<br><br>    [Parameter]<br>    readonly Configuration Configuration = IsLocalBuild ? Configuration.Debug : Configuration.Release;<br><br>    [Solution]<br>    readonly Solution Solution;<br><br>    [Parameter]<br>    AbsolutePath TestResultDirectory = RootDirectory + &quot;/.nuke/Artifacts/Test-Results/&quot;;<br><br>    Target LogInformation =&gt; _ =&gt; _<br>        .Executes(() =&gt;<br>        {<br>            Log.Information($&quot;Solution path : {Solution}&quot;);<br>            Log.Information($&quot;Solution directory : {Solution.Directory}&quot;);<br>            Log.Information($&quot;Configuration : {Configuration}&quot;);<br>            Log.Information($&quot;TestResultDirectory : {TestResultDirectory}&quot;);<br>        });<br><br>    Target Preparation =&gt; _ =&gt; _<br>        .DependsOn(LogInformation)<br>        .Executes(() =&gt;<br>        {<br>            TestResultDirectory.CreateOrCleanDirectory();<br>        });<br><br>    Target RestoreDotNetTools =&gt; _ =&gt; _<br>        .Executes(() =&gt;<br>        {<br>            DotNet(arguments: &quot;tool restore&quot;);<br>        });<br><br>    Target Clean =&gt; _ =&gt; _<br>        .DependsOn(Preparation)<br>        .Executes(() =&gt;<br>        {<br>            DotNetClean();<br>        });<br><br>    Target Restore =&gt; _ =&gt; _<br>        .DependsOn(Clean)<br>        .Executes(() =&gt;<br>        {<br>            DotNetRestore(a =&gt; a.SetProjectFile(Solution));<br>        });<br><br>    Target Compile =&gt; _ =&gt; _<br>        .DependsOn(Restore)<br>        .Executes(() =&gt;<br>        {<br>            DotNetBuild(a =&gt;<br>                a.SetProjectFile(Solution)<br>                    .SetNoRestore(true)<br>                    .SetConfiguration(Configuration));<br>        });<br><br>    Target RunUnitTests =&gt; _ =&gt; _<br>        .DependsOn(Compile)<br>        .Executes(() =&gt;<br>        {<br>            var testProjects = Solution.AllProjects.Where(s =&gt; s.Name.EndsWith(&quot;Tests.Unit&quot;));<br><br>            DotNetTest(a =&gt; a<br>                .SetConfiguration(Configuration)<br>                .SetNoBuild(true)<br>                .SetNoRestore(true)<br>                .ResetVerbosity()<br>                .SetResultsDirectory(TestResultDirectory)<br>                    .EnableCollectCoverage()<br>                    .SetCoverletOutputFormat(CoverletOutputFormat.opencover)<br>                    .SetExcludeByFile(&quot;*.Generated.cs&quot;)<br>                    .EnableUseSourceLink()<br>                .CombineWith(testProjects, (b, z) =&gt; b<br>                    .SetProjectFile(z)<br>                    .AddLoggers($&quot;trx;LogFileName={z.Name}.trx&quot;)<br>                    .SetCoverletOutput(TestResultDirectory + $&quot;{z.Name}.xml&quot;)));<br>        });<br><br>    Target RunMutationTests =&gt; _ =&gt; _<br>        .DependsOn(RunUnitTests,RestoreDotNetTools)<br>        .Executes(() =&gt;<br>        {<br>            //It will add dashboard reporter<br>            string reporter = &quot;--reporter dashboard&quot;;<br><br>            //we don&#39;t use dashboard reporter on local builds<br>            if (IsLocalBuild)<br>                reporter = &quot;&quot;;<br><br>            var testProjects = Solution.AllProjects.Where(s =&gt; s.Name.EndsWith(&quot;.Tests.Unit&quot;));<br><br>            foreach (var testProject in testProjects)<br>                DotNet(workingDirectory: testProject.Directory, arguments: $&quot;stryker {reporter}&quot;);<br>        });<br>}</pre><p>The implementation is smooth and straightforward. Each step in the build plan is implemented as a target. Additionally, you’ll discover how we can incorporate Stryker for mutation testing into our Nuke build targets.</p><h3>Integrating with GitHub Actions workflow (CI)</h3><p>Here is the CI implementation using GitHub Actions. You can also find the latest version on <a href="https://github.com/hamed-shirbandi/TaskoMask/blob/master/.github/workflows/ci.yml">GitHub</a>.</p><pre>name: build<br><br>env:<br>  Configuration: Release<br>  ContinuousIntegrationBuild: true<br><br>on:<br>  pull_request:<br>    branches: [&quot;master&quot;]<br>  push:<br>    branches: [&quot;master&quot;]<br><br>jobs:<br>  build:<br>    runs-on: windows-latest<br><br>    steps:<br>      - uses: actions/checkout@v3<br>      - name: Setup .NET<br>        uses: actions/setup-dotnet@v2<br>        with:<br>          dotnet-version: 6.0.x<br><br>      - name: Build<br>        run: ./build.ps1 Compile<br><br>      - name: Unit Test<br>        run: ./build.ps1 RunUnitTests --skip Compile<br><br>      - name: Mutation Test<br>        run: ./build.ps1 RunMutationTests --skip RunUnitTests<br>        env:<br>          STRYKER_DASHBOARD_API_KEY: ${{ secrets.STRYKER_DASHBOARD_API_KEY }}</pre><p>I assume you are familiar with GitHub Actions or other CI tools, so let’s talk about the last three steps (Build, Unit Test, Mutation Test).</p><p>Nuke generates some build scripts that you can use in your CI pipelines. Here, we’re using the <strong>build.ps1</strong> script, which is placed in the root of the repository. For each step, we run the build.ps1 script and pass the desired target name as its argument.</p><h3>Build Step</h3><p>In the <strong>Build </strong>step, we run the <strong>Compile </strong>target which depends on Restore, Clean, Preparation and LogInformation targets. So it runs all of those targets one by one based on their priority.</p><h3>Unit Test Step</h3><p>In this step, because the <strong>RunUnitTests </strong>target depends on <strong>Compile </strong>target, we don’t need to run the Compile target again, we skip it by passing<strong><em> — skip</em></strong> argument.</p><h3>Mutation Test Step</h3><p>We need to skip unit tests and also provide <strong>STRYKER_DASHBOARD_API_KEY </strong>to be able to send the mutation testing result to Stryker dashboard.</p><p>On TaskoMask, I’ve configured Stryker to break the build if the mutation score falls below the threshold specified in <strong><em>stryker-config.json</em></strong>. For more details, check out my discussion on this topic in <a href="https://medium.com/@hamed.shirbandi/mutation-testing-with-stryker-in-net-projects-ff1f05ddce8f">my other article</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0750ce8c8829" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>