logoalt Hacker News

deadbabe • today at 7:18 PM • 4 replies • view on HN

You create secret workflows, skills, and solutions that you never give others access to. Already doing this at work, 65% of my tooling is not available to any other employee.


Replies

coffeebeqn • today at 7:45 PM

One of our staff engineers tried that but I just took one of the outputs they shared and told the same model figure out how to prompt and what to set up to do this and his super power was mine in an hour or less.

I don’t know what moats we can have at this point. I’m trying to build a side hustle with vibe coding something because if it’s a backend only you can access at least you have a tiny moat. If you’re just prompting slightly more cleverly at your employers Claude account you do not have a moat

_aavaa_ • today at 7:22 PM

As they say, this doesn't seem like a durable moat.

kodoman • today at 7:21 PM

I agree but then you have to make sure your prompting of the model does not expose the special technique, if your running local fine otherwise someone can just work out your tools or simply just pinch you skill markdown files.

ratelimitsteve • today at 8:00 PM

ooh shit i remember security through obscurity from back in the 90s. i wonder how well it will work in the age of fully automated reverse engineering and smart guess and check.

i also wonder if there's something in your employment agreement about the things you make on company time and who they belong to.