DEV Community

Oleksandr Viktor
Oleksandr Viktor

Posted on

Six Months, One Developer, Too Much Coffee

Solo Developers Can Still Build Big Things in 2026 πŸš€

Every few weeks I see a post claiming something like:

"Modern software is too complex for a solo developer."

Or:

"You need funding, a team, product managers, a designer, a DevOps engineer, and at least three weekly meetings to build anything serious."

As a solo developer, I decided to perform a highly scientific experiment.

The experiment lasted six months.

The results were unexpected.


The Beginning

       πŸ’‘
        β”‚
        β–Ό
       WJb
Enter fullscreen mode Exit fullscreen mode

Six months ago, WJb was just an idea.

Not a company.

Not a startup.

Not a venture-backed product.

Just a simple goal:

Build a modern background job and workflow framework for .NET that is easy to use and easy to extend.

Sounds small enough.

Famous last words.


The Feature Expansion Loop

Build Feature
      β”‚
      β–Ό
 "Wouldn't it be nice..."
      β”‚
      β–Ό
 Build Another Feature
Enter fullscreen mode Exit fullscreen mode

Six months later, the original idea had evolved into an ecosystem.


WJb Core

             WJb
               β”‚
     β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”
     β–Ό         β–Ό         β–Ό
   Actions   Jobs     Workflows
Enter fullscreen mode Exit fullscreen mode

Today WJb provides:

  • Background jobs
  • Delayed execution
  • Scheduled jobs
  • Recurring jobs
  • Workflows
  • Action pipelines
  • Queues
  • Retry handling
  • Progress reporting
  • Dependency Injection integration

NuGet Packages:

WJb Free

WJb Commercial

https://www.nuget.org/packages?q=wjb


WJb.UI.Blazor

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ Dashboard                    β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ βœ… Completed                 β”‚
β”‚ 🟑 Running                   β”‚
β”‚ ❌ Failed                    β”‚
β”‚ πŸ”„ Retrying                  β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
Enter fullscreen mode Exit fullscreen mode

The dashboard brings visibility to jobs, queues, workflows, progress, payloads, errors, and execution history.

All inside the .NET ecosystem.

Just Blazor.

WJb.UI.Blazor


Supporting Real Projects Means Supporting Real Databases

βœ… IndexedDB
βœ… SQLite
βœ… SQL Server
βœ… PostgreSQL
βœ… MySQL
Enter fullscreen mode Exit fullscreen mode

This means WJb can be used in:

  • Blazor WebAssembly applications
  • Desktop applications
  • Small services
  • Enterprise systems
  • Cloud environments
  • Self-hosted deployments

Documentation Is a Feature

      Code
        β”‚
        β–Ό
     Examples
        β”‚
        β–Ό
 Documentation
        β”‚
        β–Ό
      Demos
        β”‚
        β–Ό
      wjb.pro
Enter fullscreen mode Exit fullscreen mode

Website:

WJb website

πŸ‘‰ https://wjb.pro

The site contains documentation, getting-started guides, examples, and interactive demos.


Testing: Conversations With Future Me

Past Me:
"This implementation is perfect."

Future Me:
"What is this?"
Enter fullscreen mode Exit fullscreen mode

Then you check Git history.

Author: You.

Awkward.

That's why a large amount of effort went into unit tests, integration tests, regression tests, and benchmarks.


Modern Solo Development

           πŸ’‘ Idea
              β”‚
              β–Ό
       Alexander
              β”‚
              β–Ό
        "Let's build it"
              β”‚
              β–Ό
         Copilot/Grok
              β”‚
              β–Ό
       Lots Of Code
              β”‚
              β–Ό
            WJb πŸš€
Enter fullscreen mode Exit fullscreen mode

AI doesn't replace developers.

It helps remove friction.

The vision, architecture, debugging, and persistence still come from the developer.


What Six Months Produced

                         WJb
                          β”‚
         β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
         β”‚                β”‚                β”‚
         β–Ό                β–Ό                β–Ό
      Core           UI.Blazor         Documentation
         β”‚
         β–Ό
      Providers
         β”‚
 β”Œβ”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”
 β–Ό       β–Ό       β–Ό       β–Ό       β–Ό
IDB   SQLite   SQL   PostgreSQL MySQL
Enter fullscreen mode Exit fullscreen mode

βœ… WJb Core

βœ… WJb.UI.Blazor

βœ… IndexedDB Provider

βœ… SQLite Provider

βœ… SQL Server Provider

βœ… PostgreSQL Provider

βœ… MySQL Provider

βœ… Documentation

βœ… Interactive Demos

βœ… Examples

βœ… Tests

βœ… Benchmarks

βœ… NuGet Packages

βœ… Website


Useful Links

Website

πŸ‘‰ https://wjb.pro

NuGet Packages

πŸ‘‰ https://www.nuget.org/packages?q=wjb

GitHub

πŸ‘‰ https://github.com/UkrGuru/WJb.Demo


Final Thoughts

      One Developer
             +
       Clear Vision
             +
       Modern Tools
             +
         Six Months
             =
      Entire Ecosystem
Enter fullscreen mode Exit fullscreen mode

Six months ago, WJb was just an idea.

Today it includes a framework, a dashboard, multiple providers, documentation, demos, tests, benchmarks, NuGet packages, and a public website.

So the next time someone says:

"A solo developer can't build something serious."

Just smile.

Then ship another release. πŸš€

Top comments (0)