(3) The tech stack will be Go for the backend, Vanilla JS for the frontend, PSQL as the main database, and Polar for payments, all running within an AWS architecture that includes EC2, S3, SES, Pulumi deployment scripts and more.
#buildinpublic
#buildinpublic
December 9, 2025 at 7:44 PM
(3) The tech stack will be Go for the backend, Vanilla JS for the frontend, PSQL as the main database, and Polar for payments, all running within an AWS architecture that includes EC2, S3, SES, Pulumi deployment scripts and more.
#buildinpublic
#buildinpublic
(2) After finishing the core features, I'm planning to make the entire GitHub repository public before the official release.
The project will be fully open source and free to self-host.
#buildinpublic
The project will be fully open source and free to self-host.
#buildinpublic
December 9, 2025 at 7:44 PM
(2) After finishing the core features, I'm planning to make the entire GitHub repository public before the official release.
The project will be fully open source and free to self-host.
#buildinpublic
The project will be fully open source and free to self-host.
#buildinpublic
Fail fast. For me that is the only way to test. Build as quickly as possible, but make sure to handle performance and security. Then publish and try to do marketing. But what I’m actually doing is learning marketing.
December 1, 2025 at 6:38 PM
Fail fast. For me that is the only way to test. Build as quickly as possible, but make sure to handle performance and security. Then publish and try to do marketing. But what I’m actually doing is learning marketing.
(6) This time I'm mainly focusing on AI-related workflows, a single editor for the entire application.
Starting tomorrow, I’m going all in on this.
#buildinpublic
Starting tomorrow, I’m going all in on this.
#buildinpublic
November 30, 2025 at 4:57 PM
(6) This time I'm mainly focusing on AI-related workflows, a single editor for the entire application.
Starting tomorrow, I’m going all in on this.
#buildinpublic
Starting tomorrow, I’m going all in on this.
#buildinpublic
(5) I've used TipTap in almost every project I've built, so I decided to create a custom editor component with zero dependencies that is highly configurable, easier than ProseMirror, and faster on both desktop and mobile. The name will still be 'Writtte'.
November 30, 2025 at 4:57 PM
(5) I've used TipTap in almost every project I've built, so I decided to create a custom editor component with zero dependencies that is highly configurable, easier than ProseMirror, and faster on both desktop and mobile. The name will still be 'Writtte'.
(4) Yep there are hundreds of editors out there like CKEditor and TipTap, but most of them can't be used directly for AI-related workflows. TipTap can be adapted, but you have to build extensions for almost everything, and it’s based on ProseMirror. ProseMirror is a great framework.
November 30, 2025 at 4:57 PM
(4) Yep there are hundreds of editors out there like CKEditor and TipTap, but most of them can't be used directly for AI-related workflows. TipTap can be adapted, but you have to build extensions for almost everything, and it’s based on ProseMirror. ProseMirror is a great framework.
(3) It was better than the first one, though, because the first product failed after 8 months of work.
Since I had already bought the domain Writtte, I decided to turn it into an editor component instead.
Since I had already bought the domain Writtte, I decided to turn it into an editor component instead.
November 30, 2025 at 4:57 PM
(3) It was better than the first one, though, because the first product failed after 8 months of work.
Since I had already bought the domain Writtte, I decided to turn it into an editor component instead.
Since I had already bought the domain Writtte, I decided to turn it into an editor component instead.
(2) After that, I started creating a blogging platform called Writtte and shared more than a 30-day 'build in public' journey. However I ran into a serious issue, users of the platform could get banned by search engines, and I couldn’t find a solution for it. So that failed too :D
November 30, 2025 at 4:57 PM
(2) After that, I started creating a blogging platform called Writtte and shared more than a 30-day 'build in public' journey. However I ran into a serious issue, users of the platform could get banned by search engines, and I couldn’t find a solution for it. So that failed too :D
Yeah, I feel the same. Cloaking directly appears as a red flag for the core feature of the MVP. I’m thinking about getting a second opinion, but I still have no idea what to do.
November 24, 2025 at 3:12 PM
Yeah, I feel the same. Cloaking directly appears as a red flag for the core feature of the MVP. I’m thinking about getting a second opinion, but I still have no idea what to do.
Yeah, for this project I started with Next.js, then switched to React, and eventually moved to vanilla JS. For me, managing DOM manipulation directly is easier than using React. I know exactly what’s happening and why it’s happening, and it’s much easier to debug.
November 19, 2025 at 6:34 PM
Yeah, for this project I started with Next.js, then switched to React, and eventually moved to vanilla JS. For me, managing DOM manipulation directly is easier than using React. I know exactly what’s happening and why it’s happening, and it’s much easier to debug.
I totally agree with you. this project uses plain CSS, direct DOM manipulation, and no frameworks. The frontend is in TS, the backend in Go, and some critical parts are written in C. The design system is built from scratch, and I even had to design the icons myself :D and now my life is !sunnier too
November 19, 2025 at 6:00 PM
I totally agree with you. this project uses plain CSS, direct DOM manipulation, and no frameworks. The frontend is in TS, the backend in Go, and some critical parts are written in C. The design system is built from scratch, and I even had to design the icons myself :D and now my life is !sunnier too