Kategoria: Day by day
-
Day#18 Solving the „CORS error with Authorization header” in Next.js and NestJS
Today, I tackled a cross-origin issue in a full-stack TypeScript project using Next.js (frontend) and NestJS (backend).
-
Day#17 Self-Hosted Collaboration Tools: More Than Just Code
Building great software isn’t just about code. Today’s focus was on storytelling, internal documentation, and team tools — from preparing investor-ready presentations to deploying a self-hosted collaboration suite that supports transparency and autonomy.
-
Day#15 Account Registration, Subscription Plans, Email Verification & i18n
Today I focused on finalizing account registration RESTful webservice, subscription logic, implementing account verification, and introducing language support. It was a day of careful structuring, breaking cyclic dependencies, and refining developer UX. Here’s what got done: Subscription Models Enums Seed Data User Registration Email Verification i18n Support Email Delivery Translation File Structure „`/apps/partner/api/i18n/pl/auth.json/en/auth.json„` `.env` Configuration…
-
Day#14 Register Form with Validation in Next.js and React Hook Form
In this post, I will walk you through the process of building a registration form using Next.js and React Hook Form, complete with validation and dynamic language switching using i18next.
-
Day#13 Scoped Access Done Right (12 modules, 80+ tests)
Today I finalized tenant-aware access across all core modules using a shared ScopedRepository abstraction. This was the largest refactoring effort so far: 12 modules, 80+ unit tests, and one generic strategy to guarantee data isolation via subscriber_id.
-
Day#12 Password Reset Flow with JWT in a NestJS Backend
Today I implemented a complete password reset mechanism in a NestJS backend API. It consists of two public endpoints and uses a stateless approach based on JWT for token management.
-
Day #11 Climbing the Hierarchy
I spent the last few days working through one of the most foundational layers in our system — the user–supervisor–contract structure. The goal was simple: ensure that every user in the system has: a contract with the right supervisor, a valid assignment to a unit, a role that fits into a larger hierarchical model. But…
-
Day#10 Migrations vs Developer: A story of friction
Today was supposed to be a calm day. I just wanted to add a single value to a lookup table using a TypeORM migration. Two hours later, I had a fully working script to track migration status, a clearer understanding of TypeORM’s friction points, and a renewed appreciation for tools that just work.