Can Eker (John)

TheAssembler (DotNet Builder) - Prototype V1 #buildinpublic #dotnet #saas #indiedevelopers

The satisfaction of doing honest work and solving a real problem for someone is priceless. Client operation done. Now, its time to turn to the real construction site, the Pickaxe architecture, before the engine cools down. Moving on. Keep it real, keep shipping! ⚡🛵 #BuildInPublic #dotnetpickaxe #indiehackers

Let those lab architechts boast about how 'fancy' their code is; the client does not care what is spinning in the background. They just looks if the solution arrives at the door, error-free, secure, and on time.

Some so-called 'profesionals' expose their client's private projects and data publicly on X for 3-5 interactions and they call this 'Build in Public'. The rule of the street is simple: Honesty is not just measured by timely delivery, but by the respect for the privacy inside that package. I succesfuly delivered a 7-day intense Scraping operation today.

Some so-called "laboratory architechts" open 5 differant files across layers to setup a simple Authorization (Auth) system for a project, turning the whole thing into a bureaucracy labirynth. There is an unchangeable rule of the street and delivery: The customer want the package at his door, they dont care how many pans the chef used in the kitchen. Right now I am coding that perfect, fully configured Auth system for #dotnetpickaxe under the rules of Vertical Slice Architecture (VSA). How it will work? Single click. In seconds, JWT, Identity and the security infraestructure will be injected into your project, ready to hit the road. No more days of 'Integration Fatigue'. Zero technical dept. Remember; architecture isnt an acadamic show-field that slows the developer down, it is the fastest delivery vehicle that ships the product to the customer. Stop wasting time searching for a screw in the toolbox. Start the engine. Keep it lean, keep shipping! #buildinpublic #dotnet #indiehackers

The golden rule of Bootstrapping: To finance your dream, you must first 'ship' your client's work. Client work by day, building your own empire (Pickaxe) by night! This strategy is the most reliable fuel driving us toward our goal. I was off the radar for the last 4 days; we ran the engine full throttle for an urgent client BOT project. Pragmatic engineering dictates this: Code is not for show; it's meant to work and be shipped to the client. The BOT has been successfully delivered. While coding someone else's endless rules, my mind was constantly on Pickaxe's razor-sharp Vertical Slice Architecture (VSA) infrastructure. Trying to navigate someone else's labyrinth teaches you the value of the lean highway we built for ourselves so much better. Client delivery is complete. Now the route is heading back to the main operation: the Pickaxe construction site! Route re-established. To move leaner and faster: Keep it lean, keep shipping! #buildinpublic #indiehackers #dotnet #dotnetpickaxe

I know the mind of a developr real good; it wants to open folders, update the .csproj, and fix everything all at once. This is the "Over-engineering" trap. Pragmatik ingineering needs isolation. Right now, I am fogetting every other thing and turning my mind to "Laser Focuss." My first task: to code the worker roboot (the generater) that only produces the Program.cs text perfectely with JSON instructions. Stop biulding massive, broken, bureacratic factories on empty plots. Put up the main collumns, start the engine, and begin the delivry. I'm ready to lit up our first "Program.cs" code generater. My mind is clare, the rout is set. Keep it lean, keep shipping!

The plane simplicity of Modern .NET's "Top-level statemens" is a gift. An empty Program.cs starts the motor with only 4 lines. That is where TheAssembler's tru magic starts: It sneak in between that 4-line pure engine block and, with instuctions from the JSON DNA, places the modules (Exampel: Exeption Handler) in a perfect order. No spagetti code, just millimeter injektion.

Sum of our friends, "corporate architects," might as well be bragging 'bout bloated templates stuffed with 50 different liberys they don't even know what for when starting a new project. The rule of the street and shiping never changes: the more unnecessary wight in the trunk, the later you'll get to the goal. That's preccisely why we're starting the system behind Pickaxe Builder (TheAssembler) with the purest "Empty" template, zero technical dept. Wanna know why? #BuildInPublic #SaaS #DotNet

