undefined

points

[-]

Just nerding out here, not rebutting, but when you say "craftspeople take their jigs with them from job to job" --- sort of. Sometimes. I think if you put a woodworker in a position where they obliged to build a new miter sled or assembly table, they might actually be thrilled. You make a tool, you use it for awhile, you build up a mental list of things you'd like to improve about it, that you'd do differently if you got a do-over; now you have an excuse to do it.

by happyopossum18 hours ago|

parent|

[-]

This, for like 37 things in my workshop right now.

by aquajet20 hours ago|

prev|

[-]

Using something like pi helps. I've made my own dotfiles for skills/extensions I like and can install them just like my normal dotfiles

https://github.com/anishthite/agent-dotfiles

by djfergus15 hours ago|

parent|

[-]

"Humor When you finish a job — completing a task, answering a question, fixing a bug, shipping a feature — end your final message with one short funny line. A quip, a dad joke, a wry observation, a playful self-roast. One line. No emoji spam. Make it land, then shut up."

whats the purpose of this? just fun or does it cause some desired behaviour?

by ClikeX11 hours ago|

parent|

[-]

> does it cause some desired behaviour?

Fun is desirable.

by agravier19 hours ago|

prev|

[-]

I've imported and adapted my personal agentic dev framework to my team relatively successfully (as I've kept it relatively harness independent), but it requires actually owning it, vibed or bloated or conceptually inconsistent stuff bite a lot when porting things over.

by worldsayshi20 hours ago|

prev|

[-]

> craftspeople take their jigs with them from job to job

Except for software gigs the software typically belongs to the customer so you'd need to rewrite it every time...

by ClikeX11 hours ago|

parent|

[-]

Depends. With all the web agencies I've made, the only code that belonged to customers was the actual website part. Any of the "jigs" that we made for our workflow was not part of that.

And contractually, any code I made was my employer's if I made it during office hours. Some even made a claim for code I would've written that during my employ that would be "competitive". Luckily, there was a massive difference in what I would do in my own time versus what they did.

by borski19 hours ago|

parent|

prev|

[-]

Depends. If you are a contractor, like most craftspeople, your tools are your own.

by ninjalanternshk18 hours ago|

parent|

[-]

My contracts always state I own tools created or byproducts of the work that don't end up in the work.

by pjmlp9 hours ago|

parent|

prev|

[-]

Only if you are self employed, otherwise it belongs to the agency.

by borski8 hours ago|

parent|

[-]

Again: it depends. It is all about how the contract is written.

by pjmlp7 hours ago|

parent|

[-]

I never seen any other kind of contract, on my 50ys.

by krzyk3 hours ago|

parent|

[-]

I'm curious how does it work, you handover the tools you wrote, .bashrc/.zshrc, etc?

When I'm hired in a company (not contract), they wipe the harddrive when I leave (well, I also do it before I hand it over sometimes). So they don't get the tools (I take them with myself, it would be a waste to loose them)

by borski7 hours ago|

parent|

prev|

[-]

You're definitely right for most agencies; most will let you use it in a portfolio or something, but not necessarily retain the rights to the work.

Some agencies do, however; it's dependent on the contract specifics.

by jaxn20 hours ago|

prev|

[-]

i have been thinking about this from a different direction: how do we make these shared within a company in a way that increases the productivity floor of the team/department/company. Sure, they can still be extended/enhanced by individuals, but we don’t need everyone configuring mcps, building institutional memory, etc.

for me, it’s not about the cost to leave, it’s about lowering the cost of onboarding and change.