TECHDEV

ilding small, useful dev tools. Maker of env-doctor — a zero-dependency Python CLI that audits .env files.

Joined on Oct 16, 2026 [email protected] https://techdev.fun

Work

Indie developer building dev tools at techdev.fun

TECHDEV

Oct 24

Your CI failed. Was it a flake or a real break?

#javascript #node #devops #testing

4 min read

TECHDEV

Oct 23

Your agent asked "can I run this?" You said yes. It ran it 40 minutes later.

#node #ai #devops #opensource

2 min read

TECHDEV

Oct 23

I measured an AI sandbox's audit export. It contained zero records — so I built the layer that keeps its own.

#ai #security #opensource #python

4 min read

TECHDEV

Oct 22

Your scanners pass. Your audit evidence doesn't exist. We built the missing layer.

#devsecops #opensource #security #githubactions

6 min read

TECHDEV

Oct 22

I was tired of letting the OOM killer do my VRAM math, so I wrote a one-file CLI

#python #llm #gpu #opensource

2 min read

TECHDEV

Oct 22

Your agent forgot a decision you made last week. Mine did too.

#javascript #node #cli #ai

2 min read

TECHDEV

Oct 21

I was pasting 4KB of JSON into every prompt. So I built a key-folder that shrinks it — reversibly.

#node #javascript #json #ai

3 min read

TECHDEV

Oct 21

AI assistants cite fake stats with total confidence. I built a 10-second checker.

#python #ai #cli #opensource

2 min read

TECHDEV

Oct 21

After the agent-tool breach, I asked: where do my API keys actually live?

#security #python #cli #devops

2 min read

TECHDEV

Oct 21

Your dependencies will break. Your CI will leak. Probably not today.

#javascript #node #devops #security

3 min read

TECHDEV

Oct 19

Your CI is green. Your tests might be lying.

#testing #python #javascript #ai

3 min read

TECHDEV

Oct 18

Your build log is 40,000 lines. Your agent's context window is not.

#javascript #node #cli #devops

2 min read

TECHDEV

Oct 17

I installed a bunch of agent skills. Then I wrote a tool to audit them.

#python #ai #cli #devops

2 min read

TECHDEV

Oct 16

Your .env file is lying to you. I built a tiny tool to catch it.

#python #dotenv #cli #devops

3 min read

DEV Community

TECHDEV

Badges

Writing Debut

Skills/Languages

Currently learning

Currently hacking on

Available for

Your CI failed. Was it a flake or a real break?

Your agent asked "can I run this?" You said yes. It ran it 40 minutes later.

I measured an AI sandbox's audit export. It contained zero records — so I built the layer that keeps its own.

Your scanners pass. Your audit evidence doesn't exist. We built the missing layer.

I was tired of letting the OOM killer do my VRAM math, so I wrote a one-file CLI

Your agent forgot a decision you made last week. Mine did too.

I was pasting 4KB of JSON into every prompt. So I built a key-folder that shrinks it — reversibly.

AI assistants cite fake stats with total confidence. I built a 10-second checker.

After the agent-tool breach, I asked: where do my API keys actually live?

Your dependencies will break. Your CI will leak. Probably not today.

Your CI is green. Your tests might be lying.

Your build log is 40,000 lines. Your agent's context window is not.

I installed a bunch of agent skills. Then I wrote a tool to audit them.

Your .env file is lying to you. I built a tiny tool to catch it.