---
title: "Lakhyajit Changmai (@lakhyajit) | Hashnode"
description: "Founder of ZANCTA - privacy-first PDF and image tools that run entirely in your browser. No uploads, no server-side processing."
url: "https://hashnode.com/@lakhyajit"
---

@lakhyajit

# Lakhyajit Changmai

@lakhyajit · Guwahati, Assam, India · Joined October 2026

Founder of ZANCTA - privacy-first PDF and image tools that run entirely in your browser. No uploads, no server-side processing.

## Comments

[Helpful distinction between runtime helper threads and the libuv pool. One practical debugging trap: raising UV\_THREADPOOL\_SIZE will not move CPU-bound JavaScript off the event loop; it changes libuv’s pool capacity, while CPU-heavy work needs worker\_threads or a separate process. I’d also label any observed startup thread count with the exact Node and platform versions, since “seven” is an observation rather than a portable guarantee.](https://hashnode.com/posts/why-an-empty-nodejs-process-runs-7-threads/6af6d73a41060513e7d11ea0/comment/6af73fef3b7fa79a4a2fd181)

Comment · Article · 4h ago · [The 7 Threads Running Inside Every Node.js Process](https://hashnode.com/posts/why-an-empty-nodejs-process-runs-7-threads/6af6d73a41060513e7d11ea0)

[The consistency-group caveat in your post-discussion update is crucial for app-and-database backups: a file-level snapshot can be readable yet logically inconsistent if the database and application state are captured at different points. I’d document the quiesce/snapshot/restore sequence and test it on a clean instance, using paused writes or a database-native consistent dump where appropriate. That turns “backup completed” into a reproducible recovery path.](https://hashnode.com/posts/backups-arent-simple/6af6d3f1856174f724934b0c/comment/6af73fc63b7fa79a4a2fcc76)

Comment · Article · 4h ago · [Backups aren't simple](https://hashnode.com/posts/backups-arent-simple/6af6d3f1856174f724934b0c)

[The exact byte-boundary cases are a strong way to make this deterministic. I’d also assert that the client clears its selected-file preview and progress state after a 413, so a retry with a smaller file cannot reuse stale metadata. And your distinction is important: a local mock validates client behavior, while a few genuine uploads are still needed to confirm the gateway’s cap.](https://hashnode.com/posts/testing-file-upload-size-boundaries/6af72c894facdfb3d0295804/comment/6af73f943b7fa79a4a2fc6e6)

Comment · Article · 4h ago · [Testing File Upload Size Boundaries](https://hashnode.com/posts/testing-file-upload-size-boundaries/6af72c894facdfb3d0295804)