Syket Das

I build complete web, mobile, AI & 3D products end to end, solo. Founder of ReliaBuilds. 30+ shipped for founders & agencies. Building in public 🚀

[Syket Das @syket_d]

@ReliaBuilds 👏👏

[Syket Das @syket_d]

I build these for businesses (support bots, internal assistants). If you want one for your product, my DMs are open.

[Syket Das @syket_d]

How to give any app an AI chatbot that answers from YOUR own docs, not generic internet answers. Simple version 🧵

[Syket Das @syket_d]

You need three things: a place to store the chunks (a vector database), a way to search them, and the model to write the answer. That's it.

[Syket Das @syket_d]

Founders sitting on AI-generated code: get it reviewed before you launch. It ships fast but leaves security holes, especially around user data. First things I check are auth and how secrets are stored.

[Syket Das @syket_d]

@sama Whats changes u made?

[Syket Das @syket_d]

Axios just got supply chain attacked TODAY
[email protected] and [email protected] are compromised.

Attacker hijacked a maintainer's npm account and injected a hidden RAT that compromises your machine in 15 seconds flat.
❌ Don't npm install axios right now
❌ Don't just delete node_modules and move on
❌ Don't assume you're safe if you use a lockfile with ^1.14.0

✅ Pin to [email protected] or 0.30.3
✅ Search node_modules for "plain-crypto-js" - if it's there, you're hit
✅ Rotate EVERYTHING - SSH keys, API keys, npm tokens
✅ Rebuild from clean, don't try to "fix" a compromised machine

100M weekly downloads. 80% of cloud environments. This is massive.

[Syket Das @syket_d]

Axios just got supply chain attacked TODAY
[email protected] and [email protected] are compromised.

Attacker hijacked a maintainer's npm account and injected a hidden RAT that compromises your machine in 15 seconds flat.
❌ Don't npm install axios right now
❌ Don't just delete node_modules and move on
❌ Don't assume you're safe if you use a lockfile with ^1.14.0

✅ Pin to [email protected] or 0.30.3
✅ Search node_modules for "plain-crypto-js" - if it's there, you're hit
✅ Rotate EVERYTHING - SSH keys, API keys, npm tokens
✅ Rebuild from clean, don't try to "fix" a compromised machine

100M weekly downloads. 80% of cloud environments. This is massive.

[Syket Das @syket_d]

Feels like https://t.co/tEEkeg0fh6 doing the same thing. videos don’t even make sense.

We are still far to generate real videos. Image models are pretty good these days.

[Syket Das @syket_d]

OpenAI shutting down Sora is a reality check.

The model was incredible.
The product wasn’t.

AI video sounds exciting - until you factor in:
• massive compute costs
• unclear real-world use
• weak daily retention

We’re entering a new phase:
- Products need to make sense.
- Without real-world use-case you cant scale

[Syket Das @syket_d]

@Netajinonsense1 One thing i noticed ai always suggest that one youtube video if you don’t specify 😅

[Syket Das @syket_d]

AI replaced the junior dev role.

Cool. Here's the problem nobody's discussing:
Junior → Mid-level → Senior is how the pipeline works.

If juniors can't get hired, mid-levels don't develop.

If mid-levels get compressed, seniors never emerge.

10 years from now, who reviews the AI-generated code if nobody trained up through the ranks?

[Syket Das @syket_d]

developers are literally ditching Cursor right now

Chamath (VC, founder of 8090) publicly said:
"We need to migrate off Cursor. It's just too expensive vs Claude Code. The latter is equivalent."

Cursor is valued at $29.3B. Claude Code is included in a $20/mo plan.

the math isn't mathing for Cursor anymore

#AI #Claude #CursorAI

[Syket Das @syket_d]

I just ran a full SEO audit in 30 minutes using Claude.

No Ahrefs.
No SEMrush.
No complicated dashboards.
Just Claude + a simple workflow.
It automatically checked:

• technical SEO issues
• missing meta tags
• heading structure
• broken links
• alt text & accessibility
• internal linking gaps
• page performance signals
• content optimization opportunities

Then it generated a prioritized fix list of what to improve first.

AI is about to replace a lot of manual SEO work.

[Syket Das @syket_d]

Probably, you are also ignoring SEO

I did a complete SEO audit on my site. Never thought its gonna be that bad.

Share your site, I will send you a free audit + Action Plan

[Syket Das @syket_d]

Dev environments get messy fast.

Different Node versions, Python versions, random CLIs, secrets scattered everywhere… especially in monorepos.

That’s why I started using mise.

Think of mise as a unified dev environment manager.
It manages runtimes, tools, tasks, and even environment variables - all from one place.
In my monorepo, mise handles a few important things:

1️⃣ Runtime management

Different services need different versions.

Example:

API → Node 20

AI worker → Python 3.11
CLI tools → Bun
Instead of installing everything globally, I define it in .mise.toml:

[tools]
node = "20"
python = "3.11"
bun = "latest"

Anyone cloning the repo just runs:
mise install
and the entire environment installs automatically.
No setup docs. No version mismatch.
2️⃣ Monorepo consistency
In a large repo with multiple services, dev environments drift quickly.

With mise, the runtime versions are declared and enforced at the repo level, so every developer runs the same stack.

This removes the classic:

“works on my machine” problem.

3️⃣ Environment variables

I also use mise to load and secure environment variables.

Instead of manually exporting secrets or committing .env mistakes, mise can load env files automatically when entering the project.

This keeps configs centralized and predictable.

4️⃣ Task runner

You can also define commands in mise.

Example:

[https://t.co/L2VJMLXCBs]
run = "pnpm dev"

[https://t.co/ZNqlNfsvop]
run = "pnpm build"

Then run:

mise run dev

This makes onboarding easier for new devs.

5️⃣ Tooling in one place

Instead of installing:

nvm
pyenv
asdf

volta
mise replaces all of them.
One CLI. One config.

For monorepos and multi-language projects, it’s honestly a huge productivity boost.

[Syket Das @syket_d]

Dev environments get messy fast.

Different Node versions, Python versions, random CLIs, secrets scattered everywhere… especially in monorepos.

That’s why I started using mise.

Think of mise as a unified dev environment manager.
It manages runtimes, tools, tasks, and even environment variables - all from one place.
In my monorepo, mise handles a few important things:

1️⃣ Runtime management

Different services need different versions.

Example:

API → Node 20

AI worker → Python 3.11
CLI tools → Bun
Instead of installing everything globally, I define it in .mise.toml:

[tools]
node = "20"
python = "3.11"
bun = "latest"

Anyone cloning the repo just runs:
mise install
and the entire environment installs automatically.
No setup docs. No version mismatch.
2️⃣ Monorepo consistency
In a large repo with multiple services, dev environments drift quickly.

With mise, the runtime versions are declared and enforced at the repo level, so every developer runs the same stack.

This removes the classic:

“works on my machine” problem.

3️⃣ Environment variables

I also use mise to load and secure environment variables.

Instead of manually exporting secrets or committing .env mistakes, mise can load env files automatically when entering the project.

This keeps configs centralized and predictable.

4️⃣ Task runner

You can also define commands in mise.

Example:

[https://t.co/L2VJMLXCBs]
run = "pnpm dev"

[https://t.co/ZNqlNfsvop]
run = "pnpm build"

Then run:

mise run dev

This makes onboarding easier for new devs.

5️⃣ Tooling in one place

Instead of installing:

nvm
pyenv
asdf

volta
mise replaces all of them.
One CLI. One config.

For monorepos and multi-language projects, it’s honestly a huge productivity boost.