To all those architects out there drowning in "perfect plans" and endless diagrams... I see u. Doing perfect plans behind closed doors for months. ​But today, reality called. Two managers, two different citys. The request? "We need a working prototype in 3 days." ​If i was still fighting over which design pattern is "purest" or if my folders look pretty... I would have lost this chance already. ​Real talk: Clients dont care about how elegant your layers are. They care about solutions. And they want them FAST. In 2026, speed is the only game that matters. ​What am I doing right now? ​Using my TheAssembler engine to build the skeleton in seconds. ​Not just asking AI to "write code", but using it as an orchestra conductor. ​Using NotebookLM to keep my ADHD brain focused and grounded on what matters. ​Architecture matters. Discipline is key. But "perfectionism" is just a fancy word for being stuck. If u cant ship a prototype in 72 hours, your architecture is not helping you... its holding u back. ​Gonna park my bike and get back to shipping this thing. ​See u at the finish line. ​#dotnet #buildinpublic #cleanarchitecture

Many “architects” turn a simple JWT implementation into a NuGet dumpster fire, resulting in tons of corporate bloat. But the rule is simple: carry unnecessary weight, and you’ll be late on delivery. That’s why I designed #dotnetpickaxe specifically to clear out this bloat. Select your architecture (.NET 8-10). Check only the modules you need (JWT + Identity, Redis, Global Exception Handling, Serilog, etc.). The result: A clean project with minimal dependencies and zero conflicts—in seconds. I’m running the final tests now; the site will be updated soon. Remember: Architecture is not a display area; it's the fastest and safest vehicle to get the product to the customer. Keep it lean, keep shipping! #dotnet #buildinpublic #indiehackers

With Dotnetpickaxe (Pickaxe Builder) V 0.1, after selecting your architecture (Onion or VSA) and marking all the modules your project needs, such as JWT or Redis, your millimeter-perfect and error-free .NET project, containing only the necessary dependencies according to the architecture you selected, is automatically scaffolded onto an empty base template in seconds. #buildinpublic #indiehackers #dotnet

I added AddEndpointsApiExplorer and AddSwaggerGen to the core code, but the main rule is: UseSwaggerUI() only works when IsDevelopment() is true. Simple street rule: You dont open the package on the road for everyones to see. OpenAPI/Swagger docs are development-only, proving the "Secure by Default" architecture from the start. That's real professionalism! dotnetpickaxe.com #DotNet #indiehackers #BuildInPublic

Two modules want the same NuGet package? No problem. I used a Map object with package names as keys for perfect de-duplication. No code repetition! The system uses flatMap and Array.isArray checks to handle single string or array inputs for slots (like di_slot or middleware_slot), catching every piece like flexible Lego inputs and placing them right.

Some people really tak weeks just to setup a basic .NET project and call it "enterprise architecture." Unbelievable. I pulled an all-nighter and finished the most important module for Pickaxe Builder! (Like 4+ hours of pure focus). U can select your architecture and modules like JWT/Redis, and the system instantly give you a flawless .NET project with only the dependencies you need. And it's 100% freee. How I achieved this perfect delibery? Technical details here:

Pickaxe Builder is demo right bow but completely FREE. Choose your architecture, mark your modules, and download your flawless project in seconds. We look forward to your ruthless real-world feedback to make the system even faster. Link here enjoy the delivery: dotnetpickaxe.com #DotNet #SoftwareArchitecture #BuildInPublic #SaaS

When a user selects 5 different modules, the JS Injector only has 3 clear "deliveries" to make: 1️⃣.csproj merging 2️⃣appsettings.json merging 3️⃣program.cs Injection So-called "laboratory architects" might over-engineer this, but this is exactly what pragmatic engineering looks like. Keep it simple, ship it fast.

Some allegedly turn the frontend into an if/else jungle just to add a simple JWT or Redis to their .NET projects, and call it 'flexible architecture.'The street rule is simple: Bad routing kills delivery. Today, I'm launching the precise Pickaxe Builder which generates only what you need in seconds totally free. Let me show you how it works