|
|
|
|
|
by ksaj
66 days ago
|
|
If you build or use something during work hours, and you're a coder coding, it seems pretty obvious to me that the company owns it. Don't fall in love with the code you wrote to do the work you did there. It's part of the process. Someone will have to maintain it well after you're gone. |
|
But I don't have anything in the contract about sharing my self-improvement skills and I consider my AI framework (cursor commands I created to not repeat myself, claude/cursor skills, system prompts - everything what makes me to generate code fast) as an acceleration of my work as developer.
If I leave without sharing this, company will continue develop the code I created/generated.
If I share this, I am losing my only handicap in the AI-era: they could take my A framework and the next developer will just type `/fix-issue gh 1243` and have the same result as I do have now.
The `/fix-issue` command is something I created months ago, and I am constantly improving so at this point the first, at most third, result is the code which goes through code review with suggestion-level insights and QA team can't find any bug.
I am not exaggerating. That command is really complex and loads plenty of skills (also mine) and md files (still mine, kept out of the repo) - in total it is like ~12 A4 pages text (I actually counted it now). This is basically my coding approach ported into AI.