Tootfinder

TL;DR:🧵
Today I lost 2 hours because TypeORM ESM NestJS is a fragile combo when it comes to migrations.
No migration:status.
No ESM-compatible CLI.
No schema awareness.
Class name must match filename (with timestamp!).
So I wrote my own migration-status.ts script to compare database state with the migration folder.
Lesson: if you need INSERT INTO "schema"."table", don’t forget the schema.
ORMs give you boilerplate — and tra…

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 ...

PFMBench: Protein Foundation Model Benchmark
Zhangyang Gao, Hao Wang, Cheng Tan, Chenrui Xu, Mengdi Liu, Bozhen Hu, Linlin Chao, Xiaoming Zhang, Stan Z. Li
https://arxiv.org/abs/2506.14796

PFMBench: Protein Foundation Model Benchmark
This study investigates the current landscape and future directions of protein foundation model research. While recent advancements have transformed protein science and engineering, the field lacks a comprehensive benchmark for fair evaluation and in-depth understanding. Since ESM-1B, numerous protein foundation models have emerged, each with unique datasets and methodologies. However, evaluations often focus on limited tasks tailored to specific models, hindering insights into broader generali…

Day 1:
tl;dr: ESM TS NestJS TypeORM is possible, but not recommended for the impatient.
Successfully bootstrapped NestJS TypeORM PostgreSQL stack using ESM.
It only took:
- 6 hours
- 17 cryptic errors
- 3 existential crises
Turns out, using modern JS modules with legacy decorators is... bold. But hey — it runs now.
#CloudNative

Day 3 2/2
2. Enabling API documentation with Swagger.
I integrated Swagger into the backend (NestJS v10, ESM, Turbo monorepo), using `@nestjs/swagger@7` to match our current framework version.
The docs are now live at `/api/docs`, fully aligned with our global `ValidationPipe` and `AllExceptionsFilter` — ensuring consistent validation and error responses.
Next: annotate DTOs, describe endpoints properly, and restrict access.

Day 3 1/2
TL;DR:
Added global `ValidationPipe` and unified `AllExceptionsFilter` in NestJS. API errors now follow a consistent format: `{ statusCode, error, message, code, details }`.
Today’s work focused on:
1. Standardizing input validation and error handling in the backend of the insurance sales network management system (NestJS, TypeScript, ESM, Turbo monorepo).
- Enabled global `ValidationPipe` with: `whitelist`, `forbidNonWhitelisted`, `transform`, `enableI…

Day 2:
TL;DR:
❌ `composite: true`
❌ `tsconfig.build.json`
✅ `paths` in `tsconfig.base.json`
✅ `include` shared libs explicitly where needed
✅ `turbo run build` just works
Wrestled for hours (~3) with TypeScript `project references` and `paths` in a Turbo monorepo (NestJS, ESM).
Turns out: if you want global aliases like `@my-lib/foo` to *just work* across apps — skip `composite: true` and `tsc --build`.
Project references and alia…