Tweet
#buildinpublic update: Burnout recovery complete.

After the 2,5 months of work resulting in nothing due to partnership failing, it triggered a short burnout episode.

This is the one common theme in my career, if a project that I pour my soul into leads to nothing, I lose all my… twitter.com/i/web/status/1…
#buildinpublic update

That partnership that I’ve started a few months back utterly failed. That’s 2,5 months of work down the drain… Trying to salvage what I can.

At least freelance work is going strong that keeps me on my feet. $5k in May, and just signed a deal for $15k for… twitter.com/i/web/status/1…
At the beginning of the year I started my #buildinpublic journey aiming to launch 16 products in 12 months, hoping to at least earn $1 in a few months.

4 months later, still at 0 MRR, with 3m of runway left and some debt to clean up.

Thankfully I can extend this with… twitter.com/i/web/status/1…
Ok, did some financial analysis. I have 90 days of runway to reach $2.500 MRR for break-even point.

It looks like I need to take some more freelancing work to extend it 😢

I’ve been dodging incoming project requests for some time, I’ll poke some of them.

#buildinpublic
CraftLog #9 #buildinpublic

I've been slacking about documenting the journey... Time for a new CraftLog!

I've built the CLI for Rx.Atlas a few weeks ago and have been using it with great success since.

Some details and tech below.

It's a cross-platform #dotnet console app that… twitter.com/i/web/status/1…
Back to shipping! #buildinpublic

Kiddo is finally feeling better and I’m back in business.

Today shipped a new product… for a former client 😩

It’s a SSP platform for outdoor advertising, managing displays and advertisements. Built with #dotnet / React.
CraftLog #8 #buildinpublic

In 12 hours, the situation with the partnership offer I got will resolve, one way or another. Fingers crossed.

In the mean time, I spent some time polishing stuff and streamlining the codebase.

Some tech details 👇

I’ve created a payment module for… twitter.com/i/web/status/1…
Need some feedback from #buildinpublic community.

I got a partnership offer for 3 related B2B products. (Online events, academic event mgmt, digital certificates)

It’ll be a 4 person team, I’ll build the products, other 3 will handle the sales & marketing.

Pros & Cons:

They… twitter.com/i/web/status/1…
CraftLog #7 #buildinpublic

While working on the partnership situation to resolve, I did some more work on the tech side.

I streamlined the Email sending with some awesome .NET packages. #dotnet

Some tech details 👇🏻
CraftLog #6 #buildinpublic

After a two week hiatus, I’m finally back at building.

CertificateReactor is feature complete, but I’m holding a bit on the launch. There is a potential partnership offer on the table which will hopefully resolve this week.

Some tech details 👇🏻
If you had to opportunity to team up with a few great people for one or more of your products, where they took ownership of the marketing and you handle the tech side, would you do it?

Asking for a friend.

#buildinpublic
CraftLog #5 #buildinpublic

I’ve completed the designer with all bells and whistles for Certificate Reactor.

I really like how it turned out.

I’ll add image creation, email sending and groups today to complete the necessary features for launch.

Also, Tailwind is awesome.
CraftLog #4 #buildinpublic

Finally dived into the frontend. The main functionality of Certificate Reactor, the certificate designer, is almost complete.

I’m loving Typescript more and more.

Here is how the first rough draft of UI looks like 👇🏻
CraftLog #3

2 more subsystems are done for Rx.Atlas.

Tag -> A self referential entity that can be attached to any other entity in the database.

MultiTenancy -> Transparent multi-tenancy support.

Both are cornerstones of any app I’ve built in the past.

#buildinpublic
Finishing touches today for Rx.Atlas File Storage subsystem.

It allows me to manage all things about files & uploads on my apps, similar to ActiveStorage from Rails.

It has pluggable backends, currently local, S3 & database. I’ll be mainly using Cloudflare R2.

#buildinpublic
JS reorientation part #2 for Rx.Atlas.

I’ve deep dived into the query/fetch solutions since yesterday.

RTK Query, Tanstack Query, SWR, React Router, Apollo/Relay.

Here are my findings 👇🏻

#21 will shock you !?!!11?!1

#buildinpublic
I’ve been reorienting myself with the latest state of things in React ecosystem, reevaluating Next, Remix, React Router, React Server Components, CSS-in-JS etc.

Here are my findings 👇

#buildinpublic
I’m trying a new productivity experiment:

I’ve moved all my social content consumption & creation (where possible) to iPad and blocked them from my Mac.

Added friction should help when I’m trying to get in the zone but my hands go open Twitter for the x time.

#buildinpublic
Does anyone else use Figma/Sketch this way?

I start with a rough sketch/prototype of what I want (top left), and iterate with duplicating until I arrive at a satisfactory result (bottom right).

Each row roughly corresponds with a different path of exploration.

#buildinpublic
#16in12 update #1

I’m back to publishing logs after a short hiatus.

I’ve changed my plans a bit and picking up speed. My work on the framework side is done for now, and I’ve started working on the product side.

I’m calling the framework Rx.Atlas.

Details👇🏻

#buildinpublic