DEV Community: Sreegeethesh

# I Built My Developer Portfolio as Peter Parker's Lab 🕷️

Sreegeethesh — Thu, 13 Aug 2026 06:21:19 +0000

I could have built another developer portfolio.

You know the one.

Dark background.

Glowing buttons.

"Full Stack Developer | AI | Cloud | DevOps"

Six project cards.

GitHub link.

Done.

But honestly, that doesn't feel like me.

Before I was interested in AI, software engineering, cloud, automation and all the other things I keep breaking and rebuilding, I was just a kid who loved Spider-Man.

And the older I got, the more I realized that I didn't actually relate to Spider-Man because he was a superhero.

I related to Peter Parker.

The curious kid.

The awkward kid.

The kid who builds things.

The kid who experiments.

The kid who fails and somehow keeps going.

That felt familiar.

So when I started building my portfolio, I wanted it to represent that.

I called it:

🧪 Peter Parker's Lab

The idea is that my portfolio is basically my digital lab.

A place where I can show what I'm building, what I'm learning and what I'm experimenting with.

🕷️ Peter Parker → curiosity

🕸️ Spider-Man → persistence

💻 Developer → everything I'm building today

And honestly, "lab" describes my development journey pretty well.

I build something.

It breaks.

I investigate why.

I fix it.

Then I get another idea and break something else.

😂

That's the fun part.

I'm currently interested in building things around:

AI
AI agents
automation
full-stack applications
developer tools
cloud infrastructure
DevOps
local-first software

I'm not trying to pretend I've mastered all of it.

I'm trying to keep learning by building real things.

That's what I want this portfolio to show.

Not just a list of technologies.

Not just a list of GitHub repositories.

But the problems I'm curious about and the things I'm actually trying to create.

🌐 Peter Parker's Lab

https://peterparker-lab.vercel.app/

This is version one.

I'll keep changing it as I change.

New projects.

New experiments.

New ideas.

Probably new bugs too.

Because maybe the best portfolio isn't one that says:

"Look how much I know."

Maybe it's one that says:

"Look what I'm curious enough to build next."

🕷️❤️

And yes...

I still think Spider-Man is one of the coolest characters ever.

Some things don't change.

I Built an Open-Source AI Video Clipping Pipeline

Sreegeethesh — Sat, 08 Aug 2026 06:46:05 +0000

I Built an Open-Source AI Video Clipping Pipeline

I wanted a tool that could take a long video and turn it into social-ready clips without uploading the entire video to some SaaS platform.

So I built AutoClip.

The idea is simple:

YouTube URL / Video File
          ↓
      Transcription
          ↓
   LLM Clip Selection
          ↓
   Vertical Reframing
          ↓
    Speaker Tracking
          ↓
   Animated Captions
          ↓
     MP4 Export
          ↓
    Buffer Scheduling

The interesting part is that the video processing happens locally.

AutoClip uses an LLM to identify moments worth clipping, but only the transcript text is sent to the LLM. The actual video stays on the user's machine.

It supports multiple caption styles:

Word Pop
Karaoke Fill
Clean Lower Third
Boxed

The final clips are rendered as 9:16 MP4s ready for social platforms.

Publishing Architecture

I also wanted publishing to follow the same privacy model.

Instead of building a cloud scheduler, AutoClip uses a BYOK approach.

The stack is:

Your PC
  ↓
AutoClip processes video
  ↓
Cloudflare R2
  ↓
Buffer
  ↓
Social Platform

The R2 bucket acts as temporary media storage so Buffer can access the video.

Once the job is handed off, the user's computer doesn't need to stay online.

No central media storage.

No SaaS layer.

No subscription.

No watermark.

No telemetry.

Just your infrastructure and your API keys.

Why I Built It

There are plenty of AI video tools already.

I wanted one where I could actually understand and control what happens to my content.

The goal was:

Your machine edits.
Your Buffer publishes.
Your content stays yours.

AutoClip is open source.

GitHub:

SREEGEETHES / Autoclip

AutoClip

The local-first AI clipper that finishes the job. Drop in a long video → get ranked, caption-burned, speaker-tracked 9:16 clips out — and schedule them to post while your PC is off.

Paste a YouTube link or drop a file. AutoClip transcribes it, uses an LLM to find the moments actually worth clipping, reframes them to vertical while tracking whoever is speaking, burns in animated captions, exports platform-ready MP4s — then hands the finished clips to Buffer to publish on schedule. No accounts with us. No uploads to our servers. No watermarks. No subscription.

Your machine edits. Your Buffer publishes. Your R2 bridges the media. Nobody owns your content but you.

What it does

Ingest anything — a YouTube URL or a local file, hours long or minutes.
Find the real hooks — an LLM reads the transcript and ranks the moments worth clipping, down to the word. Timing…

View on GitHub

I'd love feedback from anyone building content automation, video tooling, or local-first AI applications.

How I built an offline semantic photo search app (Python + Vector DB)

Sreegeethesh — Mon, 03 Aug 2026 10:51:14 +0000

Show DEV 🚀

I built OmniCard, a local-first AI media manager.

Features:

• Semantic image search

• AI captions

• Smart tags

• Duplicate detection

• SQLite + LanceDB

• Desktop application with pywebview

The goal was simple:

Search photos by what's inside them instead of by filename.

Example:

"Drone over mountains"

instead of

IMG_4829.jpg

The app stores everything locally, so your media never leaves your computer.

Live demo:
https://sreegeethes.github.io/Omnicard/

GitHub:
https://github.com/SREEGEETHES/Omnicard

Release:
https://github.com/SREEGEETHES/Omnicard/releases/tag/v1.0.0

Would love feedback from other Python and AI developers.